provider-devin
Skill16 starsChanged 2 months agoMITView on GitHub
Track and maintain the upstream Devin CLI contract. Use when Devin ships a CLI release, when a `devin` flag, permission mode, ACP entrypoint, or subcommand changes, or when an upstream scan flags drift. Process guidance only: `src/upstream-contracts.ts` is the mechanical source of truth.
In this repository19 other files it gives its agents.
- site/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- async-job-orchestrationSkill
- implement-review-fixSkill
- least-cost-routingSkill
- multi-llm-reviewSkill
- personal-agent-config-kitSkill
- provider-claudeSkill
- provider-codexSkill
- provider-cursorSkill
- provider-geminiSkill
- provider-grokSkill
- provider-mistralSkill
- public-demo-sessionSkill
- retrospective-walkSkill
- secure-orchestrationSkill
- session-workflowSkill
- supply-chain-guardSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Keep the gateway's Devin (devin) integration aligned with the upstream CLI.
- Very specific: line 41
Use devin_request for normal work and devin_request_async for long-running work.
- Very specific: line 48
Treat permissionMode:"accept-edits" as an explicit edit-authorizing choice.
- Distinctive: line 58
Use a real resumable provider session only when the response reports it as resumable.
- Very specific: line 67
All other caller-controlled argv values are admitted in their final encoded form before spawn.
- Very specific: line 75
Follow multi-llm-review's full-access protocol, inspect the current request schema and live capability response, and use a fresh …
- Distinctive: line 101
Add conformance fixtures that prove every new accept and reject behavior.
- Very specific: line 102
If a source URL or watch category changes, update TypeScript metadata first, then mirror it in docs/upstream/provider-sources.dag.toml.
- Very specific: line 104
Verify with npm run build, npm run upstream:contracts, and targeted provider tests before the full suite.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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: Devin CLI
Keep the gateway's Devin (devin) integration aligned with the upstream CLI.
This skill does not define argv or environment behaviour. The single mechanical
source of truth is UPSTREAM_CLI_CONTRACTS.devin in
src/upstream-contracts.ts, enforced by validateUpstreamCliArgs and
validateUpstreamCliEnv. Do not re-encode flags, permission modes, ACP rules,
or session rules here or in TOML.
Identity
| Field | Value |
| CliType | devin |
| Executable | devin |
| Distribution | vendor installer / self-update |
| Command docs | https://cli.devin.ai/docs/reference/commands |
| CLI docs | https://docs.devin.ai/cli |
| Changelog | https://docs.devin.ai/cli/changelog/stable |
| Watch categories | flags, subcommands, permission-modes, acp-entrypoint |
These values mirror UPSTREAM_CLI_CONTRACTS.devin.upstreamMetadata and
docs/upstream/provider-sources.dag.toml ([providers.devin]). The TypeScript
metadata is authoritative; the TOML is scanner input only.
Gateway use
- Discover the live gateway surface before relying on Devin-specific controls:
For a cached read-only resource, useprovider_tool_capabilities({cli:"devin"})provider-tools://devin. - Use
devin_requestfor normal work anddevin_request_asyncfor long-running work. Sync calls may auto-defer; pollllm_job_statusand fetch withllm_job_resultwhen that happens. - Omit
modelunless the caller explicitly requests one. Use only request controls reported byprovider_tool_capabilities. Devin must useapprovalStrategy:"legacy": it rejects Claude-onlymcp_managedbefore launch, andapprovalPolicyhas no effect. - Treat
permissionMode:"accept-edits"as an explicit edit-authorizing choice. It is not equivalent to unrestricted autonomous execution. - Devin accepts flat
promptonly, notpromptParts. For CLI transport, pass localworkingDiror a verified registeredworkspaceto bind the repository. Use gatewayworktreeonly with an explicit provider-nativesessionIdthat is not overridden bycreateNewSession; fresh,createNewSession, andresumeLatest-only worktree requests fail closed. ACP rejectsworkingDirandworktree; use its registeredworkspaceselector. An unscoped CLI child runs in a fresh neutral temporary cwd, not the gateway repository. - Use a real resumable provider session only when the response reports it as
resumable. Gateway bookkeeping IDs are not automatically valid Devin session
IDs.
resumeLatest:trueneedsworkingDir,workspace, or a configured default workspace because Devin's latest-session pointer is cwd-scoped. - Native ACP is capability-gated. It rejects
approvalStrategy:"mcp_managed"and anyapprovalPolicy, as does the Devin CLI gateway path. Probe the actual entrypoint withdevin acp --help, not onlydevin --version. - Devin's CLI print prompt is argv-bound. Oversized UTF-8 input fails before
spawn as non-retryable
input_too_large; the gateway never truncates it. All other caller-controlled argv values are admitted in their final encoded form before spawn. Embedded NUL bytes return non-retryableinvalid_inputwithout exposing the rejected value.
Full-access review handoff
For a user-authorized exhaustive review that needs full provider permissions and
native MCP access, do not infer the launch controls from this maintenance guide.
Follow multi-llm-review's full-access protocol, inspect the current request
schema and live capability response, and use a fresh target-checkout
node dist/index.js --transport=stdio gateway rather than a global process.
Reapply the grant on every new job, preserve native MCP configuration without a
pretend gateway allowlist, send the corrective-program report and exact
diff/file identity, set no caller caps, and honor a user-required 90-second
progress cadence. The reviewer must independently inspect code, docs, tests,
and commands before it can approve.
Scan for upstream change
npm run upstream:scan -- --provider devin
npm run upstream:scan -- --live --provider devin --fail-on-critical
npm run upstream:scan -- --provider devin --probe-installed --fail-on-critical
npm run upstream:scan -- --live --provider devin --probe-installed --write-snapshot --write-reportA failed source fetch is advisory unless --fail-on-critical is passed. The
installed help probe is the primary evidence for fast-moving CLI surface drift.
Update procedure
- Edit
UPSTREAM_CLI_CONTRACTS.devininsrc/upstream-contracts.ts: flags, arities, enum values, permission modes, session rules, ACP probe commands, and catalogued subcommands belong there. - Add conformance fixtures that prove every new accept and reject behavior.
- If a source URL or watch category changes, update TypeScript metadata first,
then mirror it in
docs/upstream/provider-sources.dag.toml. - Verify with
npm run build,npm run upstream:contracts, and targeted provider tests before the full suite.
Devin-specific notes
- Tested against
devin 3000.6.12 (fc947ca5). - Current upstream help includes
auto,accept-edits,smart, anddangerouspermission modes. Keep the gateway contract, request schemas, capability description, and fixtures synchronized when that set changes. --printand--resumeaccept optional upstream values. The gateway's headless request path may intentionally use a narrower form, which should be stated in request tests rather than inferred from root help.- Catalog administrative, authentication, plugin, MCP, sandbox, and setup commands for drift monitoring. Do not expose them through request argv without a separately reviewed gateway surface.
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.

