Loading...
Loading...
Found 138 Skills
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.
One-click comprehensive analysis of a stock/company. Collect data from five dimensions - stock price, news sentiment, industry comparison, market environment, and official company website - simultaneously through parallel sub-agents, then conduct cross-analysis, causal attribution, and trend prediction in the main thread, and output a standardized analysis report. Trigger words: Analyze XX stock, analyze TICKER, How is XX, Is XX worth buying? Supports A-shares and U.S. stocks.
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.
Multi-model consensus council for validation, research, and brainstorming. Spawns parallel judges with configurable perspectives and optional explorer sub-agents using runtime-native backends (Codex sub-agents or Claude teams). Modes: validate, brainstorm, research. Triggers: council, validate, brainstorm, critique, research, analyze, multi-model, consensus.
Stay current with how OpenCode, OpenAI Codex, and Claude Code implement extensibility features (skills, slash commands, subagents, custom prompts). Use when comparing implementations across AI coding assistants, researching how a specific tool implements a feature, or syncing knowledge about agent extensibility patterns. Triggers include questions like "how does X implement skills?", "compare slash commands across tools", "what's the latest on Claude Code sub-agents?", or requests to understand agent extensibility approaches.
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).
Explore a codebase for architectural friction, discover refactoring opportunities, and propose module-deepening refactors as GitHub issue RFCs. Uses friction-driven exploration and parallel sub-agents to design multiple interface alternatives. Use when user wants to improve architecture, find refactoring opportunities, consolidate coupled modules, reduce complexity, make code more testable, or review codebase health.
Semantic search, context management, and document indexing via OpenViking. Use when the user asks to: index/import documents or files into a knowledge base, perform semantic search across indexed content, browse or explore indexed resources, get summaries/overviews of indexed documents, manage an OpenViking instance, or integrate structured context retrieval into workflows. Also use when sub-agents need to retrieve relevant context from a large document collection.
Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop
Agent-based declarative testing with YAML test specs. Tests run in sub-agents to preserve main context while executing many tests. Supports MCP servers, APIs, and browser automation. Use when: testing MCP servers, running integration tests, validating tool behavior after changes, or creating regression test suites. Keywords: yaml tests, agent testing, mcp test, integration tests.
Run OpenCode CLI for code generation, analysis, and development tasks. Uses OAuth authentication. Use for rapid prototyping, code refactoring, testing, and automation. Preferred for load balancing sub-agent work (35% weight).
Scans all skill directories in the repository to generate a comprehensive global map of agent capabilities, inputs, and outputs. Use when you need to understand the full potential of your agent library or when a master agent needs to decide which sub-agent skill to invoke for a complex task.