SKILLEMALL.ai
GitHub ↗ RU Sign in

CC add-opencode

Use OpenCode as an agent provider. OpenRouter, OpenAI, Google, DeepSeek, etc. via OpenCode config — not the Anthropic Agent SDK. Per group via `ncl groups config update --provider opencode`; host passes OPENCODE_* and XDG mount when spawning containers.

nanocoai/nanoclaw Agent Skills author: nanocoai MIT 42 files · 37 scripts body ≈ 4 888 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Use OpenCode as an agent provider.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
93
Quality 40%
84
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 7

    ✓ No critical or high findings

    Medium and low: 7
    • low Secrets in code secret-password-literal payload/container/agent-runner/src/providers/opencode.config.test.ts:74
      Hard-coded password / key literal (may be an example) (detector / deny-list definition; test fixture / example file)
      expect(config.provider).toMatchObject({ anthropic: { options: { apiKey: 'nc-o…-v1' } } });
      detectorfixture
    • low Secrets in code secret-password-literal payload/container/agent-runner/src/providers/opencode.config.test.ts:84
      Hard-coded password / key literal (may be an example) (test fixture / example file)
      expect(entry.options).toEqual({ apiKey: 'nc-o…-v1', baseURL: 'https://inference.example.test/v1' });
      fixture
    • low Secrets in code secret-password-literal payload/container/agent-runner/src/providers/opencode.config.test.ts:93
      Hard-coded password / key literal (may be an example) (test fixture / example file)
      expect(entry.options).toEqual({ apiKey: 'nc-o…-v1' });
      fixture
    • low Secrets in code secret-password-literal payload/container/agent-runner/src/providers/opencode.config.test.ts:377
      Hard-coded password / key literal (may be an example) (test fixture / example file)
      expect(entry.options).toEqual({ apiKey: 'nc-o…-v1' });
      fixture
    • low Secrets in code secret-high-entropy-token payload/container/agent-runner/src/providers/opencode.question.test.ts:46
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      id: 'que_…ezK',
      fixturequoted
    • low Secrets in code secret-high-entropy-token payload/container/agent-runner/src/providers/opencode.question.test.ts:52
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      requestID: 'que_…ezK',
      fixturequoted
    • low Secrets in code secret-high-entropy-token payload/scripts/opencode-vault.ts:49
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      clientId: 'app_…ann',
      quoted

    Files scanned: 42. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 65): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 54/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 16 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4888 tokens
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 253: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 9 items
    • +4Has examples (20 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.