███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 151 | hyperframes-media | heygen-com/hyperframes |
HyperFrames Media Preprocessing Three CLI commands that produce assets for compositions: tts (speech), transcribe (timestamps), and remove-background (transparent video). Each downloads a model on first run and caches it under ~/.cache/hyperframes/ . Drop the output into the project, then reference it from the composition HTML — see the hyperframes skill for the audio/video element conventions. Text-to-Speech ( tts ) Generate speech audio locally with Kokoro-82M. No API key. npx hyperframes tts ...
|
141.8K |
| 152 | azure-messaging | microsoft/github-copilot-for-azure |
Azure Messaging SDK Troubleshooting Quick Reference Property Value Services Azure Event Hubs, Azure Service Bus MCP Tools mcp_azure_mcp_eventhubs , mcp_azure_mcp_servicebus Best For Diagnosing SDK connection, auth, and message processing issues When to Use This Skill SDK connection failures, auth errors, or AMQP link errors Idle timeout, connection inactivity, or slow reconnection after disconnect AMQP link detach or detach-forced errors Message lock lost, message lock expired, lock renewal fail...
|
140.6K |
| 153 | paper-context-resolver | lllllllama/ai-paper-reproduction-skill |
paper-context-resolver When to apply README and repo files leave a reproduction-critical gap. The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions. The main skill needs a narrow evidence supplement instead of a full paper summary. There is already a concrete reproduction question to answer. When not to apply The README already gives enough reproduction detail. The user wants a general paper explanation rather than reproduction su...
|
140.4K |
| 154 | repo-intake-and-plan | lllllllama/ai-paper-reproduction-skill |
repo-intake-and-plan When to apply At the beginning of README-first reproduction work. When the main skill needs a fast map of repo structure and documented commands. When inference, evaluation, and training candidates must be classified conservatively. When the user explicitly wants to inspect the repo first and not run anything yet. When not to apply When execution has already started and the task is now about running commands or writing outputs. When the target is not a repository-backed repr...
|
139.9K |
| 155 | env-and-assets-bootstrap | lllllllama/ai-paper-reproduction-skill |
env-and-assets-bootstrap When to apply After repo intake identifies a credible reproduction target. When environment creation or asset path preparation is needed before running commands. When the repo depends on checkpoints, datasets, or cache directories. When the user explicitly wants setup help before any run attempt. When not to apply When the repository already ships a ready-to-run environment that does not need translation. When the task is only to scan and plan. When the task is only to r...
|
139.8K |
| 156 | minimal-run-and-audit | lllllllama/ai-paper-reproduction-skill |
minimal-run-and-audit When to apply After a reproduction target and setup plan exist. When the main skill needs execution evidence and normalized outputs. When a smoke test, documented inference run, documented evaluation run, or other short non-training verification is appropriate. When the user already knows what command should be attempted and wants execution plus reporting only. When not to apply During initial repo scanning. When environment or assets are still undefined enough to make exec...
|
139.8K |
| 157 | subagent-driven-development | obra/superpowers |
Subagent-Driven Development Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review. Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for...
|
136.1K |
| 158 | verification-before-completion | obra/superpowers |
Verification Before Completion Overview Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule. The Iron Law NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE If you haven't run the verification command in this message, you cannot claim it passes. The Gate Function BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command prov...
|
134K |
| 159 | brandkit | leonxlnx/taste-skill |
BRANDKIT IMAGE GENERATION SKILL You are an elite brand identity art director, logo designer, visual-system strategist, and presentation designer. Your job is to generate premium brand-kit images that feel like they came from a serious identity studio. The output must feel: intentional premium minimal coherent strategic visually expensive brand-system driven presentation-ready Do not generate generic logos. Do not generate random mockups. Do not generate messy AI moodboards. Create a complete bra...
|
134K |
| 160 | image-to-code | leonxlnx/taste-skill |
CORE DIRECTIVE: IMAGE-FIRST WEBSITE DESIGN TO CODE You are an elite web design art director and implementation strategist. Your job is not to generate generic website mockups. Your job is to generate premium, artistic, implementation-friendly website section references and then turn them into real frontend. This skill is for: hero sections landing pages marketing sites startup sites editorial brand pages product pages portfolio websites premium multi-section websites redesigns where visual quali...
|
132.5K |
| 161 | imagegen-frontend-web | leonxlnx/taste-skill |
CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION You are an elite frontend image art director. Your job is not to generate generic AI art. Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts. Standard image generation tends to collapse into repetitive defaults: centered dark hero purple/blue AI glow floating meaningless blobs generic dashboard card spam weak typography hierarchy cloned sections "luxury" that is just b...
|
131.4K |
| 162 | receiving-code-review | obra/superpowers |
Code Review Reception Overview Code review requires technical evaluation, not emotional performance. Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort. The Response Pattern WHEN receiving code review feedback: 1. READ: Complete feedback without reacting 2. UNDERSTAND: Restate requirement in own words (or ask) 3. VERIFY: Check against codebase reality 4. EVALUATE: Technically sound for THIS codebase? 5. RESPOND: Technical acknowledgment or ...
|
128.6K |
| 163 | imagegen-frontend-mobile | leonxlnx/taste-skill |
CORE DIRECTIVE: PREMIUM MOBILE APP IMAGE DIRECTION You are an elite mobile product design art director. Your job is not to generate generic app mockups. Your job is to generate premium, app-native, highly readable mobile app screen images and flow images. This skill is for: onboarding flows auth flows home dashboards profile screens settings screens chat screens ecommerce screens fintech screens health and fitness screens productivity apps social apps utilities multi-screen app concepts premium ...
|
128.4K |
| 164 | xlsx | anthropics/skills |
Requirements for Outputs All Excel files Professional Font Use a consistent, professional font (e.g., Arial, Times New Roman) for all deliverables unless otherwise instructed by the user Zero Formula Errors Every Excel model MUST be delivered with ZERO formula errors (REF!, DIV/0!, VALUE!, N/A, NAME?) Preserve Existing Templates (when updating templates) Study and EXACTLY match existing format, style, and conventions when modifying files Never impose standardized formatting on files with establi...
|
127.9K |
| 165 | writing-skills | obra/superpowers |
Writing Skills Overview Writing skills IS Test-Driven Development applied to process documentation. Personal skills live in agent-specific directories ( ~/.claude/skills for Claude Code, ~/.agents/skills/ for Codex) You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). Core principle: If you didn't watch an agent fail without the skill, you don't know if the...
|
127.5K |
| 166 | dispatching-parallel-agents | obra/superpowers |
Dispatching Parallel Agents Overview You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequen...
|
125.7K |
| 167 | using-git-worktrees | obra/superpowers |
Using Git Worktrees Overview Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching. Core principle: Systematic directory selection + safety verification = reliable isolation. Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace." Directory Selection Process Follow this priority order: 1. Check Existing Directories Check in priority order ls -d .worktrees 2 > /dev/null Pref...
|
125.2K |
| 168 | extract-design-system | arvindrk/extract-design-system |
Extract Design System Use this skill when the user wants to reverse-engineer a public website's design primitives into project-local starter token files. Before You Start Ask for: the target public website URL whether the user wants extraction only or starter files too Set expectations: this v1 extracts tokens and starter assets, not a full component library results are useful for initialization, not pixel-perfect reproduction do not overwrite an existing design system or app styling without con...
|
124.8K |
| 169 | finishing-a-development-branch | obra/superpowers |
Finishing a Development Branch Overview Guide completion of development work by presenting clear options and handling chosen workflow. Core principle: Verify tests → Present options → Execute choice → Clean up. Announce at start: "I'm using the finishing-a-development-branch skill to complete this work." The Process Step 1: Verify Tests Before presenting options, verify tests pass: Run project's test suite npm test / cargo test / pytest / go test ./ .. . If tests fail: Tests failing (<N> failur...
|
123K |
| 170 | emil-design-eng | emilkowalski/skills |
Design Engineering Initial Response When this skill is first invoked without a specific question, respond only with: I'm ready to help you build interfaces that feel right, my knowledge comes from Emil Kowalski's design engineering philosophy. If you want to dive even deeper, check out Emil’s course: animations.dev . Do not provide any other information until the user asks a question. You are a design engineer with the craft sensibility. You build interfaces where every detail compounds into som...
|
119.4K |
| 171 | azure-hosted-copilot-sdk | microsoft/github-copilot-for-azure |
GitHub Copilot SDK on Azure Codebase Detection — MANDATORY FIRST CHECK ⚠️ CRITICAL: This check MUST run before ANY other skill (azure-prepare, azure-deploy, etc.) when an existing codebase is present. Detection procedure (run IMMEDIATELY for any deploy/modify/add-feature prompt): Read package.json in the workspace root (and any */package.json one level deep) Check if @github/copilot-sdk or copilot-sdk appears in name , dependencies , or devDependencies If NOT found in package.json, scan .ts and ...
|
118.7K |
| 172 | azure-observability | microsoft/github-copilot-for-azure |
Azure Observability Services Services Service Use When MCP Tools CLI Azure Monitor Metrics, alerts, dashboards azure__monitor az monitor Application Insights APM, distributed tracing azure__applicationinsights az monitor app-insights Log Analytics Log queries, KQL azure__kusto az monitor log-analytics Alerts Notifications, actions - az monitor alert Workbooks Interactive reports azure__workbooks - MCP Server (Preferred) When Azure MCP is enabled: Monitor azure__monitor with command monitor_metri...
|
115.5K |
| 173 | azure-reliability | microsoft/azure-skills |
Azure Reliability Assessment & Configuration Quick Reference Property Details Best for Reliability posture assessment, zone redundancy enablement, multi-region failover setup Primary capabilities Reliability assessment table, Zone Redundancy Configuration, Multi-Region IaC Generation Supported services Azure Functions (App Service and Container Apps planned for a future version) MCP tools Azure Resource Graph queries, Azure CLI commands When to Use This Skill Activate this skill when user wants ...
|
113.5K |
| 174 | next-best-practices | vercel-labs/next-skills |
Next.js Best Practices Apply these rules when writing or reviewing Next.js code. File Conventions See file-conventions.md for: Project structure and special files Route segments (dynamic, catch-all, groups) Parallel and intercepting routes Middleware rename in v16 (middleware → proxy) RSC Boundaries Detect invalid React Server Component patterns. See rsc-boundaries.md for: Async client component detection (invalid) Non-serializable props detection Server Action exceptions Async Patterns Next.js ...
|
111.6K |
| 175 | webapp-testing | anthropics/skills |
Web Application Testing To test local web applications, write native Python Playwright scripts. Helper Scripts Available : scripts/with_server.py - Manages server lifecycle (supports multiple servers) Always run scripts with --help first to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts ra...
|
110.6K |
| 176 | design-an-interface | mattpocock/skills |
Design an Interface Based on "Design It Twice" from "A Philosophy of Software Design": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare. Workflow 1. Gather Requirements Before designing, understand: What problem does this module solve? Who are the callers? (other modules, external users, tests) What are the key operations? Any constraints? (performance, compatibility, existing patterns) What should be hidden inside vs exposed? Ask: "What doe...
|
109.7K |
| 177 | grilling | mattpocock/skills |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering. If a question can be answered by exploring the codebase, explore the codebase instead. Installs 1.7K Repository matt...
|
108.1K |
| 178 | request-refactor-plan | mattpocock/skills |
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. Explore the repo to verify their assertions and understand the current state of the codebase. Ask whether they have considered other options, and present other options to them. Interview the user about the im...
|
107.2K |
| 179 | marketing-psychology | coreyhaines31/marketingskills |
Marketing Psychology & Mental Models You are an expert in applying psychological principles and mental models to marketing. Your goal is to help users understand why people buy, how to influence behavior ethically, and how to make better marketing decisions. How to Use This Skill Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before applying mental models. Use that context to tailor reco...
|
106.3K |
| 180 | emil-design-eng | emilkowalski/skill |
Design Engineering Initial Response When this skill is first invoked without a specific question, respond only with: I'm ready to help you build interfaces that feel right, my knowledge comes from Emil Kowalski's design engineering philosophy. If you want to dive even deeper, check out Emil’s course: animations.dev . Do not provide any other information until the user asks a question. You are a design engineer with the craft sensibility. You build interfaces where every detail compounds into som...
|
104.1K |
| 181 | ubiquitous-language | mattpocock/skills |
Ubiquitous Language Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file. Process Scan the conversation for domain-relevant nouns, verbs, and concepts Identify problems : Same word used for different concepts (ambiguity) Different words used for the same concept (synonyms) Vague or overloaded terms Propose a canonical glossary with opinionated term choices Write to UBIQUITOUS_LANGUAGE.md in the working directory using the format...
|
104K |
| 182 | analyze-project | lllllllama/rigorpilot-skills |
analyze-project Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should guide read-only analysis without constraining the model's project-specific reasoning. When to apply The user wants to understand a deep learning repository before changing it. The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships. The user wants conservative suggestions about likely insertion points or suspicious implem...
|
103.9K |
| 183 | ai-research-explore | lllllllama/rigorpilot-skills |
No SKILL.md available for this skill. View on GitHub
|
103.9K |
| 184 | explore-code | lllllllama/rigorpilot-skills |
explore-code Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should guide bounded candidate code work without over-prescribing implementation details. When to apply When the researcher explicitly authorizes exploratory code changes on an isolated branch or worktree. When the task is source-anchored module transplant, backbone adaptation, LoRA or adapter insertion, or low-risk module combination. When summary-level recording is sufficient and the...
|
103.7K |
| 185 | ai-research-reproduction | lllllllama/rigorpilot-skills |
ai-research-reproduction Purpose Use this as the RigorPilot Reproduce orchestrator for README-first deep learning repository reproduction. The skill guides the agent toward a minimal trustworthy run with auditable evidence; it should not micromanage implementation details that the model can infer from the repository. Reproduction is not "make it run by changing anything"; it means faithfully reading the README, environment, weights, datasets, and documented commands, then recording results and d...
|
103.7K |
| 186 | paper-context-resolver | lllllllama/rigorpilot-skills |
paper-context-resolver When to apply README and repo files leave a reproduction-critical gap. The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions. The main skill needs a narrow evidence supplement instead of a full paper summary. There is already a concrete reproduction question to answer. When not to apply The README already gives enough reproduction detail. The user wants a general paper explanation rather than reproduction su...
|
103.7K |
| 187 | run-train | lllllllama/rigorpilot-skills |
run-train Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should keep training evidence bounded while leaving repository-specific monitoring details to the model. When to apply When the training command has already been selected and should be executed conservatively. When the researcher wants startup verification, short-run verification, full training kickoff, or resume handling. When the run needs structured training status, checkpoint, and met...
|
103.7K |
| 188 | safe-debug | lllllllama/rigorpilot-skills |
safe-debug Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should guide conservative diagnosis without blocking the model from finding the local root cause. When to apply The user provides a traceback, terminal error, or concrete training or inference failure symptom. The user wants diagnosis, root-cause narrowing, and minimal patch suggestions before code is changed. The user wants a safe debug flow with explicit human approval before mutation....
|
103.7K |
| 189 | repo-intake-and-plan | lllllllama/rigorpilot-skills |
repo-intake-and-plan When to apply At the beginning of README-first reproduction work. When the main skill needs a fast map of repo structure and documented commands. When inference, evaluation, and training candidates must be classified conservatively. When the user explicitly wants to inspect the repo first and not run anything yet. When not to apply When execution has already started and the task is now about running commands or writing outputs. When the target is not a repository-backed repr...
|
103.7K |
| 190 | explore-run | lllllllama/rigorpilot-skills |
explore-run Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should guide candidate run planning while preserving model judgment about the active repo. When to apply When the researcher explicitly authorizes exploratory runs. When the task is a small-subset validation, short-cycle training probe, batch sweep, idle-GPU search, or quick transfer-learning trial. When the output should rank candidate runs rather than certify trusted success. When not...
|
103.7K |
| 191 | env-and-assets-bootstrap | lllllllama/rigorpilot-skills |
env-and-assets-bootstrap When to apply After repo intake identifies a credible reproduction target. When environment creation or asset path preparation is needed before running commands. When the repo depends on checkpoints, datasets, or cache directories. When the user explicitly wants setup help before any run attempt. When not to apply When the repository already ships a ready-to-run environment that does not need translation. When the task is only to scan and plan. When the task is only to r...
|
103.7K |
| 192 | minimal-run-and-audit | lllllllama/rigorpilot-skills |
minimal-run-and-audit When to apply After a reproduction target and setup plan exist. When the main skill needs execution evidence and normalized outputs. When a smoke test, documented inference run, documented evaluation run, or other short non-training verification is appropriate. When the user already knows what command should be attempted and wants execution plus reporting only. When not to apply During initial repo scanning. When environment or assets are still undefined enough to make exec...
|
103.7K |
| 193 | qa | mattpocock/skills |
QA Session Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and file GitHub issues that are durable, user-focused, and use the project's domain language. For each issue the user raises 1. Listen and lightly clarify Let the user describe the problem in their own words. Ask at most 2-3 short clarifying questions focused on: What they expected vs what actually happened Steps to reproduce (if not obvious) Whether it's con...
|
102.8K |
| 194 | content-strategy | coreyhaines31/marketingskills |
Content Strategy You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both. Before Planning Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (a...
|
101.8K |
| 195 | domain-modeling | mattpocock/skills |
Domain Modeling Actively build and sharpen the project's domain model as you design. This is the active discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading CONTEXT.md for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.) File structure Most repos have a single context: / ├── CONTEXT.md ├── docs/ │ └─...
|
101.7K |
| 196 | git-guardrails-claude-code | mattpocock/skills |
Setup Git Guardrails Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them. What Gets Blocked git push (all variants including --force ) git reset --hard git clean -f / git clean -fd git branch -D git checkout . / git restore . When blocked, Claude sees a message telling it that it does not have authority to access these commands. Steps 1. Ask scope Ask the user: install for this project only ( .claude/settings.json ) or all projects ( ~/.claude/...
|
101.4K |
| 197 | obsidian-vault | mattpocock/skills |
Obsidian Vault Vault location /mnt/d/Obsidian Vault/AI Research/ Mostly flat at root level. Naming conventions Index notes : aggregate related topics (e.g., Ralph Wiggum Index.md , Skills Index.md , RAG Index.md ) Title case for all note names No folders for organization - use links and index notes instead Linking Use Obsidian [[wikilinks]] syntax: [[Note Title]] Notes link to dependencies/related notes at the bottom Index notes are just lists of [[wikilinks]] Workflows Search for notes Search ...
|
100.9K |
| 198 | firebase-basics | firebase/agent-skills |
Prerequisites Make sure you follow firebase-local-env-setup skill first. This skill assumes you have already installed the Firebase CLI and Firebase MCP server. Core Workflow 1. Authentication Log in to Firebase: npx -y firebase-tools@latest login This opens a browser for authentication. For environments where localhost is not available (e.g., remote shell), use npx -y firebase-tools@latest login --no-localhost . 2. Creating a Project To create a new Firebase project from the CLI: npx -y firebas...
|
100.2K |
| 199 | firebase-auth-basics | firebase/agent-skills |
Prerequisites Firebase Project : Created via npx -y firebase-tools@latest projects:create (see firebase-basics ). Firebase CLI : Installed and logged in (see firebase-basics ). Core Concepts Firebase Authentication provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app. Users A user is an entity that can sign in to your app. Each user is identified by a unique ID ( uid ) which is guaranteed to be unique across all providers. User properties inc...
|
99.4K |
| 200 | codebase-design | mattpocock/skills |
Codebase Design Design deep modules : a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed or restructured. The aim is leverage for callers, locality for maintainers, and testability for everyone. Glossary Use these terms exactly — don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point. Module — anything with an interface and an im...
|
98.8K |