Loading...
Loading...
Found 209 Skills
Watch for the 11 known AI-coding-agent failure modes (fabrication, scope_creep, security_vulnerability, etc.) — consult this skill before edits, dependency adds, completion claims, or anything that could trip a known supervision concern. Quote the snake_case failure-mode ids verbatim when flagging risks.
The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code. NOT for: Running Archon CLI workflows in worktrees (use /archon instead).
Portable OKF knowledge bundle for coding-agent memory and LLM wikis. Use when the user wants to start a wiki, ingest a source, document a repository, query project knowledge with citations, lint for drift, or visualize connections; whenever a repo has a knowledge/ bundle that should inform the task; and when another kb-* skill needs the shared spec, glossary, templates, or trust model.
interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow
Invoke external coding-agent harnesses non-interactively with an explicit model, working directory, prompt, and safety policy. Use when delegating work to Codex, Claude Code, Grok, OpenCode, Cursor CLI, GitHub Copilot CLI, or Cockpit, including from planning or review loops.
Guide for adding new AI SDK harness packages. Use when creating a new @ai-sdk/harness-<name> package that adapts a coding-agent runtime to HarnessV1.
Authoritative reference for Pi (@earendil-works/pi-coding-agent): install, configure, run, and extend. Use when the user asks about Pi CLI/flags/commands, providers/models/auth, settings/compaction/sessions, security/trust, extensions, skills, prompt templates, themes, packages, custom providers, TUI components, the SDK, RPC mode, or JSON streaming. Also use for Pi's design philosophy and opinionated choices (why minimal, 4 tools, YOLO, no MCP/plan mode/to-dos/sub-agents), the creator Mario Zechner's coding-agent blog post, Pi's internal monorepo architecture (the Chord plugin/service runtime (@earendil-works/chord), the agent harness, facets/services, delta tracking), and the repository's build, development, and contribution rules.
Score any AI model on the DeepSWE coding-agent benchmark via the OpenRouter API. Use when the user wants an independent, reproducible coding-agent eval — "run DeepSWE", "benchmark this model on DeepSWE", "score model X on the coding benchmark", "test a model via OpenRouter on DeepSWE", or to verify vendor-reported coding scores. Covers setup, the OpenRouter wiring for mini-swe-agent, single-task / subset / full 113-task runs, and leaderboard submission.
Set up or audit a machine's coding-agent harnesses from one rule table and the user's workstation repo - the shared global instructions every harness reads, the global rules (deny, ask, allow-and-report) each one enforces, the pre-tool hook, memory kept off, declared Codex CLI defaults, and the skills and tools the workstation repo lists to install. Use for a new machine or VPS, to audit this machine's agent setup, or when another skill says to check the machine.
Reconstructs or writes a coding-agent handoff from git and `.agents/handoff.md`. Use when the user is about to switch coding agents (Claude Code, Cursor, Codex, Antigravity), a usage limit expired, or a new agent is picking up in-progress work.
Use when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation, saved artifact set, or session summary, on any platform (Claude Code, Codex, Cursor, Antigravity, OpenCode) or across several platforms in one ask, such as reviewing threads across Claude and Codex.
Render a token-usage stat card from local Claude Code, Codex, Gemini CLI, and OpenCode session logs and commit it into the repository as a file. Use when someone wants a current usage figure in a README, or asks for a shareable card of their coding-agent activity.