provider-adapter
Skill31 starsChanged 2 months agoApache-2.0View on GitHub
Add or modify a target provider (vercel, aws, gcp, supabase, github, ssh, or a new one) - connect modes (CLI login, token, OAuth, keys), test and health, token issue/revoke and scoping, scope classification, shims, fixtures and tests.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- db-migrationSkill
- ipc-commandSkill
- port-screenSkill
- releaseSkill
- run-appSkill
- spec-lookupSkill
- state-machine-changeSkill
- ui-componentSkill
- visual-diffSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Add the id to providerSchema (packages/core/src/model/common.ts) and the second Provider union in apps/desktop/src/main/providers/types.ts.
- Very specific: line 26
Run the security-reviewer subagent.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Provider adapter: $ARGUMENTS
The full, current walkthrough is docs/contributing/adding-a-target.md (worked example: Supabase). Read it first and
follow its "Adding yours" checklist; this is the short version.
- Add the id to
providerSchema(packages/core/src/model/common.ts) and the secondProviderunion inapps/desktop/src/main/providers/types.ts;targets.providerhas a SQLCHECK, so add a table-rebuild migration (/db-migration). - Implement
ProviderAdapterinapps/desktop/src/main/providers/$0.ts: connect (CLI login first, then token / OAuth / keys under Advanced),test,health,issue,revoke,scopeOfCommand(argv)(fails closed: unknown commands are the widest scope). Register it inproviders/index.ts. - Secrets go through
CredentialVaultonly, behindcredentialRef;configholds non-secret ids. Reportscopedhonestly: an unscoped prod credential needs MFA even for reads. - Shims are generic (
packages/cli/src/wrap.ts+exec_authorize); add the CLI name to the shim tool list, the stripped env vars and the secret shapes the guide lists. - Copy and UI: provider names, connect bodies and the renderer's provider lists (see the guide's checklist).
- Tests:
MemoryVault, stubbedfetch,FakeCliRunner, a scope table including "fails closed", the registry test. Fake credentials are markedFIXTURE; never call real providers. - Run the
security-reviewersubagent.
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.

