Loading...
Loading...
Found 894 Skills
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
Automated web QA skill: analyzes a website or project, generates end-user use cases, derives a structured test plan, executes tests via Playwright browser automation, and produces a full HTML/Markdown QA report with screenshots and pass/fail results. TRIGGER this skill whenever the user asks to: test a website, run QA on a web app, check if a site works, find bugs on a site, validate a web project, create a test plan for a website, run functional tests, check a landing page, audit a web app for issues, test user flows — or any variation of "проверить сайт", "протестировать сайт", "QA сайта", "тест веб-приложения", "найти баги на сайте". Even if the user just says "посмотри работает ли всё нормально на сайте" — use this skill.
Interact with Atlassian Jira and Confluence using REST APIs — no MCP server needed. Use this skill whenever the user mentions Jira, Confluence, Atlassian, tickets, issues, sprints, backlogs, epics, stories, or any project management task that involves creating/editing/searching/transitioning Jira issues, writing or reading Confluence pages, generating status reports, triaging bugs, converting specs to backlogs, capturing tasks from meeting notes, searching company knowledge, syncing local BMAD documents with Jira or Confluence, pushing docs to Jira, pulling from Jira, linking documents to tickets, downloading Confluence spaces to local markdown, or converting between Confluence storage format and markdown. Also trigger when the user says things like "move that ticket to done", "what's the status of PROJ-123", "create a bug for X", "search our wiki for Y", "file a ticket", "check for duplicates", "write a status update", "break this spec into stories", "sync this doc", "push to jira", "pull from jira", "sync to confluence", "link this to jira", "sync my epics", "download confluence pages", "sync confluence space", "convert confluence to markdown", or "pull docs from confluence". If there is even a chance the user wants to interact with Jira or Confluence, use this skill.
Create a complete, actionable design system for any project (website, app, product) grounded in physical/sensory anchoring rather than design trends. Delivers CSS tokens, typography scale, component patterns, accessibility checklist, and absolute rules as a single developer-ready markdown document. Use this skill whenever the user asks to create a design system, theme, color palette, visual identity, CSS tokens, theme variables, or propose an art direction. Also triggers on "style guide", "site colors", "choose fonts", "look and feel", "visual branding", "charte graphique", "identite visuelle", "direction artistique", "refonte visuelle", or any new project where design isn't yet defined — propose this skill proactively.
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
Comprehensive security code review workflow for a target repository, producing a markdown report with findings and recommendations.
HTML-rendered version of /cc-canary — produces a long-form nerf-detection report as a standalone dark-theme HTML file and auto-opens it in the browser. Same analysis as /cc-canary (forensic markdown writeup), same narrative placeholders, but the output is a styled HTML page suitable for viewing, sharing, or printing. Writes `./cc-canary-<YYYY-MM-DD>.html` to the current directory.
Char (formerly Hyprnote) platform help — open-source, bot-free, local-first AI meeting notepad with system audio capture, markdown output, plugin SDK, and optional cloud STT/LLM (GPL-3.0). Use when setting up Char on macOS for the first time, speaker identification not working in group meetings, configuring local-only transcription with Cactus or Ollama for full offline use, choosing between Char's cloud STT providers (Deepgram, AssemblyAI, Soniox, OpenAI, etc.), app not launching or bouncing on dock without opening, telemetry concerns with PostHog or Sentry in a local-first app, building a Char plugin or using the automation hooks system, comparing Char to Granola or Meetily or Fathom for privacy, or configuring the CLI for template management. Do NOT use for picking between note-takers generally (use /sales-note-taker) or reviewing a single call for coaching (use /sales-call-review).
Guide Ane through structured reflection at end of day, end of week, after a decision, or after encountering new learning material. Use when the user says "journal", "reflect on today", "weekly review", "what did I learn", "after-action review", or references writing to the MELdigitalgarden vault. Produces Obsidian-compatible markdown; writes directly to the vault when filesystem MCP is connected, otherwise returns content for manual save.
Use when user input contains xlb topic queries (for example "xlb >vibe coding/vib", "xlb ??vibe coding", or "查询xlb vibe coding主题") and the task is to fetch Markdown index from local getPluginInfo API, then perform code-based retrieval with routing to available network skills/MCP tools when possible.
Single source of truth and librarian for ALL Claude official documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Claude documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from sitemaps or docs maps; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, sitemap.xml parsing, docs map processing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.