Loading...
Loading...
Found 123 Skills
Research codebase comprehensively using parallel sub-agents to answer user questions. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
Review a single file or all files in a folder for data inconsistencies, reference errors, typos, and unclear terminology using parallel sub-agents
Use when you have 2+ tasks that Codex agents should execute. Runtime-native: Codex sub-agents when available, Codex CLI fallback otherwise. Handles file conflicts via merge/wave strategies. Triggers: "codex team", "spawn codex", "codex agents", "use codex for", "codex fix".
Use this skill when creating new Claude Code skills from scratch, editing existing skills to improve their descriptions or structure, or converting Claude Code sub-agents or slash commands to skills. This includes designing skill workflows, writing SKILL.md files, organizing supporting files with intention-revealing names, and leveraging CLI tools and appropriate scripting.
Execute complex tasks through sequential sub-agent orchestration with intelligent model selection, and LLM-as-a-judge verification
Управление сессиями AI агентов через agent-deck CLI. Триггеры (RU): "запусти агента", "запусти саб-агента", "создай сессию", "проверь сессию", "проверь статус", "покажи вывод агента", "что агент ответил". Triggers (EN): "launch sub-agent", "create sub-agent", "start session", "check session", "show agent output".
Sets up Claude Code agent teams with role-based composition. Use when creating dev teams, defining team roles, or organizing multi-agent collaboration. Do NOT use for single sub-agent creation (use agent-creator instead).
Deep EVM smart contract security audit system. Use when asked to audit a contract, find vulnerabilities, review code for security issues, or file security issues on a GitHub repo. Covers 500+ non-obvious checklist items across 19 domains via parallel sub-agents. Different from the security skill (which teaches defensive coding) — this is for systematically auditing contracts you didn't write.
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. For exploratory or ambiguous requests where the user is unsure what to do, prefer ce-brainstorm first.
Design a module's interface using parallel sub-agents producing radically different designs ("design it twice"). Compare on depth, simplicity, and efficiency. Embedded grill on the synthesized choice. Use when designing a new API, exploring interface options, or deciding the shape of a refactor before writing code.
Novel Logic/Plot Review, applicable to user requests such as "Help me check if there are bugs in my novel", "Check if there are timeline contradictions", "Check if characters are OOC", "Find plot conflicts between different parts", "Sort out whether foreshadowings are resolved", "Check the rationality of novel plots", "Check if there are plot loopholes", "Character behaviors are inconsistent with their personalities", "Check if the timeline is correct", "Find contradictions in the novel", "Help me sort out all foreshadowings", "Novel plot bug check", "Logical loophole troubleshooting", etc. It detects issues such as timeline conflicts, logical loopholes, character OOC, and missing foreshadowings. **Performs word count checks to ensure chapter word counts meet standards**, **generates a detailed issue list and automatically fixes all issues, with the fixed results directly modifying the chapters/ directory and automatically backing up the original files to .sumeru/write/original/ before modification**, **uses sub-Agents for parallel processing during batch review, with each Agent responsible for a maximum of 3 chapters**
Use when tasks are complex and require full microservices collaboration: The main agent acts as a pure Orchestrator, strictly prohibited from writing code personally, and is responsible for accurately assigning responsibilities such as positioning, planning, coding, testing, and review to corresponding sub-agents (explorer, planner, worker, verifier, reviewer, fixer). This Skill enforces microservices workflow discipline, requiring full Chinese communication, minimal routing output, and minimized context transfer.