openwork-core
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionopenwork-coreExecute the skills CLI command in your project's root directory to begin installation:
Fetches openwork-core 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 openwork-core. Access via /openwork-core 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
AGENTS.md, VISION.md, PRINCIPLES.md, PRODUCT.md, and ARCHITECTURE.md before changing behavior.vendor/opencode exists for self-reference.tauri-solidjs skill for stack-specific guidance.git -C vendor/opencode pull --ff-only
pnpm tauri dev # Desktop development
pnpm tauri ios dev # iOS development
pnpm tauri android dev # Android development
# Or run directly in the desktop package:
pnpm -C packages/desktop tauri dev
opencode -p "your prompt" -f json -q
~/.opencode/opencode.db # SQLite database
sessions — Task runsmessages — Chat messages and tool callshistory — File change trackinggit clone https://github.com/anomalyco/opencode vendor/opencode
pnpm create tauri-app . --template solid-ts
pnpm tauri ios init
pnpm tauri android init
git clone https://github.com/anomalyco/opencode vendor/opencode
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
ailabs-393/ai-labs-claude-skills
Useful defaults in openwork-core — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
openwork-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend openwork-core for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
openwork-core is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
openwork-core fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added openwork-core from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: openwork-core is focused, and the summary matches what you get after install.
Useful defaults in openwork-core — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
openwork-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
openwork-core reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 41