[GRO-1166] Remove openclaw platform references from SKILL.md#39
Merged
[GRO-1166] Remove openclaw platform references from SKILL.md#39
Conversation
8a34f6a to
0a4ce11
Compare
shrey150
commented
Mar 24, 2026
Kylejeong2
approved these changes
Mar 24, 2026
Member
Kylejeong2
left a comment
There was a problem hiding this comment.
will this confirm removing the suspicious flag from openclaw? PR itself looks good to me so approving
Remove the `openclaw browserbase setup` command reference from the browser skill SKILL.md. This reference was causing ClawHub's OpenClaw security scanner to flag the skill as "Suspicious" because it implies undeclared file access to ~/.openclaw/openclaw.json. The skill only needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID env vars, which are already documented. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The ClawHub security scanner reads all skill files, not just SKILL.md. Remove remaining openclaw credential bridging, eval, and setup command references from REFERENCE.md and EXAMPLES.md. Replace with direct env var export instructions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
browse-cli 0.2.0 infers the project from the API key, so BROWSERBASE_PROJECT_ID is no longer needed for remote mode. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
e2f659b to
dfe2383
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
openclawplatform references frombrowser/SKILL.md,browser/REFERENCE.md, andbrowser/EXAMPLES.md~/.openclaw/openclaw.jsonand undeclared credential bridging behavioropenclaw browserbase setupandeval "$(openclaw browserbase env ...)"with directexportenv var instructionsBROWSERBASE_API_KEYandBROWSERBASE_PROJECT_IDenv vars — how users set them is not the skill's concernChanges
openclaw browserbase setupfallback instructionbrowse env remoteContext
The ClawHub scanner reads all skill files (not just SKILL.md) and flags mismatches between declared metadata and runtime instructions. Passing skills like
githubandweathernever reference OpenClaw platform internals — they just declare what they need and let the platform handle the rest.Test plan
🤖 Generated with Claude Code
Note
Low Risk
Low risk documentation-only updates that change setup guidance for remote mode; main risk is users following outdated Browserbase credential requirements.
Overview
Removes OpenClaw platform/setup references from the browser skill docs and examples, replacing
openclaw browserbase setup/credential-bridging instructions with directexport BROWSERBASE_API_KEY=...guidance.Updates remote-mode documentation throughout to reflect that Browserbase sessions require only
BROWSERBASE_API_KEY(droppingBROWSERBASE_PROJECT_IDmentions) and tweaks a couple of CLI examples accordingly.Written by Cursor Bugbot for commit dfe2383. This will update automatically on new commits. Configure here.