Update docs: domain-based auth lookup, no connection IDs needed

Connection IDs are no longer stored in settings.json. The applier
finds auth connections by domain (linkedin.com, wellfound.com) at
runtime via the Kernel SDK. Updated SKILL.md, README.md, and bumped
to 0.1.4.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-06 15:57:55 -08:00
parent 668a40a51a
commit 0e18bbf481
4 changed files with 8 additions and 10 deletions

View File

@@ -53,12 +53,12 @@ kernel proxies create --type residential --country US --name "claw-apply-proxy"
kernel auth connections create --profile-name "LinkedIn-YourName" --domain linkedin.com
kernel auth connections create --profile-name "WellFound-YourName" --domain wellfound.com
# Complete initial login flows
# Complete initial login flows (use: kernel auth connections list to find IDs)
kernel auth connections login <linkedin-connection-id>
kernel auth connections login <wellfound-connection-id>
```
Add the profile names, connection IDs, and proxy ID to `config/settings.json`.
Add the profile names and proxy ID to `config/settings.json`. Connection IDs are not needed — the applier finds them automatically by domain.
### 3. Set up Telegram notifications