standards

boshu2/agentops · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/boshu2/agentops --skill standards
0 commentsdiscussion
summary

Language-specific coding standards loaded on-demand by other skills.

skill.md

Standards Skill

Language-specific coding standards loaded on-demand by other skills.

Purpose

This is a library skill - it doesn't run standalone but provides standards references that other skills load based on file types being processed.

Standards Available

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

How It Works

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.

Domain-Specific Checklists

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.

Deep Standards

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

Integration

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 recommendations

Examples

Vibe Loads Python Standards

User says: /vibe (detects changed Python files)

What happens:

  1. Vibe skill checks git diff for file types
  2. Vibe finds auth.py in changeset
  3. Vibe loads standards/references/python.md automatically
  4. Vibe validates against Python standards (type hints, docstrings, error handling)
  5. Vibe reports findings with standard references

Result: Python code validated against language-specific standards without manual reference loading.

Implement Loads Go Standards

User says: /implement ag-xyz-123 (issue modifies Go files)

What happens:

  1. Implement skill reads issue metadata to identify file targets
  2. Implement finds server.go in implementation scope
  3. Implement loads standards/references/go.md for context
  4. Implement writes code following Go standards (error handling, naming, package structure)
  5. Implement validates output against loaded standards before committing

Result: Go code generated conforming to standards, reducing post-implementation vibe findings.

Troubleshooting

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

Reference Documents

how to use standards

How to use standards on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add standards
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/boshu2/agentops --skill standards

The skills CLI fetches standards from GitHub repository boshu2/agentops and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/standards

Reload or restart Cursor to activate standards. Access the skill through slash commands (e.g., /standards) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.671 reviews
  • Mateo Abbas· Dec 24, 2024

    standards reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Anika Jain· Dec 24, 2024

    standards is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Dhruvi Jain· Dec 20, 2024

    Keeps context tight: standards is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Meera Tandon· Dec 12, 2024

    standards has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anaya Perez· Dec 12, 2024

    Keeps context tight: standards is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Meera Shah· Nov 23, 2024

    Useful defaults in standards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Valentina Liu· Nov 15, 2024

    standards is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Oshnikdeep· Nov 11, 2024

    Registry listing for standards matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Soo Srinivasan· Nov 11, 2024

    standards reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Michael Kim· Nov 3, 2024

    standards fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 71

1 / 8