ワンクリックで
opencode-agent-devkit
Generate OpenCode agent markdown definitions with safe permission presets and an interactive question flow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Generate OpenCode agent markdown definitions with safe permission presets and an interactive question flow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforce this repository's actual coding rules and verification flow (TypeSpec -> generated artifacts -> implementation). Use when writing, modifying, refactoring, or reviewing code in this repository.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
| name | opencode-agent-devkit |
| description | Generate OpenCode agent markdown definitions with safe permission presets and an interactive question flow. |
| compatibility | opencode |
Create .opencode/agents/<name>.md (or ~/.config/opencode/agents/<name>.md) in the same format as opencode agent create, but driven by the question tool.
question tool (name, description, mode, model, permissions).Use this when you want to add or update an OpenCode agent under .opencode/agents/.
Ask follow-up questions (still via the question tool) when:
kebab-case, filename-safe)description (required; 1-2 sentences)mode (primary, subagent, or all){file:./prompts/...} reference)Optional inputs:
model, temperature, maxSteps, hidden, provider-specific optionsOpenCode decides model and provider options based on whether you explicitly set them.
model:
primary agents use the globally configured model (from your OpenCode config).subagent agents inherit the model from the invoking primary agent.model, it is pinned to that model (independent of the primary).Provider-specific knobs (for example: reasoningEffort: "high", textVerbosity: "low", etc.) can be placed as additional frontmatter keys and will be passed through to the provider.
Recommendation:
model and omit provider-specific options.model + low temperature explicitly..opencode/agents/<name>.md~/.config/opencode/agents/<name>.md@<name>)question call for the baseline.custom permissions, ask a second question call for details.kebab-case names for stability.permission: (not deprecated tools: booleans).permission.bash), rules are evaluated by wildcard match with the last matching rule winning. Put "*" first, and put specific deny/allow exceptions after it.permission.task), also start with "*": deny, then allow only explicit subagent names. Do not allow the agent to call itself.bash allowlists, always deny destructive patterns like rm *.These are suggested starting points. Customize as needed.
Note: lsp is experimental and only available when OPENCODE_EXPERIMENTAL_LSP_TOOL=true (or OPENCODE_EXPERIMENTAL=true).
permission:
edit: deny
bash: deny
webfetch: deny
task: deny
read: allow
glob: allow
grep: allow
list: allow
lsp: allow
permission:
edit: deny
webfetch: deny
task: deny
read: allow
glob: allow
grep: allow
list: allow
lsp: allow
bash:
'*': ask
'git diff*': allow
'git status*': allow
'git log*': allow
'git show*': allow
'git grep*': allow
'rm *': deny
permission:
edit: allow
webfetch: deny
task: deny
read: allow
glob: allow
grep: allow
list: allow
lsp: allow
bash:
'*': allow
'git add*': deny
'git commit*': deny
'git status*': allow
'git diff*': allow
'git log*': allow
'pnpm lint*': allow
'pnpm test*': allow
'pnpm gen*': allow
'pnpm build*': allow
'go test*': allow
'go vet*': allow
'rm *': deny
'git push*': deny
"*": allow), still deny destructive commands (e.g. rm *, git push*, git commit*, git add*) and keep the rest least-privilege where possible.permission.task (start with "*": deny, then allow only explicit subagent names). Never allow the agent to invoke itself, and avoid permitting other delegators to reduce the risk of infinite call loops.scripts/new_agent.pyscripts/validate_agents.pyscripts/README.mdassets/agent.body.template.mdassets/README.mdreferences/repo-agent-examples.mdreferences/README.mdSKILL.md is spelled in all capsname and description exist in YAML frontmatternamepermission.skill is not set to deny