boshu2/agentops

Two-level beads architecture and routing. Understanding where beads live, how prefix routing works, and when to use BEADS_DIR. Critical for Mayor understanding which database to use for different work types.

This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what''s ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.

This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn''t work", "failing", "investigate bug".

Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".

Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".

Gold standard for code-map feature documentation. Use when generating docs in docs/code-map/ or running /doc on CODING repositories.

Use when: "code review", "review", "PR review", "test", "testing", "unit test", "integration test", "test generation", "coverage", "quality", "maintainability", "security review", "edge cases".

Analyze code complexity and find refactor targets using radon/gocyclo. Triggers: "complexity", "analyze complexity", "find complex code", "refactor targets", "cyclomatic complexity", "code metrics".

Analyze code complexity and find refactor targets using radon/gocyclo

Analyze code complexity and find refactor targets using radon/gocyclo

This skill should be used when the user asks to "build container", "create Dockerfile", "configure podman", or needs guidance on OpenShift container images, arbitrary UIDs, or image tagging.

Fully autonomous epic execution. Runs until ALL children are CLOSED. Loops through beads issues, runs /implement on each, validates with /vibe. NO human prompts, NO stopping.

Crew workspace management. Understanding and managing persistent human-guided workspaces in Gas Town. Covers lifecycle, workspace operations, and when to use crew vs polecats.

Use when: "data pipeline", "ETL", "Spark", "dbt", "Airflow", "data warehouse", "analytics", "machine learning", "ML", "model", "PyTorch", "TensorFlow", "MLOps", "MLflow", "Kubeflow", "feature engineering", "A/B testing".

Use when: "API", "backend", "frontend", "fullstack", "mobile", "iOS", "React Native", "Flutter", "deploy", "CI/CD", "Docker", "Kubernetes", "GitHub Actions", "LLM", "RAG", "prompt engineering", "microservices", "database schema", "SwiftUI".

Unified dispatch for Gas Town work assignment. Covers gt sling (assign work), gt hook (attach work), gt convoy (batch tracking), and the Propulsion Principle. This is THE skill for understanding how to dispatch work to agents.

This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.

This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.

This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.

This skill should be used when the user asks to "create documentation", "write a corpus document", "create a standard", "add corpus content", "write GraphRAG documentation", or mentions corpus/standards documentation.

Use when: "document", "docs", "README", "API docs", "OpenAPI", "Swagger", "Diátaxis", "tutorial", "how-to", "reference", "explanation", "SDK", "developer docs", "knowledge OS", "7-pattern stack".

Extract decisions and learnings from Claude session transcripts. Triggers: "extract learnings", "process pending", SessionStart hook.

Spawn Agent Farm for parallel issue execution. Mayor orchestrates crew via tmux + MCP Agent Mail. Replaces /crank for multi-agent work. Triggers: "farm", "spawn agents", "parallel work", "multi-agent".

Knowledge flywheel health monitoring. Checks velocity, pool depths, staleness. Triggers: "flywheel status", "knowledge health", "is knowledge compounding".

Mine transcripts for knowledge - decisions, learnings, failures, patterns. Triggers: "forge insights", "mine transcripts", "extract knowledge".

Gas Town status and utility operations. Check convoy progress, peek into polecats, nudge stuck workers, cleanup completed work. For autonomous execution, use /crank.

Execute safe, reproducible Git workflows with MANDATORY semantic commits (feat/fix/docs), auto-injected templates, and git hooks integration

Create structured handoff for session continuation. Triggers: handoff, pause, save context, end session, pick up later, continue later.

Execute a single beads issue with full lifecycle. Triggers: "implement", "work on task", "fix bug", "start feature", "pick up next issue".

Execute a single beads issue with full lifecycle. Triggers: "implement", "work on task", "fix bug", "start feature", "pick up next issue".

Parallel execution of multiple issues. Triggers: "run a wave", "parallel implementation", "batch execute", "implement in parallel".

Inject relevant knowledge into session context from .agents/ artifacts. Triggers: "inject knowledge", "recall context", SessionStart hook.

Query knowledge artifacts across all locations. Triggers: "find learnings", "search patterns", "query knowledge", "what do we know about", "where is the plan".

Use when: "Python", "Go", "Golang", "Rust", "Java", "TypeScript", "shell script", "bash", "async/await", "goroutines", "ownership", "virtual threads", "type system", "decorators", "generators", "channels", "interfaces", "Spring Boot", "POSIX".

Agent communication patterns. Send mail, check inbox, broadcast to workers, nudge stuck polecats, and escalate to humans when needed.

Repository maintenance utilities. Use for "audit docs", "cleanup repo", "check documentation structure", "remove deprecated", "audit workflow", "clean old plans", "check onboarding docs".

Use when: "context", "session", "multi-agent", "workflow", "memory", "persistence", "retrospective", "retro", "patterns", "learnings", "stigmergy", "autonomous", "coordination", "observer", "blackboard".

Use when: "monitoring", "observability", "metrics", "tracing", "OpenTelemetry", "alerts", "runbooks", "SLO", "SLI", "dashboards", "Prometheus", "Grafana", "performance", "latency", "throughput", "Core Web Vitals", "load testing".

Use when: "incident", "outage", "production issue", "debug", "logs", "error", "postmortem", "root cause", "triage", "escalation", "P0", "P1", "on-call", "mitigation", "rollback".

Scaffold and audit OSS documentation for open source projects. Triggers: "add OSS docs", "create README", "setup contributing", "add changelog", "missing SECURITY.md", "oss documentation", "prepare for open source", "github templates", "add AGENTS.md".

