Loading...
Loading...
Found 11,954 Skills
Initialize a Harness Engineering framework in the current project. Use when user says 'harness', 'init harness', 'initialize framework', 'setup harness engineering', '/harness', or wants to set up a Plan-Build-Verify development workflow with specialized agents (planner, generator, evaluator). Creates CLAUDE.md, agent definitions, command templates, hooks, and documentation structure for autonomous AI-driven development.
Use when the user wants to pair PocketClaw, install or upgrade ClawPilot, verify host runtime readiness, and generate a pairing code for OpenClaw, Hermes, or cc-connect Coding Agent hosts. Follow a strict pairing workflow and output the final pairing code on its own line when successful.
Guide users through installing and setting up `todoing` — the local, git-friendly CLI task manager. Use this when the user asks to install todoing, set up todoing, configure todoing for their project, or wants to start using todoing for task management. Also use this when onboarding AI agents to use todoing — including adding agent instructions to project config files like AGENTS.md or CLAUDE.md.
Persist and restore agent sessions across conversations with state snapshots
Crypto wallet API + CLI for AI agents — install, authentication, and routing to specific Zerion capabilities. Use this skill for setup or to learn which `zerion-*` skill applies; deep-dive skills handle individual capabilities (analyze, trade, sign, manage wallets, manage agent tokens).
Runs an autonomous delivery loop from an existing PRD to implementation, issue triage, per-slice verification, and final repo validation. Use when the user has already created or approved a PRD and asks to automate to-issues, tickets, triage, ready-for-agent implementation, validation, or production-ready completion.
The CLI for the public API directory at postman.com/explore — search, rank, and watch community-contributed Postman Collections, agent-native and offline. Trigger phrases: `find a postman collection for`, `what postman collection should i fork for`, `is there a postman collection for`, `browse postman api network`, `compare postman publishers`, `what changed on the postman network`, `use postman-explore`, `run postman-explore`.
Context scoping for writing agent spawns — use when deciding what context a spawned agent should receive, whether ephemeral story decisions should be materialized before handoff, and how much to pass. Poor context handoffs cause writers to invent contradictions and critics to miss relevant history.
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).
This skill should be used when the user wants to run baseline evaluations on existing agent skills, regenerate transcripts after a model upgrade, or check whether a skill still solves the gap it was authored for. Common triggers include "rerun the baselines", "re-eval skill X", "test all the skills", "check for skill drift", and "run the evals". Bakes in verbatim transcript capture (no paraphrasing), deterministic-only grading (regex / contains / file_exists — no LLM-as-judge), and the iteration-N workspace convention. Skip when authoring a new skill (use skill-creator) or modifying skill content directly.
Compress agent-facing instructions to the fewest words that preserve behavior, constraints, and clarity.
Translate Figma designs into production-ready code with 1:1 visual fidelity. Useful for handing off Figma frames straight to a frontend agent.