Rewrite the Explorbot skills: local setup, no-install running, when-to-use descriptions - #167
Merged
Merged
Conversation
Explorbot's agentic-usage doc makes the global installation the default path — models and a key once per machine, no project files — but the skills still taught the project-local flow only: npm i explorbot, ESM package.json, provider packages, a config to hand-edit. - explorbot-setup: global install first, env-var and project-local modes moved to references/. Providers, model ids, and key variable names are no longer named in the skill; they come from `explorbot init --help` and the version's models.json, so a new provider needs no skill edit. - explorbot-fundamentals: docs were read from node_modules/explorbot/docs with flat filenames — that directory does not exist and the layout has changed. Points at the package, the repo, or GitHub, with current paths. Adds mode detection, artifact locations, and exit-code semantics. - explorbot-plan: plans belong in the repo; run commands per mode. Follows SKILL-GUIDE: bullets over prose, one fact in one place, no communication coaching. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The global install is machine-wide and every run names its own site, so there is no default site to configure. `test`, `learn`, and `knows` take EXPLORBOT_URL. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- Descriptions say when to reach for the skill, not how Explorbot is built. The mode names, ~/.explorbot paths, and artifact layout are body material at most. - Fundamentals points at docs/index.json instead of copying a 18-row index that goes stale on every doc move. - Setup treats local and global as the user's choice and asks. Local is the fuller setup a project keeps; global is a provider and a key. The local flow is back in SKILL.md rather than a reference file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…t one Setup is the project install — explorbot.config.js, .env, knowledge, and generated tests in the repo — with no global path competing for it. Running Explorbot needs no install at all: npx plus a provider. That belongs where commands are run, so fundamentals owns it, and the env-var form moved there as references/no-install.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A bare `app.example.com/dashboard` cannot be told apart from a relative path, so the skills no longer suggest it. A relative path resolves against web.url or EXPLORBOT_URL; without either, pass the full URL. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DavertMik
changed the title
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
1 participant
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.
The skills were a version behind
docs/workflow/agentic-usage.mdand had drifted from how Explorbot actually works.The split
explorbot-setupexplorbot.config.js,.env, knowledge and generated tests in the repoexplorbot-fundamentalsnpxplus a providerexplorbot-planexplorbot testSetup no longer offers a global path, and no longer decides for the user. Running Explorbot needs no install at all, and that belongs where commands are run, so fundamentals owns it with the detail in
references/no-install.md.Descriptions say when to use the skill
They were listing how Explorbot is built — modes,
~/.explorbotpaths, artifact layout. Now each is a trigger sentence: "install Explorbot into a project", "running or debugging from the command line", "write a test plan by hand".Docs are pointed at, not copied
Fundamentals carried an 18-row table of doc filenames — all stale, since the docs had moved into subdirectories, and pointing at
node_modules/explorbot/docs/, which did not exist (fixed upstream in testomatio/explorbot#115). It now says where docs live and to readdocs/index.jsonto pick a page. Nothing to re-sync when a doc moves.No provider or model knowledge in the skills
Provider names, model ids, and
*_API_KEYvariables appear nowhere. The skills read the provider list fromexplorbot init --helpand letinitpick model ids from that version'smodels.json. Adding a provider upstream needs no skill edit.Facts corrected
http(s)://…URL or a/pathresolved againstweb.url/EXPLORBOT_URL. The bare-host form the docs advertise is ambiguous and is not taught.exploreandtestexit0on completion — read the report, not the exit code. Onlynavigategates.test,learn,knows,experience, andcompacttake no target and readEXPLORBOT_URL.explorbot context(no AI calls) added as the cheap page check.[[explorbot-debug]]/[[explorbot-fix-session]]links removed.Size
explorbot-setup334 → 86 lines,explorbot-fundamentals88 → 74, plus a 36-line reference. Per SKILL-GUIDE: bullets over prose, one fact in one place, no communication coaching.Pairs with testomatio/explorbot#115, which ships
docs/in the npm package.🤖 Generated with Claude Code