Repository navigation
Look up the config registry in the CLI, SDK, and bot detection skills - #51
Conversation
Agents following these skills chose browser configs from hardcoded defaults and never consulted the config registry. Add a lookup step that applies the recommended browser settings and proxy recipe, and starts a resolve on a miss so the next lookup has an answer. Drop datacenter proxies, which are deprecated and gone from the CLI and generated SDKs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5277253. Configure here.
| # Profile Website for Bot Detection Vendors | ||
|
|
||
| Analyzes a target website to identify bot detection vendors, their specific products, and challenge types. Supports comparative analysis between stealth and non-stealth browser modes. | ||
| Analyzes a target website to identify bot detection vendors, their specific products, and challenge types. Supports comparative analysis between stealth and non-stealth browser modes. Checks Kernel's config registry for a configuration already tested on the site, and starts an analysis when there isn't one. |
There was a problem hiding this comment.
KERNEL brand casing in new prose
Low Severity
New skill prose names the product Kernel and Kernel's in the frontmatter description, intro, and registry copy. User-facing skill text uses KERNEL and KERNEL's.
Additional Locations (2)
Triggered by learned rule: KERNEL brand casing in user-facing prose
Reviewed by Cursor Bugbot for commit 5277253. Configure here.
| -d "$(jq -n --arg url "$TARGET_URL" --arg intent 'search for a product and open the first result' '{url: $url, intent: $intent}')" | jq '.analysis' | ||
| ``` | ||
|
|
||
| The config registry needs a Hobbyist plan or higher. |
There was a problem hiding this comment.
Plan gate follows the examples
Medium Severity
The new config registry sections open with the lookup payoff and mention the Hobbyist plan only after the copy-pasteable calls. Agents that get a 403 mid-debug follow a dead-end path before learning the feature is plan-gated.
Additional Locations (2)
Triggered by learned rule: agent_helpers.py is for durable primitives only
Reviewed by Cursor Bugbot for commit 5277253. Configure here.
Sayan-
left a comment
Sayan-
left a comment
There was a problem hiding this comment.
reviewed the full diff and checked the registry API shapes, proxy recipes, and CLI flags. no merge blockers found. static review only, no live browser or analysis runs.
Summary
Agents that follow these skills pick a browser config from hardcoded defaults and never consult the config registry. When a site blocks them, nothing they find out goes back into the registry. This adds the registry to the skills agents use to build integrations.
resolvewith anintentwithout waiting, keeping the stealth default.kernel browsers createflags.--type datacentergone from the CLI and the generated SDKs.Plugin versions are unchanged, matching how earlier content changes landed.
Testing
@onkernel/sdk0.140.0 withtsc --strict, then ran it live: lookup, create-or-reuse the proxy by name, create a browser, clean up.kernel0.140.0 with the same flow.resolvelive, because it starts a real analysis. The request body matches the API spec and the SDK types.Not in this PR
grok/skills/kernel-mcpstill lists datacenter proxies. Rewrite kernel-mcp skill around flows #50 rewrites that file, so this PR leaves it alone.proxy_idinstead ofproxy: { id }.🤖 Generated with Claude Code
Note
Low Risk
Changes are documentation and agent skill guidance only; they do not modify runtime code or auth paths.
Overview
Teaches agents to look up Kernel’s config registry before creating browsers, instead of relying on hardcoded defaults. TypeScript and Python SDK skills add a Choose a Browser Config for a Site section:
lookupfor tested browser/proxy settings, one-time managed proxy creation under a stable name, and fire-and-forgetresolvewith anintentwhen there’s no recommendation (stealth fallback, Hobbyist plan note).The CLI skill documents the same flow via
curlto/config-registry/lookupand/resolve, including how recommendations map tokernel browsers createflags and proxy CLI commands.The profile-website-bot-detection skill runs registry lookup in Step 1, can start
resolvein Step 6 when there’s no recommendation and either browser was blocked, and extends the summary template with recommended configuration and analysis status. README reflects the expanded bot-detection skill description.Datacenter proxies are removed from the CLI proxies reference and the Python proxy example (ISP used instead); proxy reference copy is trimmed accordingly.
Reviewed by Cursor Bugbot for commit 5277253. Bugbot is set up for automated code reviews on this repo. Configure here.