Scaffold and audit OSS documentation for open source projects. Triggers: "add OSS docs", "create README", "setup contributing", "add changelog", "missing SECURITY.md", "oss documentation", "prepare for open source", "github templates", "add AGENTS.md".

This skill should be used when the user asks to "create a plan", "plan implementation", "break down into tasks", "decompose into features", "create beads issues from research", "what issues should we create", "plan out the work", or needs to convert a goal into executable beads issues.

Epic decomposition into trackable issues. Triggers: "create a plan", "plan implementation", "break down into tasks", "decompose into features", "create beads issues from research", "what issues should we create", "plan out the work".

Polecat worker lifecycle management. Covers spawning polecats (gt sling), resetting them for reuse, nuking completed workers, and garbage collecting stale branches. For Witness and Mayor roles primarily.

Comprehensive post-implementation validation. Combines retro (learnings), vibe (code validation), security scanning (Talos), and knowledge extraction into a single unified workflow. Triggers: "post-mortem", "validate completion", "final check", "wrap up epic", "close out", "what did we learn".

Fork-based implementation with isolation check. Runs isolation check from pr-prep Phase 0 before starting work. Triggers: "implement PR", "implement contribution", "pr implement", "fork implementation".

Systematic upstream codebase exploration for open source contribution. Outputs research artifact with contribution guidelines, PR patterns, maintainer expectations, and open issues. Triggers: "pr research", "upstream research", "contribution research", "open source prep".

Pre-mortem simulation for specs and designs. Simulates N iterations of implementation to identify failure modes before they happen. Triggers: "pre-mortem", "simulate spec", "stress test spec", "find spec gaps", "simulate implementation", "what could go wrong", "anticipate failures".

Create lightweight product brief (PR/FAQ) that articulates customer need, success criteria, and scope before engineering decomposition. Triggers: "product brief", "customer value", "who is this for", "PR/FAQ", "working backwards", "define success", "scope this".

Trace knowledge artifact lineage and sources. Find orphans, stale citations. Triggers: "where did this come from", "trace this learning", "knowledge lineage".

Brownian Ratchet progress gates for RPI workflow. Check, record, verify. Triggers: "check gate", "verify progress", "ratchet status".

Deep codebase exploration. Triggers: "research", "explore", "investigate", "understand", "deep dive", "current state".

Deep codebase exploration. Triggers: research, explore, investigate, understand, deep dive, current state.

Deep codebase exploration. Triggers: "research", "explore", "investigate", "understand", "deep dive", "current state".

Extract learnings from completed work. Trigger phrases: "run a retrospective", "extract learnings", "what did we learn", "capture lessons", "create a retro".

Extract learnings from completed work. Trigger phrases: "run a retrospective", "extract learnings", "what did we learn", "capture lessons", "create a retro".

Understanding Gas Town role responsibilities. Clarifies when Claude should behave as Mayor, Crew, Polecat, Witness, or Refinery.

Use when: "security", "penetration test", "pentest", "vulnerability", "OWASP", "network", "firewall", "SSL", "TLS", "DNS", "load balancer", "CDN", "encryption", "authentication", "authorization", "secrets".

Use when: "accessibility", "WCAG", "a11y", "customer support", "FAQ", "tickets", "UI", "UX", "design system", "wireframe", "Obsidian", "knowledge graph", "links", "task decomposition", "workflow", "risk assessment", "edge cases", "failure modes".

Library skill providing language standards, style guides, and best practices. Not invoked directly - other skills reference these docs.

Language-specific coding standards and validation rules. Provides Python, Go, TypeScript, Shell, YAML, JSON, and Markdown standards. Auto-loaded by /vibe, /implement, /doc, /bug-hunt, /complexity based on file types.

TypeScript coding standards. Library skill - loaded by other skills, not invoked directly.

Shell scripting standards. Library skill - loaded by other skills, not invoked directly.

Go coding standards. Library skill - loaded by other skills, not invoked directly.

Python coding standards. Library skill - loaded by other skills, not invoked directly.

Quick status check of current work state. Use when the user asks "what's my status", "show status", "where am I", "current state", or needs a snapshot of active work, ready issues, and git state.

Scan Python codebases to identify modules without corresponding test files. This skill should be used when enforcing Law 7 (TDD), auditing test coverage gaps, or before starting new development to understand testing debt. Outputs a report of untested modules with recommendations.

Execute testing workflows including unit tests, manifest validation, security scanning, and integration tests with proper reporting

Meta skill explaining the AgentOps workflow. Auto-injected on session start. Covers RPI workflow, Knowledge Flywheel, and skill catalog.

Use when: "validate", "verify", "assumption", "test strategy", "tracer bullet", "smoke test", "continuous validation", "environment check", "reality check", "deployment validation", "pre-flight".

This skill should be used when the user asks to "validate changes", "run validation gate", "check before merge", "quality check", or needs comprehensive validation across security, quality, and architecture.

This skill should be used when the user asks to "validate changes", "run validation gate", "check before merge", "quality check", or needs comprehensive validation across security, quality, and architecture.

Talos-class comprehensive code validation. Use for "validate code", "run vibe", "check quality", "security review", "architecture review", "accessibility audit", "complexity check", or any validation need. One skill to validate them all.

Validate documentation claims against deployment reality. Use when checking if docs accurately describe what's deployed, finding false claims, or auditing doc accuracy. Triggers: "verify docs", "doc audit", "check doc claims", "docs match reality", "validate doc status".

Validate documentation claims against deployment reality. Use when checking if docs accurately describe what's deployed, finding false claims, or auditing doc accuracy. Triggers: "verify docs", "doc audit", "check doc claims", "docs match reality", "validate doc status".