create-agent-opencode

Generate and validate OpenCode subagent bundles from canonical agent source files.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill create-agent-opencode-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-agent-opencode
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/create-agent-opencode
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill create-agent-opencode-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually authoring OpenCode agent configurations risks divergent permissions, invalid model identifiers, and hand-edited bundles that drift from the canonical agent definitions. This Skill deterministically generates and locally validates candidate bundles for PoP's six OpenCode subagents without invoking any model, provider, or network. ## Core Features & Use Cases - Deterministic Bundle Generation: Renders .opencode/agents/*.md files and opencode.json from the six canonical specialist sources in .agents/agents/ using a closed JSON profile. - Fail-Closed Validation: Enforces exact role sets, permission allowlists, subagent_depth: 2, SHA-256 manifest digests, and rejects deprecated tools fields, symlinks, and unmanaged file collisions. - Transactional Writes: Stages output in a temporary directory, validates it, and atomically swaps it into place with backup rollback on failure. - Use Case: After editing the canonical planner or executor agent definitions, run the builder to produce a validated candidate bundle with a manifest of hashes, then materialize only the verified files into your project. ## Quick Start Use the create-agent-opencode skill to build and validate a candidate OpenCode agent bundle from the canonical sources in .agents/agents/ using the closed profile fixtures/profiles.valid.json.

Frequently Asked Questions about create-agent-opencode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate OpenCode agent configuration files from source definitions?▼

Run the build_agents.py script with the build action, passing --source-dir pointing to the six canonical agent Markdown files, --profiles with a closed JSON profile, and --destination for an isolated candidate directory. The script renders and validates the bundle before writing it transactionally.

How do I validate an OpenCode agent bundle without rebuilding it?▼

Use the validate-static action of build_agents.py with the same source directory, profile, and destination arguments. It re-renders the expected output and compares manifest digests and file contents, printing STATIC_OK only when everything matches.

What model identifier format does OpenCode require for providers?▼

OpenCode splits the model ID at the first slash, so every model needs an explicit provider prefix such as kimi-for-coding/<model> or openrouter/<organization>/<model>. Profiles referencing models without a declared capability are rejected.

Why does the OpenCode agent build fail with a BLOCKED error?▼

Builds fail closed when sources are missing or divergent, profiles contain deprecated tools fields or wrong permissions, the destination looks like an active project root, or managed files were edited outside the builder. The error message identifies the exact invariant violated.

Can I hand-edit generated OpenCode agent bundle files?▼

No. Generated bundles are disposable projections of the canonical sources in .agents/agents/. The builder detects outside modifications via SHA-256 manifest digests and refuses to proceed; edit the source files and rebuild instead.