Loading...
Loading...
Found 5,142 Skills
Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude" or "/wiki-history-ingest codex", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history skill.
Analyze codebase with parallel mapper agents to produce .planning codebase documents
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Use before EVERY npm publish. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
Use when the user wants to update, refresh, or reinstall the CopilotKit agent SKILLS (the SKILL.md files that teach this agent about CopilotKit). NOT for updating the CopilotKit codebase or project — this is specifically about refreshing the skills/knowledge this agent has loaded. Triggers on "update copilotkit skills", "update skills", "refresh skills", "skills are stale", "skills are outdated", "get latest skills", "my copilotkit knowledge is wrong", "copilotkit APIs changed", "skills seem old", "wrong API names", "reinstall skills", "skills not working right", "update your copilotkit knowledge".
Run agency-orchestrator YAML workflows directly in Claude Code / OpenClaw / Cursor — no API key required, using the current session's LLM as the execution engine. Triggered when the user provides a .yaml workflow file or requests multi-role collaboration to complete a task.
MUST be used whenever creating an AtlasTool (client-side tool) for an Atlas agent. Do NOT manually write AtlasTool definitions or wire them into useAtlasChat — this skill handles the TypeBox schema, execute function, and hook wiring. This includes tools that fetch data, render UI, call APIs, show charts, query local state, or perform any browser-side action. Triggers: AtlasTool, client tool, add tool, create tool, new tool, tool definition, agent tool.
MUST be used whenever building a chat UI with Atlas agents in a Dune app. Do NOT manually write useAtlasChat integration code — this skill handles installation, component structure, and hook wiring. Triggers: useAtlasChat, atlas chat, streaming chat, agent chat, chat interface, chat component, chat UI. For a full chat app, run skills in order: (1) integrate-atlas-chat, (2) create-client-tool (per tool), (3) setup-python-tools (if Python tools needed).
Systematic debugging for ADK agents — trace reading, log analysis, common failure diagnosis, and the debug loop.
Nassim Taleb's Antifragility framework applied to a business idea, system, or portfolio position. Spawns a team of specialist agents — Fat-Tail Detector, Fragility Auditor, Optionality Scout, Iatrogenics Checker, Skin-in-the-Game Auditor — who each apply a distinct lens from Taleb's Incerto to evaluate whether the subject is fragile, robust, or antifragile. The lead synthesizes into a convexity assessment: what's the payoff structure under disorder, where are the hidden tail risks, and the honest Taleb verdict. Use when the user says "taleb this", "is this fragile", "antifragility analysis", "what would Taleb think", "tail risk check", or proposes a business/system and wants structural risk analysis. Works standalone or after /munger for complementary analysis.
Claude Shannon's Six Techniques for Creative Problem Transformation. Spawns a team of specialist agents — Simplifier, Analogist, Reframer, Decomposer, Inverter — who each apply one of Shannon's problem-solving techniques to your stuck problem. The lead synthesizes into a transformation assessment: which reframings opened paths, which analogies map, and the honest Shannon verdict on whether the problem has been cracked open. Use when stuck on any problem — engineering, strategy, design, math, business. Works standalone or after other analysis skills surface a hard sub-problem.
Charlie Munger's Mental Lattice applied to a business idea. Spawns a team of specialist agents — Mathematician, Psychologist, Inverter, Economist, Moat Analyst — who each apply their discipline's elementary models to the idea. The lead synthesizes into a lollapalooza analysis: which forces stack, which fight you, and the honest Munger verdict. Use when the user says "munger this", "apply the lattice", "what would Charlie think", or proposes a business idea and wants multidisciplinary analysis. Works as a standalone analysis or after /office-hours.