Language-specific coding standards loaded on-demand by other skills.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstandardsExecute the skills CLI command in your project's root directory to begin installation:
Fetches standards from boshu2/agentops 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 standards. Access via /standards 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
243
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
243
stars
Language-specific coding standards loaded on-demand by other skills.
This is a library skill - it doesn't run standalone but provides standards references that other skills load based on file types being processed.
| Standard | Reference | Loaded By |
|---|---|---|
| Skill Structure | references/skill-structure.md |
vibe (skill audits), doc (skill creation) |
| Python | references/python.md |
vibe, implement, complexity |
| Go | references/go.md |
vibe, implement, complexity |
| Rust | references/rust.md |
vibe, implement, complexity |
| TypeScript | references/typescript.md |
vibe, implement |
| Shell | references/shell.md |
vibe, implement |
| YAML | references/yaml.md |
vibe |
| JSON | references/json.md |
vibe |
| Markdown | references/markdown.md |
vibe, doc |
| SQL Safety | references/sql-safety-checklist.md |
vibe, pre-mortem (when DB code detected) |
| LLM Trust Boundaries | references/llm-trust-boundary-checklist.md |
vibe, pre-mortem (when LLM code detected) |
| Race Conditions | references/race-condition-checklist.md |
vibe, pre-mortem (when concurrent code detected) |
| Codex Skills | references/codex-skill.md |
vibe (when skills-codex/ or converter files detected) |
| Test Pyramid | references/test-pyramid.md |
plan, pre-mortem, implement, crank, validation, post-mortem |
Skills declare standards as a dependency:
skills:
- standards
Then load the appropriate reference based on file type:
# Pseudo-code for standard loading
if file.endswith('.py'):
load('standards/references/python.md')
elif file.endswith('.go'):
load('standards/references/go.md')
elif file.endswith('.rs'):
load('standards/references/rust.md')
# etc.
Specialized checklists for high-risk code patterns. Loaded automatically by /vibe and /pre-mortem when matching code patterns are detected:
| Checklist | Trigger Pattern | Risk Area |
|---|---|---|
sql-safety-checklist.md |
SQL queries, ORM calls, migration files, database/sql, sqlalchemy, prisma |
Injection, migration safety, N+1, transactions |
llm-trust-boundary-checklist.md |
anthropic, openai imports, prompt templates, *llm*/*prompt* files |
Prompt injection, output validation, cost control |
race-condition-checklist.md |
Goroutines, threads, asyncio, sync.Mutex, shared file I/O |
Shared state, file races, database races |
codex-skill.md |
Files under skills-codex/, convert.sh, skills-codex-overrides/ |
Codex API conformance, prohibited primitives, tool mapping |
Skills detect triggers via file content patterns and import statements. Each checklist's "When to Apply" section defines exact detection rules.
For comprehensive audits, skills can load extended standards from
vibe/references/*-standards.md which contain full compliance catalogs.
| Standard | Size | Use Case |
|---|---|---|
| Tier 1 (this skill) | ~5KB each | Normal validation |
| Tier 2 (vibe/references) | ~15-20KB each | Deep audits, --deep flag |
| Domain checklists | ~3-5KB each | Triggered by code pattern detection |
Skills that use standards:
/vibe - Loads based on changed file types/implement - Loads for files being modified/doc - Loads markdown standards/bug-hunt - Loads for root cause analysis/complexity - Loads for refactoring recommendationsUser says: /vibe (detects changed Python files)
What happens:
auth.py in changesetstandards/references/python.md automaticallyResult: Python code validated against language-specific standards without manual reference loading.
User says: /implement ag-xyz-123 (issue modifies Go files)
What happens:
server.go in implementation scopestandards/references/go.md for contextResult: Go code generated conforming to standards, reducing post-implementation vibe findings.
| Problem | Cause | Solution |
|---|---|---|
| Standards not loaded | File type not detected or standards skill missing | Check file extension matches reference; verify standards in dependencies |
| Wrong standard loaded | File type misidentified (e.g., .sh as .bash) | Manually specify standard; update file type detection logic |
| Deep standards missing | Vibe needs extended catalog, not found | Check vibe/references/*-standards.md exists; use --deep flag |
| Standard conflicts | Multiple languages in same changeset | Load all relevant standards; prioritize by primary language |
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
standards reduced setup friction for our internal harness; good balance of opinion and flexibility.
standards is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: standards is the kind of skill you can hand to a new teammate without a long onboarding doc.
standards has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: standards is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in standards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
standards is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for standards matched our evaluation — installs cleanly and behaves as described in the markdown.
standards reduced setup friction for our internal harness; good balance of opinion and flexibility.
standards fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 71