copilot-cli
Use when you need to run or troubleshoot GitHub Copilot CLI (npx @github/copilot), including sessions, permissions (--allow-tool/--deny-tool), MCP management (/mcp), or Copilot CLI agents.
Use when you need to run or troubleshoot GitHub Copilot CLI (npx @github/copilot), including sessions, permissions (--allow-tool/--deny-tool), MCP management (/mcp), or Copilot CLI agents.
Git-native issue tracking with first-class dependency support. Issues stored alongside code in .beads/ directory, dual-persisted in SQLite (queries) and JSONL (git-friendly history). Hash-based IDs, DAG dependencies, daemon mode with RPC, and LSP-inspired multi-workspace support.
Analyze OSS solutions for code quality, documentation, and best practices using Context7, DeepWiki, and Perplexity. Use when users request repository analysis, code review, library documentation lookup, or need insights about GitHub projects and open-source technologies.
Flush and sync Beads changes to git (export/commit/pull/import/push)
Skill para manejar el flujo de trabajo de Git: changelog, commits, push, y releases. Automatiza el proceso de versionado y publicación.
Production monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics, traces, on-call, production monitoring, health checks, uptime, availability, dashboards, post-mortem, incident management, runbook. Completes SDD Stage 8 (Monitoring) with comprehensive production observability: - SLI/SLO definitions and tracking - Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.) - Alert rules and notification channels - Incident response runbooks - Observability dashboards (logs, metrics, traces) - Post-mortem templates and analysis - Health check endpoints - Error budget tracking Use when: user needs production monitoring, observability platform, alerting, SLOs, incident response, or post-deployment health tracking.
Routes analysis and debugging tasks. Triggers on analyze, debug, troubleshoot, review, audit, security, performance, optimize, investigate, trace.
Use when querying Grafana dashboards, Prometheus metrics, Loki logs, alerting, or incidents - provides workflows and patterns for Grafana MCP tools including datasource discovery, efficient dashboard access, and query construction
Use when building distributed apps with Aspire; orchestrating .NET, JavaScript, Python, or polyglot services; when environment variables or service discovery aren't working; when migrating from .NET Aspire 9 to 13+ or Community Toolkit; when seeing AddNpmApp deprecated errors; when OTEL not appearing in dashboard; when ports change on restart breaking OAuth; when configuring MCP server for AI assistants; when debugging Aspire apps and need to check resource status or logs
Generate new skills with standardized structure and frontmatter. Triggers: SG, new skill, 新增 skill, 建立技能, create skill, 新技能, 產生技能, generate skill, 技能模板, skill template, add skill, 加技能, make skill.
Comprehensive research toolkit for discovering patterns, best practices, and technical knowledge across Web search, MCP servers, GitHub repositories, and documentation. Use when researching technologies, exploring codebases, finding examples, or gathering requirements for skill development.
Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.
Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.
Conduct comprehensive web research on any topic using available MCP tools including Perplexity for current information, Playwright for web automation, and DeepWiki for encyclopedia-style content. Use when users request research, information gathering, or need to investigate a topic.
Automatically detect and suggest appropriate MCP tools (context7, grep_app, web_search) based on user queries. Use when queries contain documentation keywords (how to use, docs, API, guide, tutorial, 如何使用, 文档, 教程); code search keywords (example, implementation, source code, github, 例子, 示例, 实现, 源码); or latest information/bug fixing keywords (latest, 2025, 2026, new, update, fix bug, error, 最新, 更新, 修复 bug, 报错).
PRIMARY tool for fetching library/framework documentation. PROACTIVELY use instead of WebFetch/WebSearch when user requests docs, API references, setup guides, or code examples for any programming library or framework. Use this skill immediately when detecting queries like "show me X docs", "how do I use Y", "get Z documentation", etc. Token-efficient alternative to MCP servers.