Loading...
Loading...
Found 69 Skills
Retrieve and explore DeepWiki-generated documentation for public GitHub repositories. Use when listing repository documentation topics, reading DeepWiki pages, or asking focused questions about a codebase that needs current repository structure, architecture notes, or component explanations.
Creates a new AEM Edge Delivery site from scratch — GitHub repo from the boilerplate, aem-code-sync installation, initial DA content (nav, footer, homepage), and a live preview URL. Use this skill whenever a user wants to create a new AEM Edge Delivery site and no repository or DA content exists yet.
Create a prepared local and GitHub repository baseline.
Adopt an exact or latest stable repository standards release.
Deep research specialist for finding GitHub repos, tools, AI models, APIs, and real data sources. Searches repositories, compares libraries, researches latest AI benchmarks, discovers APIs, locates datasets, and performs competitive analysis to accelerate development.
Generate complete project from PRD + stack template — directory structure, configs, CLAUDE.md, git repo, and GitHub push. Use when user says "scaffold project", "create new project", "start new app", "bootstrap project", or "set up from PRD". Uses SoloGraph for patterns and Context7 for latest versions. Do NOT use for planning features (use /plan) or PRD generation (use /validate).
Audit how agent context (CLAUDE.md / AGENTS.md / rules / skills) lines up with the code across a set of repositories and generate a self-contained HTML report — a short list of specific "things to check" (context behind the code, thin coverage for the codebase, oversized files, no per-area context), plus per-repo raw metrics and a folder tree comparing folder LOC to context coverage. Use when the user wants to audit context coverage across repos, "which repos are missing CLAUDE.md", "where is our agent context thin or stale", "context coverage across my org / projects folder", or "/context-coverage". Works on a local folder of clones or a whole GitHub org via the gh CLI.
Deep analysis of GitHub repositories to understand their core architecture, design philosophy, technical decisions, and implementation patterns. This skill should be used when users provide a GitHub URL and request comprehensive understanding of the repository's structure, purpose, key abstractions, or technical approach.
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.
Install themed spinner verb packs for Claude Code. Fetches spinner packs directly from the awesome-claude-spinners repository and installs them into the user's settings. Use when the user wants to customize their Claude Code spinner, install spinner verbs, or change spinner themes.
Ask questions and read documentation about any GitHub repository using DeepWiki MCP. Use when you need to understand a codebase, find specific APIs, or get context about a repository.
Deep retrospective audit of everything merged to main over a window - code quality against the stand-* skills, introduced bugs, unsafe changes, merges over red signals, hollow thread resolutions, and untracked deferrals - with a tabbed HTML report as the deliverable. Use when asked to audit merges, review what landed on main, or verify automated/agent-authored merges were up to standard.