BigHugger

Agent skills that run markdown, that ask for Write, in claude-code format

A skill is a Markdown file that tells a coding agent how to do one job. We parse every one we can find — the frontmatter, the outline, the languages in its code blocks — so you can look for the one that fits instead of reading through a repository to find out.

69,865 skills from 9,574 repositories, last read 11 September 2026.

Skills declare what they need inconsistently: 58.8% name the languages they run, 11.2% list the tools they ask for, and 4.6% give themselves a category. Filtering narrows to the ones that said so, never to the ones that are.

  1. github-project-managementruvnet/ruflo

    Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

    claude-codebashjavascriptmarkdownyamlmcp__github__*mcp__claude-flow__*Bash
  2. hands-on-testktnyt/cclsp

    Performs manual hands-on testing of a web application using playwright-cli. Spawns the dev server if needed, navigates to pages, performs browser actions, captures screenshots, che

    claude-codebashmarkdownBash(playwright-cli:*)Bash(docker compose:*)Bash(lsof:*)
  3. docs-writemetabase/metabase

    Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).

    claude-codemarkdownReadWriteGrep+1 files
  4. triage-ci-flakepayloadcms/payload

    Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    claude-codebashdotmarkdownWriteBash(date:*)Bash(mkdir -p *)
  5. agent-creatormysleekdesigns/crawlforge-mcp

    Creates new Claude Code agent configurations from user requirements. Translates task descriptions into precisely-tuned agent .md files with expert personas, system prompts, and opt

    claude-codemarkdownyamlReadWriteEdit
  6. add-java-code-snippets-in-docsJetBrains/koog

    Use when the user asks to add Java tabs/examples to mkdocs docs that already have Kotlin examples (files under docs/docs/**.md using === "Kotlin" / Knit INCLUDE+SUFFIX blocks). Han

    claude-codebashjavamarkdownReadEditWrite
  7. draft-releasegrafana/mcp-grafana

    Draft a new release. Bumps version, generates CHANGELOG.md from git history, and creates a PR.

    claude-codemarkdownBash(git *)Bash(gh *)Bash(date *)
  8. write-internal-docsbrowseros-ai/BrowserOS

    Write a doc into the private internal-docs repo as Markdown plus a rendered HTML sibling, tidy the repo's structure and index, and open a PR to browseros-ai/internal-docs.

    claude-codebashmarkdownBashReadWrite
  9. api-validatormaximhq/bifrost

    Scan Bifrost HTTP controllers/handlers/integrations and validate OpenAPI API coverage, route methods/paths, parameters, request/response docs, and auth/security information. Use wh

    claude-codebashmarkdownyamlReadGrepGlob
  10. helm-updatemaximhq/bifrost

    Apply helm chart updates for Bifrost. Detects config.schema.json changes since the last helm release, applies user-requested changes, updates values.yaml / values.schema.json / _he

    claude-codebashgo-templatejsonmarkdownReadGrepGlob
  11. docs-writermaximhq/bifrost

    Write, update, and review Mintlify MDX documentation for Bifrost features. Explores the full codebase (UI, Go backend, config schema), validates config.json examples, places screen

    claude-codebashjsonmarkdownmdxReadGrepGlob
  12. changelog-writermaximhq/bifrost

    Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise

    claude-codebashmarkdownReadGrepGlob
  13. create-storiesDonchitos/Claude-Code-Game-Studios

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, accept

    claude-codemarkdownReadGlobGrep
  14. onboardDonchitos/Claude-Code-Game-Studios

    Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant

    claude-codemarkdownReadGlobGrep
  15. propagate-design-changeDonchitos/Claude-Code-Game-Studios

    When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the

    claude-codebashmarkdownReadGlobGrep
  16. adoptDonchitos/Claude-Code-Game-Studios

    Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Ru

    claude-codemarkdownReadGlobGrep
  17. architecture-reviewDonchitos/Claude-Code-Game-Studios

    Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies covera

    claude-codemarkdownReadGlobGrep
  18. team-qaDonchitos/Claude-Code-Game-Studios

    Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package

    claude-codemarkdownReadGlobGrep
  19. hotfixDonchitos/Claude-Code-Game-Studios

    Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.

    claude-codemarkdownReadGlobGrep
  20. ux-designDonchitos/Claude-Code-Game-Studios

    Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux

    claude-codemarkdownReadGlobGrep
  21. changelogDonchitos/Claude-Code-Game-Studios

    Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.

    claude-codemarkdownReadGlobGrep
  22. setup-engineDonchitos/Claude-Code-Game-Studios

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond

    claude-codemarkdownReadGlobGrep
  23. project-stage-detectDonchitos/Claude-Code-Game-Studios

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stag

    claude-codebashmarkdownReadGlobGrep
  24. release-checklistDonchitos/Claude-Code-Game-Studios

    Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.

    claude-codemarkdownReadGlobGrep
  25. create-control-manifestDonchitos/Claude-Code-Game-Studios

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Acce

    claude-codemarkdownReadGlobGrep
  26. day-one-patchDonchitos/Claude-Code-Game-Studios

    Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediat

    claude-codemarkdownReadGlobGrep
  27. bug-reportDonchitos/Claude-Code-Game-Studios

    Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and cont

    claude-codemarkdownReadGlobGrep
  28. milestone-reviewDonchitos/Claude-Code-Game-Studios

    Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or w

    claude-codemarkdownReadGlobGrep
  29. launch-checklistDonchitos/Claude-Code-Game-Studios

    Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

    claude-codemarkdownReadGlobGrep
  30. test-evidence-reviewDonchitos/Claude-Code-Game-Studios

    Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence comple

    claude-codemarkdownReadGlobGrep
  31. quick-designDonchitos/Claude-Code-Game-Studios

    Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too smal

    claude-codemarkdownReadGlobGrep
  32. reverse-documentDonchitos/Claude-Code-Game-Studios

    Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.

    claude-codebashmarkdownReadGlobGrep
  33. qa-planDonchitos/Claude-Code-Game-Studios

    Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan cove

    claude-codemarkdownReadGlobGrep
  34. bug-triageDonchitos/Claude-Code-Game-Studios

    Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when t

    claude-codemarkdownReadGlobGrep
  35. architecture-decisionDonchitos/Claude-Code-Game-Studios

    Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice sho

    claude-codemarkdownReadGlobGrep
  36. create-architectureDonchitos/Claude-Code-Game-Studios

    Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce

    claude-codemarkdownReadGlobGrep
  37. create-epicsDonchitos/Claude-Code-Game-Studios

    Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into st

    claude-codemarkdownReadGlobGrep
  38. consistency-checkDonchitos/Claude-Code-Game-Studios

    Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different v

    claude-codebashmarkdownReadGlobGrep
  39. retrospectiveDonchitos/Claude-Code-Game-Studios

    Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.

    claude-codemarkdownReadGlobGrep
  40. smoke-checkDonchitos/Claude-Code-Game-Studios

    Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stor

    claude-codebashmarkdownReadGlobGrep
  41. regression-suiteDonchitos/Claude-Code-Game-Studios

    Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after impl

    claude-codemarkdownReadGlobGrep
  42. security-auditDonchitos/Claude-Code-Game-Studios

    Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with

    claude-codemarkdownReadGlobGrep
  43. playtest-reportDonchitos/Claude-Code-Game-Studios

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    claude-codemarkdownReadGlobGrep
  44. design-systemDonchitos/Claude-Code-Game-Studios

    Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references depende

    claude-codemarkdownReadGlobGrep
  45. content-auditDonchitos/Claude-Code-Game-Studios

    Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.

    claude-codemarkdownReadGlobGrep
  46. patch-notesDonchitos/Claude-Code-Game-Studios

    Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.

    claude-codemarkdownReadGlobGrep
  47. asset-specDonchitos/Claude-Code-Game-Studios

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifes

    claude-codemarkdownReadGlobGrep
  48. localizeDonchitos/Claude-Code-Game-Studios

    Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, man

    claude-codemarkdownReadGlobGrep
  49. soak-testDonchitos/Claude-Code-Game-Studios

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases

    claude-codemarkdownReadGlobGrep
  50. sprint-planDonchitos/Claude-Code-Game-Studios

    Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design ba

    claude-codemarkdownyamlReadGlobGrep
  51. tech-debtDonchitos/Claude-Code-Game-Studios

    Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.

    claude-codemarkdownReadGlobGrep
  52. test-setupDonchitos/Claude-Code-Game-Studios

    Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workf

    claude-codemarkdownReadGlobGrep
  53. story-doneDonchitos/Claude-Code-Game-Studios

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates sto

    claude-codemarkdownReadGlobGrep
  54. upstream-checkBenedictKing/ccx

    检查 Claude Code / Codex 上游版本变更,对比本地版本,识别协议/工具/用法相关更新并追加 TODO 提醒

    claude-codebashjsonmarkdownBashReadWrite
  55. version-bumpBenedictKing/ccx

    升级项目版本号并提交git,支持patch/minor/major版本升级或指定具体版本号,自动从git log生成CHANGELOG

    claude-codebashmarkdownyamlBashReadWrite
  56. pmbex-co/bex

    Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as

    claude-codemarkdownReadWriteEdit
  57. commitfoldkit/foldkit

    Create a git commit with changeset enforcement

    claude-codemarkdownBash(git add:*)Bash(git status:*)Bash(git commit:*)
  58. creating-claude-hooksAgentWorkforce/relay

    Use when creating or publishing Claude Code hooks - covers executable format, event types, JSON I/O, exit codes, security requirements, and PRPM package structure

    claude-codebashjsonmarkdowntypescriptReadWriteEdit
  59. create-prnudgebee/nudgebee

    Create a pull request with proper formatting, validation, and conventions for this monorepo

    claude-codebashmarkdownBashReadEdit+1 files
  60. fixparcadei/Continuous-Claude-v3

    Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.

    claude-codebashmarkdownyamlBashReadGrep

Browse all 69,865 skills200 at a time, grouped by owner. The list above is the skills with the highest standing; this is every one of them.

The whole corpus is one call away through the search API, or ask a question of it on the index itself.