菜单
Routes analysis and debugging tasks. Triggers on analyze, debug, troubleshoot, review, audit, security, performance, optimize, investigate, trace.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill whenever the user wants high-quality semantic retrieval, cross-textbook synthesis, reference verification, or authority-ranked question answering over the PageIndex corpus. Trigger on requests like "find which texts cover X", "compare sources", "retrieve semantically", "verify this claim from my textbooks", "build a reading list from the corpus", "cluster by topic", or any PageIndex question where naïve filename search would miss relevant material. This skill teaches a state-of-the-art hybrid retrieval workflow over the PageIndex catalog and live MCP extraction surface.
Build complex AI systems with declarative programming, optimize prompts automatically, create modular RAG systems and agents with DSPy - Stanford NLP's framework for systematic LM programming. Use when you need to build complex AI systems, program LMs declaratively, optimize prompts automatically, create modular AI pipelines, or build RAG systems and agents.
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
Real-time observability dashboard for multi-agent Claude Code sessions. Visualize agent interactions, tool usage, and session flows in real-time through a web dashboard. Track multiple agents running in parallel with swim lane visualization, event filtering, and live charts. **Key Features:** - 🔴 Real-time event streaming via WebSocket - 📊 Agent swim lanes showing parallel execution - 🔍 Event filtering by agent, session, event type - 📈 Live charts for tool usage patterns - 💾 Filesystem-based (no database required) **Inspired by [@indydevdan](https://github.com/indydevdan)**'s work on multi-agent observability. **Our approach:** Filesystem + in-memory streaming vs. indydevdan's SQLite database approach.
Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.
Routes tasks to appropriate Task tool agents (subagents). Triggers on complex multi-step tasks, research, code review, exploration, or any task benefiting from specialized agent execution. Matches intent to agent types.
| name | analysis-router |
| description | Routes analysis and debugging tasks. Triggers on analyze, debug, troubleshoot, review, audit, security, performance, optimize, investigate, trace. |
Routes analysis, debugging, and review tasks to specialized skills.
triggers: [analyze, review, understand, trace, flow, structure]
skills:
- sc:analyze: Code quality, security, performance, architecture analysis
- systematic-debugging: Structured debugging approach
triggers: [security, audit, vulnerability, injection, auth, permissions]
skills:
- dev:security:security-audit: Security vulnerability scanning
- dev:security:secure-prompts: Prompt injection defense
- dev:security:check-best-practices: Security best practices
triggers: [performance, optimize, bottleneck, profiling, memory, speed]
skills:
- sc:improve: Systematic improvements
- parallel-debug-orchestrator: Parallel debugging
triggers: [architecture, design, patterns, refactor, structure]
skills:
- dev:architecture:explain-architecture-pattern: Pattern explanation
- sc:design: System design
analysis request
│
├── Security focus?
│ ├── Audit? → security-audit
│ ├── Prompts? → secure-prompts
│ └── Best practices → check-best-practices
│
├── Performance focus?
│ ├── Debugging? → parallel-debug-orchestrator
│ └── Optimization → sc:improve
│
├── Architecture focus?
│ └── explain-architecture-pattern
│
└── General analysis?
├── Debugging? → systematic-debugging
└── Review → sc:analyze
| Skill | Purpose | Trigger |
|---|---|---|
| sc:analyze | Code analysis | "analyze code", "review" |
| systematic-debugging | Structured debug | "debug", "troubleshoot" |
| parallel-debug-orchestrator | Parallel debug | "complex bug", "multiple issues" |
| security-audit | Security scan | "security audit", "vulnerabilities" |
| secure-prompts | Prompt security | "prompt injection", "secure prompts" |
| sc:improve | Improvements | "improve", "optimize" |