Loading...
Loading...
Found 13,566 Skills
ERC-8004 identity, reputation, and validation — register identities, retrieve identity info by agent ID, query reputation scores, submit peer feedback, and request or check third-party validation status.
Guides the agent through Capgo account lookup and organization administration. Use when listing organizations, managing members, changing security settings, or working with organization-level CLI commands. Do not use for OTA bundle uploads or native builds.
Auto-assembles review panel using deterministic rules, dispatches agents against plan file, collects verdicts.
Extracts the full design soul, system, and agent rules from reference UI images. Use this skill when the user provides screenshots, Figma exports, or any UI reference images and wants the agent to design with the same soul, taste, feeling, and personality — not just copy colors and spacing. Marrow reads beneath the surface: it extracts the living core of a design — the decisions, proportions, restraint, and emotional intent that make a UI feel the way it does. Triggers on: /marrow, /extract-ui, /design-from-ref, /read-design, or any prompt like "extract the design system from these images", "make it look and feel like this", "get the rules from this UI", "build with the same soul", "match this design". Always use this skill when images are provided alongside a request to replicate, match, or be inspired by a design.
Use when you need multi-agent orchestration for OpenAI Codex CLI. Triggers on: omx, $plan, $ralph, $team, $autopilot, $deep-interview. v0.11.10 — 30+ agents, 35+ workflow skills, tmux team runtime, sparkshell, explore, ralplan.
Design domain-specific agent teams, define specialized agents, and generate the skills they use. Use when you need to decompose a complex project into coordinated multi-agent teams, choose the right architecture pattern (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation), generate .claude/agents/ and .claude/skills/ files, or validate and iterate on generated harnesses. Triggers on: harness, build a harness, design agent team, agent team architecture, multi-agent skill generation, set up harness, harness engineering, domain agent team, harness for this project.
Launch Loki Mode autonomous SDLC agent. Handles PRD-to-deployment with minimal human intervention. Invoke for multi-phase development tasks, bug fixing campaigns, or full product builds.
An advanced SEO agent skill for deep, comprehensive single-page SEO audits. Performs full technical SEO analysis, on-page SEO review, structured data validation, content quality assessment, and canonical/crawlability checks. Outputs an advanced full SEO audit report. Use when the user says "deep audit", "advanced audit", "technical SEO audit", "full SEO audit", "full report", "key report", "comprehensive SEO review", or explicitly asks for more than a basic check. Powered by OpenClaw and Claude.
Guide for creating agent skills that follow the Agent Skills specification. Use when user wants to create, write, draft, or improve a skill. Covers structure, description optimization, progressive disclosure, scripts, and evaluation.
Use when user needs expert help, wants to summon a specialist, says "help me with", "I need guidance", or has a task requiring domain expertise. Creates and manages a growing collection of expert agents.
How to write Cavekit-quality kits that AI agents can consume effectively. Covers implementation-agnostic cavekit design, testable acceptance criteria, hierarchical structure, cross-referencing, cavekit templates, greenfield and rewrite patterns, cavekit compaction, and gap analysis. Trigger phrases: "write kits", "create kits", "cavekit this out", "define requirements for agents", "how to write kits for AI"
Plan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, implement, execute the spec, or tackle a specific §T task (`build §T.3`, `build --next`, `implement next task`, `run the build`). Expects SPEC.md to exist; if not, defers to the spec skill.