Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
Tutor the user through a source file with a cached summary, a guided walkthrough, and free-form Q&A — then persist a review record so future quizzes know what was covered.
This skill teaches Claude Code how to write detection rules for the AI Traffic Control rule engine. Read this before creating or modifying anything in rules/. The full rule schema is Rule in packages/schema/src/zod/rule.ts — it is the source of truth for every field below.
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder…
Migrate community plugins from Claude Code, Codex, or Skills.sh into AgentPlugins. Use when the user wants to convert a plugin they wrote or found into the AgentPlugins v1 manifest format so it can be installed via agentplugins add or agentplugins import.
Design, generate, audit, or revise minimal validation-driven AI agent packs for Codex, Claude Code, and Claude skills from project descriptions, README files, specs, existing workflows, or repository evidence. Use when creating or improving AGENTS.md, CLAUDE.md, context routers, primary workflow agents, reviewers…
Use when a user asks an agent to inspect, refine, or generate an API/oRPC/OpenAPI contract from website recordings captured by the Harpist Chrome extension. Covers using the published harpist npm CLI through bunx/npx, avoiding sandboxed execution, starting or reusing the local Harpist bridge, syncing extension…
Error handling patterns for Go including error wrapping, custom errors, sentinel errors, and error checking best practices. Use when implementing error handling, defining error types, or working with error flows.
Generate comprehensive Drupal migration plans with entity mapping, ETL strategies, rollback procedures, and source analysis based on best practices from the Drupal migration guide.
Query-first indexing and retrieval for Operator OS memory. Use when asked to find prior context, search memory, rebuild the memory index, or answer from the workspace without loading large files by default.
Tiered architecture-decision orchestrator — evaluates trade-offs and produces ADRs or system designs through discover, research, design, and adversarial-review phases. Use for architecture decisions, ADRs, system design, trade-off analysis between approaches, one-way-door decisions, C4-level design, or NFR evaluation…
Initialize a repository by analyzing its structure and generating AGENTS.md and structured docs/, enabling AI coding agents (Claude Code, Codex, Cursor, etc.) to operate safely, deterministically, and with minimal human supervision.
Use only in coordinator sessions to orchestrate planning or execution of work, including execute, continue, or resume-plan requests. Covers role definition, specialist discovery, dispatch, review, learning, and synthesis. Never use in Session type: DELEGATED executor sessions; those agents perform their handed scope…
Review the current diff against this team's conventions and invariants before it ships. Invoke with /prereview before opening a PR, or run as a pre-push gate.
Use when an MCP server exposes nil tools (a NILScript / Network Intent Layer gate to a backend) — teaches the propose→approve→commit→rollback discipline, reversibility tiers, and how to read refusals so an agent drives any NIL backend safely and correctly.
★not rated 9 1mo agoA60 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: