add-provider
Skill4 starsChanged 2 days agoMITView on GitHub
Add a new agent CLI (Cursor, Codex, Gemini, Amp, Aider, OpenCode, Goose, Hermes, ...) as a provider across the Threadbase repos: the shared wire-name convention, vendor intake, iron rules and land order. Use when adding a provider, a new provider name, a start chip, or when the user says add a provider. The repo-specific steps live in each repo's own add-provider skill, see Companions.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- SDSLeon/lightcodetheir own version, first seen Nov 8, 2026
- Porabuild/Poracodetheir own version, first seen Nov 8, 2026
- agentconfig/agentconfig.orgtheir own version, first seen Nov 8, 2026
- VincentShipsIt/meterbar.devtheir own version, first seen Nov 6, 2026
- tddworks/ClaudeBartheir own version, first seen Nov 3, 2026
- Adham-Aly/quartermastertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use add-tool, release-notes and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-tool
Add a new tool to PilotSwarm. Covers defining the tool with defineTool(), registering it on the worker (worker-level or per-session), referencing it from the client via toolNames, and adding an integration test.
Also in 3 projects that use this
Microsoft AzureSkillrelease-notes
Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- ThinkInAIXYZ/deepchat★ 6.4ksame name
- tddworks/ClaudeBar★ 1.6ksame name
- pydantic/genai-prices★ 416same name
- Porabuild/Poracode★ 121same name
- SDSLeon/lightcode★ 121same name
- agent-cli-framework/aclif★ 20same name
- hyhmrright/StockAI★ 14same name
- VincentShipsIt/meterbar.dev★ 12same name
- yerdaulet-damir/vibe-coding-rules★ 10same name
- kiminmonaco/ClaudeBar★ 8same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- expo-local-shipSkill
- integration-by-batchesSkill
- setup-cloudflaredSkill
- ship-expo-cloudSkill
- ship-fastlaneSkill
- add-provider-mobileSkill
- expo-local-shipSkill
- integration-by-batches-mobileSkill
- setup-cloudflaredSkill
- ship-expo-cloudSkill
- ship-fastlaneSkill
- threadbase-designSkill
The file
Files
Add a provider (shared core)
A provider reaches users through three repos. Each declares its own ProviderName, and they are not linked: shipping one never updates the others.
| Half | Repo | What it adds |
| Live PTY | threadbase-streamer | A SessionRunner, capabilities, binary resolution, health |
| Phone chips | threadbase-mobile | Start chip, health parser entry, badges, filters, i18n |
| History index | threadbase-scanner | Transcript discovery and parsing |
This skill holds the rules all three halves share. Each repo's own .claude/skills/add-provider/ holds that repo's file-level steps and verify commands. Read both before changing anything.
Wire name
- One kebab-case wire name across all three repos (
claude-code,codex-cli,cursor,aider,opencode,goose). - The product label (
Aider,OpenCode) is separate from the wire name. - The binary on PATH (argv[0]) may differ from both. The Cursor CLI is
agent, notcursor. cursor-cliis a legacy alias: accept it, emitcursor.
Vendor intake — stop or continue
Answer these before adding a name. Do not guess spawn flags.
| Ask | If no |
| Is there a spawnable interactive CLI (PTY, not an editor sidebar)? | History-only. No live runner and no start chip — a chip for an agent that cannot start is a lie. The name may still be added to badges, filters and health if the scanner will emit it. |
| Exact argv[0] on PATH? | Resolve it. Never assume it equals the product name. |
| Native resume from an id? | Declare resume unsupported. Do not reuse another provider's resume flag. |
| Documented transcript path? | Live still ships. Leave history to the scanner. |
Iron rules
- Never default an unknown name to Claude. A ternary such as
=== 'codex-cli' ? Codex : Claudeis the bug. Use the repo's label helper and thePROVIDER_NAMESlist. - The new id goes in
PROVIDER_NAMESin every repo that has one. Allowlists and parsers drop unknown names silently. - Honest capabilities. Claim only what the CLI's TUI has been parsed for. Unknown TUI: no structured questions, no permission gates, raw terminal. Inventing gates is worse than a raw terminal.
- Do not invent terminal chrome filters until the TUI is captured.
- Do not watch or classify another provider's transcript files. Each provider's layout is its own parser.
- Do not install the vendor CLI unless the user explicitly asks. A missing CLI is reported as unavailable.
- Replace leftover hardcoded two- or three-way provider unions with
ProviderNameand the label helper. Grep the current unions, not onlycodex-cli.
Land order
- Streamer first (live runner). A phone that sends a name the streamer does not know fails open on the chip and then errors on start. The exception is a badge-only name that history already returns.
- Mobile second (chips).
- Scanner is its own slice. History indexing and the scanner version bump are a later PR. Never mix the bump into the live-runner PR.
Work in a sibling worktree cut from origin/main. Never nest a worktree under the repo root.
Companions
Changing this shared skill (wire-name convention, intake rules, iron rules, land order, out-of-scope) reaches every repo through the plugin. When a change also alters a repo's own steps, update that repo's add-provider skill in the same change set.
Out of scope
Installing the vendor CLI. Scraping a TUI that has not been captured. Editor-only or protobuf-only agents with no CLI.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

