Use this skill whenever OpenWork behavior is implemented directly on top of OpenCode primitives (skills, plugins, MCP servers, opencode.json config, tools/permissions). It anchors decisions to the official OpenCode documentation and keeps terminology consistent in the UI.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionopencode-primitivesExecute the skills CLI command in your project's root directory to begin installation:
Fetches opencode-primitives from different-ai/openwork and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate opencode-primitives. Access via /opencode-primitives in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
13.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
13.3K
stars
Use this skill whenever OpenWork behavior is implemented directly on top of OpenCode primitives (skills, plugins, MCP servers, opencode.json config, tools/permissions). It anchors decisions to the official OpenCode documentation and keeps terminology consistent in the UI.
.opencode/skills/<name>/SKILL.md or global ~/.config/opencode/skills/<name>/SKILL.md.skills/*/SKILL.md in .opencode/ or .claude/skills/.SKILL.md requires YAML frontmatter: name + description.^[a-z0-9]+(-[a-z0-9]+)*$), length 1-64, must match directory name.opencode.json permissions (permission.skill allow/deny/ask)..opencode/plugins/ (project) or ~/.config/opencode/plugins/ (global).opencode.json under plugin and installed with Bun at startup.opencode.json under mcp with unique names.type: "local" + command array; remote servers use type: "remote" + url.enabled.tools in config, including glob patterns..well-known/opencode -> global ~/.config/opencode/opencode.json -> custom path -> project opencode.json -> .opencode/ directories -> inline env overrides..opencode subdirectories are plural by default (agents/, commands/, plugins/, skills/, tools/, themes/), with singular names supported for compatibility.Call skill({ name: "opencode-primitives" }) before implementing or documenting any OpenWork behavior that maps to OpenCode primitives.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: opencode-primitives is focused, and the summary matches what you get after install.
opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
opencode-primitives reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added opencode-primitives from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in opencode-primitives — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 70