Library Skill.md library
Each one names the GitHub repo it came from, so you can check exactly what it tells your AI to do.
274991 Skill.md files
--- name: brand-guidelines description: Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones. ---
--- name: brand-perception-psychologist description: One sentence - what this skill does and when to invoke it ---
--- name: brave-man description: Runs a structured clarifying interview for new project requests before building. Instead of writing code, it outputs a fully specified prompt.md for a fresh agent session to execute, preventing expensive mistakes. ---
--- name: break-ai-fix-loops description: Stop ineffective AI coding repair loops with stable failure fingerprints, a three-attempt budget, real-path proof, negative controls, and tested rollback. ---
--- name: brendangregg-use-tsa description: Methodical performance troubleshooting and root-cause analysis with Brendan Gregg's USE and TSA methods, plus evidence-backed RCA and postmortem reports. ---
--- name: brevo-automation description: Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP. ---
--- name: broken-authentication description: Identify and exploit authentication and session management vulnerabilities in web applications. Broken authentication consistently ranks in the OWASP Top 10 and can lead to account takeover, identity theft, and unauthorized access to sensitive systems. ---
--- name: brooks-audit description: Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. ---
--- name: brooks-debt description: Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. ---
--- name: brooks-harness description: Maintenance orchestrator for the brooks-lint plugin itself. ---
--- name: brooks-lint description: AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks. ---
--- name: brooks-review description: PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. ---
--- name: brooks-sweep description: Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. ---
--- name: brooks-test description: Review test-suite quality using established testing literature; identify brittleness, mock abuse, unclear fixtures, weak assertions, slow feedback, and maintenance risks. ---
--- name: browser-act description: Use BrowserAct for authenticated browser automation, JS-rendered extraction, screenshots, parallel sessions, verification handling, and human handoff. ---
--- name: browser-automation description: Build reliable browser checks using observed UI state, semantic locators, bounded waits, isolated test data and explicit outcome verification. ---
--- name: browser-extension-builder description: Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. ---
--- name: browser-extension-reverse description: Authorized reverse engineering of Chrome/Firefox extensions: manifest analysis, background workers, content scripts, and extension-based credential or data-exposure research. ---
--- name: browser-harness description: Drive an existing browser through CDP for authenticated, visual, or interactive web automation. ---
--- name: bug-bounty description: Complete bug bounty workflow ---
--- name: bug-hunt-swarm description: Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. ---
--- name: bug-hunter description: Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression. ---
--- name: bugcrowd-reporting description: Bugcrowd-specific reporting tactics complementing report-writing ---
--- name: bugs-are-annoying description: Adversarial code auditor that hunts down bugs, logic errors, and security flaws. Use for deep correctness passes, not style reviews. ---
