Discover
Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
ghostsecurity/skills Ghost Security - Secrets and credentials scanner. Scans codebase for leaked API keys, tokens, passwords, and sensitive data. Detects hardcoded secrets and generates findings with severity and remediation guidance. Use when the user asks to check for leaked secrets, scan for credentials, find hardcoded API keys or passwords, detect exposed .env values, or audit code for sensitive data exposure. | Skills | |
ArabelaTso/Skills-4-SE Reorganizes markdown documents into well-structured, consistent format while preserving content and improving readability. Use when Claude needs to: (1) Fix heading hierarchy issues (skipped levels, multiple h1s), (2) Generate or update table of contents, (3) Standardize formatting (lists, code blocks, emphasis, links), (4) Improve grammar and spelling, (5) Add missing standard sections (installation, usage, etc.), (6) Remove redundant or duplicate content, (7) Restructure technical docs, READMEs, or long-form content for better organization and flow. | Skills | |
ArabelaTso/Skills-4-SE Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment. | Skills | |
softaworks/agent-toolkit Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages. | Skills | |
softaworks/agent-toolkit Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages. | Skills | |
fpl9000/ai-skills Load, activate, and optionally install an AI skill from a .skill file. Use this skill when the user wants to load, activate, or use a skill file. The user can invoke this skill with slash command `/load-skill [ --install | -i ] SKILLFILE`, where SKILLFILE is the path to a .skill file. | Skills | |
v1.2.5 A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when writing, reviewing, or modifying code to ensure secure-by-default practices are followed. Contains: software-security A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when security concerns are mentioned, when reviewing code for vulnerabilities, or when implementing authentication, cryptography, or data handling. | Skills | |
vercel/vercel-plugin Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider. | Skills | |
neo4j-contrib/neo4j-skills Import structured data into Neo4j — LOAD CSV, CALL IN TRANSACTIONS, neo4j-admin database import full (offline bulk), apoc.load.csv/json, apoc.periodic.iterate, driver batch writes. Covers method selection, header file format, type coercion, null handling, ON ERROR modes, CONCURRENT TRANSACTIONS, pre-import constraint setup, and post-import validation. Use when importing CSV/JSON/Parquet files, migrating relational data to graph, or bulk-loading large datasets. Does NOT handle unstructured document/PDF/vector chunking pipelines — use neo4j-document-import-skill. Does NOT handle live app write patterns (MERGE/CREATE) — use neo4j-cypher-skill. Does NOT handle neo4j-admin backup/restore/config — use neo4j-cli-tools-skill. | Skills | |
v1.3.0 Reverse-engineer a legacy codebase into ATDD-ready, traceable specifications Contains: doc-this-architect Fourth agent in the doc-this Discovery pipeline (synthesis). STRICTLY DESCRIPTIVE — synthesizes C4 diagrams, full ERD, integration map, spec-impact matrix as factual dependency map. Uses LSP (outgoingCalls, incomingCalls, goToImplementation, workspaceSymbol) for deterministic dependency mapping when available; falls back to Understand-Anything layers/edges or LLM synthesis. Emits external-surface.json catalog covering every HTTP/gRPC/WebSocket/CLI/message/UI/job surface — ui entries one-per-page from the file manifest (never 'pages grouped by module'; controls get subkind:control + mounted_in). Merges Data Master's kind:database entries for external/mixed DBs. Binary confidence: 🟢 (citation) / 🔴 (gap). Dispatched programmatically by doc-this after Detective — never auto-triggered by user phrasing; direct '/doc-this-architect' is for resume/debug in an initialized pipeline. NOT for surface mapping. NOT for spec generation (doc-this-writer). NOT for technical-debt analysis. doc-this-code-analyst Second agent in doc-this Discovery pipeline (analysis). STRICTLY DESCRIPTIVE — describes code, never proposes improvements. Uses LSP for deterministic symbol inventory when available; falls back to Understand-Anything or direct reading. Per module: control flow, algorithms, data structures, metadata. Reads EVERY source file per module (markup, SQL, scripts — Total Source Coverage); token pressure checkpoints and resumes, never skips; large codebases may fan out reading to ≤3 readers under explicit consent (verified before the ledger records). Binary confidence: 🟢 (file:line) or 🔴 (gap). No 🟡. Dispatched by doc-this after Scout — never auto-triggered by user phrasing; direct '/doc-this-code-analyst' is for resume/debug. NOT for surface mapping (doc-this-scout). NOT for business-rule interpretation (doc-this-detective). NOT for cross-module synthesis (doc-this-architect). doc-this-data-master Use as an optional Discovery agent that documents the legacy database completely — tables, columns, relationships, constraints, indexes, AND the DB-resident business logic legacy systems hide: views, stored procedures, functions, triggers, rules, computed columns, non-trivial DEFAULTs, DB-side scheduled jobs (pg_cron, SQL Server Agent). Branches on database_ownership: owned → schema + business-logic + migrations-timeline docs; external → external-contract.md treating consumed objects as frozen interfaces, emits kind:database entries with visibility:external_dependency for Architect's external-surface.json; mixed → both with per-object ownership; none → skipped. Profiles actual data (enum values vs code, null rates, orphans, rows-per-state) into data-profile.md when read access exists. Triggers: '/doc-this-data-master', 'analyze database', 'extract DB logic'. NOT a generic SQL formatter. doc-this-design-system Use as an optional Discovery agent that extracts design tokens from CSS/SCSS/LESS variables, Tailwind config, UI library themes (MUI createTheme, Chakra extendTheme, Mantine, Ant Design), styled-components/Emotion theme objects, Style Dictionary tokens.json, design-tokens.yaml, Storybook stories, and screenshots. Documents color palette (primary/secondary/neutral/feedback with full scale and hex/rgb/hsl values), typography (font families with fallbacks, scale, weights, line-height, hierarchy), spacing/grid/breakpoints, other tokens (border-radius, shadows, z-index, transitions, opacity), and the in-house component library when one exists. Triggers: '/doc-this-design-system', 'extract design tokens', 'document UI design', dispatched by doc-this when frontend has a design system. NOT for design generation. NOT for screen-by-screen UI documentation (doc-this-visor). doc-this-detective Third agent in doc-this Discovery pipeline (evidence-consolidation). STRICTLY DESCRIPTIVE — extracts cited business rules, decision traces from explicit sources, state machines, RBAC/ACL matrices. Uses LSP (incomingCalls, findReferences, goToImplementation) for deterministic API classification when available; falls back to Understand-Anything call-graph or heuristics. Classifies endpoints public/private in external-surface.json. Cross-references DB-resident logic from Data Master. Confidence binary: 🟢 (cited) / 🔴 (gap). Outputs domain.md, state-machines.md, permissions.md, decision-traces/. Dispatched programmatically by doc-this after the Code Analyst — never auto-triggered by user phrasing; direct '/doc-this-detective' is for resume/debug in an initialized pipeline. NOT for surface mapping. NOT for C4 synthesis (doc-this-architect). NOT for proposing improvements or labelling bugs. doc-this-help Use to get an analogy-driven explanation of every doc-this agent and when to use each. Covers all 12 Discovery agents with one-paragraph analogies (Scout = real-estate broker doing a walkthrough; Detective = Sherlock interpreting clues; Architect = cartographer producing formal maps; Reviewer = auditor stress-testing the contracts) plus the recommended sequence and customer-project safety notes. Triggers: '/doc-this-help', 'explain doc-this agents', 'which agent should I use for X', 'what does [agent] do'. NOT for actually running an agent — invoke that agent directly. NOT for the doc-this orchestrator (use it directly). doc-this-promote Use to stage doc-this Discovery output (.doc-this-sdd/) into the project's tracked SDLC chain — the single bridge and the only doc-this skill that touches docs/. Assigns next FR/NFR/ADR IDs (flat and compound), stamps OKF frontmatter (id/type/status/description + adrs/specs relation keys) on every promoted doc, writes docs/requirements/FR-NNN-[slug].md + ADR files, bootstraps docs/okf.yaml in legacy repos, regenerates index.md catalogs by dispatching okf-maintain and appends curated TRACEABILITY rows, generates ATDD 4-layer scaffolding (.feature files tagged @api/@browser/@database/@cli into the auto-detected runner — Reqnroll/Cucumber.js/playwright-bdd/behave/godog/cucumber-rs — plus DSL stubs and protocol-driver interfaces), prints a docs(FR-NNN) commit message, halts on collisions. Triggers: '/doc-this-promote', 'promote specs to docs', 'move the discovery output into docs', 'stage SDLC artifacts'. NOT for generation (doc-this-writer). NOT for review (doc-this-reviewer). doc-this-reviewer Sixth agent in the doc-this pipeline (review). Enforces describe-only pact — REJECTS pact violations. Validates 3 canonical files per unit, reclassifies confidence under binary 🟢/🔴, REJECTS 🟡/judgment phrasing/fabricated ADRs/technical-debt/NFRs-without-contract/bug-labels. Enforces ATDD discipline: public endpoint @api coverage, UI @browser coverage, private transitive coverage, cross-layer pairing, externally observable language. Validates citation quality (no UA paths or LSP operations as citations). Validates DB coverage for external/mixed, schema-version gate. Hard-REJECTs coverage failures (ledger⊉manifest, sampling phrases, grouped ui entries); spot-checks 🔴 gaps for answers in unread files. Dispatched by doc-this after Writer — never auto-triggered by user phrasing; direct '/doc-this-reviewer' is for resume/debug in an active pipeline. NOT for SDLC promotion (doc-this-promote). NOT for re-generation (doc-this-writer). doc-this-scout Use as the first agent in the doc-this Discovery pipeline (reconnaissance phase). Maps the surface of a legacy codebase: folder structure, languages and frameworks via config files (package.json, pom.xml, go.mod, Cargo.toml, *.csproj), dependency versions, package managers, application entry points, CI/CD configs, Dockerfiles, shallow database hints (Data Master goes deeper), test frameworks, and produces an organization-suggestion (module / use-case / endpoint / hybrid / feature) with rationale. Outputs .doc-this-sdd/inventory.md, dependencies.md, .doc-this/context/surface.json + file-manifest.json (Total Source Coverage ground truth) consumed by every downstream agent. Dispatched programmatically by doc-this after the first-run handshake — never auto-triggered by user phrasing; direct '/doc-this-scout' is for resume/debug in an initialized pipeline. NOT for deep per-module analysis (that's doc-this-code-analyst). NOT for database schema extraction (that's doc-this-data-master). doc-this Reverse-engineer a legacy codebase into ATDD-ready, traceable specifications. STRICTLY DESCRIPTIVE — documents what exists, never proposes or judges. Orchestrates Scout, Code Analyst, Detective, Architect, Writer, Reviewer plus optional Tracer, Visor, Data-Master, Design-System. Uses LSP for compiler-quality cross-file analysis when available, Understand-Anything graph as fallback. Classifies APIs public/private, catalogs HTTP/gRPC/CLI/message/UI/database surfaces, emits folder-per-unit specs with binary confidence (🟢 cited / 🔴 gap). Supports --incremental re-analysis via LSP blast-radius. Triggers: 'document this codebase', 'reverse engineer this system', 'extract requirements from legacy', '/doc-this'. NOT for docstrings. NOT for greenfield. NOT for proposing improvements, technical debt, or inventing NFRs. Delegates to doc-this-promote; the promoted specs feed whatever ATDD/TDD tooling the project already uses. doc-this-tracer Use as an optional Discovery agent that resolves 🔴 gaps via dynamic analysis when static analysis falls short. STRICTLY DESCRIPTIVE — cites log lines / span IDs / samples; never proposes fixes or labels behavior as wrong. Read-only — never executes mutating code. Sources: log files, distributed traces (OTLP, Jaeger, Datadog), anonymized production samples, error-tracker exports (Sentry, Bugsnag, Rollbar). Resolves gaps like actual state machines, caller payloads, dead endpoints, error rates. Also runs the 🟢 corroboration sweep: stamps Evidence provenance (static → static + runtime, artifact-cited) on telemetry-matched scenarios — hard-advisory when the legacy system cannot be run live. Updates .doc-this-sdd/dynamic.md; promotes 🔴→🟢 ONLY on a cited specific runtime artifact — otherwise the gap stays 🔴. No 🟡. Triggers: '/doc-this-tracer', 'analyze logs', 'mine traces'. NOT for live system probing or load testing. NOT for static-only analysis (doc-this-code-analyst/detective). doc-this-viewer Open a local viewer to browse doc-this output in a browser — navigate units (requirements/design/tasks), the external-surface catalog, C4/ERD/flowchart diagrams, coverage, and open gaps from the rich .doc-this-sdd/ staging tree, plus promoted SDLC docs (FR-NNN requirements, ADRs, TRACEABILITY, .feature specs) when present. Runs a co-located launch.mjs that builds a manifest and starts a localhost-only static server for a prebuilt Svelte app, then opens the browser; stop it with launch.mjs --stop. Triggers: 'view doc-this docs', 'open the documentation viewer', 'browse doc-this output', 'serve the docs', 'open .doc-this-sdd in a browser', '/doc-this-viewer'. NOT for generating docs — that's /doc-this. NOT for staging specs into docs/ — that's /doc-this-promote. NOT for UI screenshot extraction — that's doc-this-visor. doc-this-visor Use as an optional Discovery agent that documents the legacy system's UI from screenshots — without needing the system running. Extracts components (forms with field types/validations, tables with columns/actions/pagination, navigation menus and breadcrumbs), per-screen states (loading/empty/filled/error/confirm), navigation flow between screens, and writes one screens.md per unit plus globals (ui/inventory.md, ui/flow.md). Maps each screen to a unit per the project's [specs].granularity (module/use-case/endpoint/hybrid/feature/custom), creating empty unit folders ahead of Writer when needed (Writer respects existing folders). Triggers: '/doc-this-visor', 'document UI from screenshots', 'extract screens', dispatched by doc-this when the system has a UI and the user can supply screenshots. NOT for live UI scraping (use Playwright for that). NOT for design-token extraction (doc-this-design-system). doc-this-writer Fifth agent in the doc-this Discovery pipeline (generation). STRICTLY DESCRIPTIVE — turns accumulated cited evidence into folder-per-unit operational specs; never invents requirements. Specs are ATDD-ready: requirements.md catalogs every external surface the unit exposes, with Given/When/Then scenarios per public surface tagged @api/@browser/@cli/@message/@database and file:line cites. Binary 🟢/🔴 confidence; no 🟡. NFRs ONLY from a written non-functional contract — code patterns are NOT NFR evidence. Private endpoints get no @api (covered transitively via @browser). Generates code-spec-matrix.md from the manifest (row per source file); halts when a unit's UI page lacks read markup. Dispatched by doc-this after Architect+Detective — never auto-triggered by user phrasing; direct '/doc-this-writer' is for resume/debug in an active pipeline. NOT for SDLC promotion (doc-this-promote). NOT for review (doc-this-reviewer). | Skills | |
openai/skills Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks. | Skills | |
ringcentral/rc-unified-crm-extension Use this skill when writing or revising content inside `rc-unified-crm-extension/docs` for the App Connect MkDocs site. Follow the existing public docs style used across user, developer, solution, and support pages, while applying modern documentation best practices for clarity, structure, scannability, and correctness. | Skills | |
redpanda-data/console Connect Query patterns for API calls. Use when working with mutations, queries, or data fetching. | Skills | |
HHS/OPRE-OPS Create, review, test, rebase, and rollback Alembic database migrations for OPRE OPS. Use this skill whenever the user mentions database migrations, alembic, schema changes, adding/modifying columns or tables, model changes that need migration, "migrate the database", or a migration chain conflict / divergent heads after main has moved forward. Also use when a model change has been made and the user needs to generate the corresponding migration. | Skills | |
github/awesome-copilot Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements. | Skills | |
fernandezbaptiste/claude-code-skills Extracts files from repomix-packed repositories, restoring original directory structures from XML/Markdown/JSON formats. Activates when users need to unmix repomix files, extract packed repositories, restore file structures from repomix output, or reverse the repomix packing process. | Skills | |
cased/claude-code-plugins Fetches Sentry error context using sentry-cli and helps diagnose and fix bugs in the current codebase. Use when the user wants to investgate or fix a Sentry error. | Skills | |
ArabelaTso/Skills-4-SE Generates meaningful comments and documentation for code to improve maintenance and readability. Use when adding documentation to Python or Java code, including function/method docstrings, class documentation, inline explanations for complex logic, and code annotations (TODO, FIXME). Analyzes existing comment style in the codebase to match conventions. Produces clear, concise comments that explain the "why" not just the "what", following best practices for each language. | Skills | |
trpc-group/trpc-agent-go CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language). | Skills | |
NeverSight/learn-skills.dev Atom of Thoughts (AoT) reasoning - decompose complex problems into atomic units with confidence tracking and backtracking. For genuinely complex reasoning, not everyday questions. Triggers on: atomise, complex reasoning, decompose problem, structured thinking, verify hypothesis. | Skills |
Can't find what you're looking for? Evaluate a missing skill.