███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 101 | 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...
|
20.7K |
| 102 | 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 ...
|
20.5K |
| 103 | launch-strategy | coreyhaines31/marketingskills |
Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users. Before Starting 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. Core Philo...
|
20.4K |
| 104 | schema-markup | coreyhaines31/marketingskills |
Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. Initial Assessment 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. Before imple...
|
20.3K |
| 105 | sleek-design-mobile-apps | sleekdotdesign/agent-skills |
Designing with Sleek Overview sleek.design is an AI-powered mobile app design tool. You interact with it via a REST API at /api/v1/* to create projects, describe what you want built in plain language, and get back rendered screens. All communication is standard HTTP with bearer token auth. Base URL : https://sleek.design Auth : Authorization: Bearer $SLEEK_API_KEY on every /api/v1/* request Content-Type : application/json (requests and responses) CORS : Enabled on all /api/v1/* endpoints Prerequ...
|
19.9K |
| 106 | email-sequence | coreyhaines31/marketingskills |
Email Sequence Design You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion. Initial Assessment 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. Before creating ...
|
19.9K |
| 107 | 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...
|
19.9K |
| 108 | paid-ads | coreyhaines31/marketingskills |
Paid Ads You are an expert performance marketer with direct access to ad platform accounts. Your goal is to help create, optimize, and scale paid advertising campaigns that drive efficient customer acquisition. Before Starting 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....
|
19.8K |
| 109 | competitor-alternatives | coreyhaines31/marketingskills |
Competitor & Alternative Pages You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively. Initial Assessment 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...
|
19.8K |
| 110 | onboarding-cro | coreyhaines31/marketingskills |
Onboarding CRO You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention. Initial Assessment 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. Before pr...
|
19.6K |
| 111 | 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...
|
19.5K |
| 112 | simple | roin-orca/skills |
Fun Brainstorming A structured yet lightweight brainstorming skill designed to move from idea to actionable direction quickly. It preserves the rigor of collaborative design — exploring intent, evaluating trade-offs, and validating decisions — while eliminating process overhead that doesn't scale to small and medium tasks. The goal is simple: understand what the user wants, think through the options together, pick a direction, and get moving. No multi-phase rituals, no mandatory design documents...
|
19.5K |
| 113 | frontend-design | pbakaus/impeccable |
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. Design Thinking Before coding, understand the context and commit to a BOLD aesthetic direction: Purpose :...
|
19.5K |
| 114 | form-cro | coreyhaines31/marketingskills |
Form CRO You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters. Initial Assessment 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. Before providing recommendations, identify: Form Type Lead capture (gate...
|
19.2K |
| 115 | building-native-ui | expo/skills |
Expo UI Guidelines References Consult these resources as needed: references/ animations.md Reanimated: entering, exiting, layout, scroll-driven, gestures controls.md Native iOS: Switch, Slider, SegmentedControl, DateTimePicker, Picker form-sheet.md Form sheets in expo-router: configuration, footers and background interaction. gradients.md CSS gradients via experimental_backgroundImage (New Arch only) icons.md SF Symbols via expo-image (sf: sou...
|
19.2K |
| 116 | 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...
|
19K |
| 117 | referral-program | coreyhaines31/marketingskills |
Referral & Affiliate Programs You are an expert in viral growth and referral marketing. Your goal is to help design and optimize programs that turn customers into growth engines. Before Starting 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 (ask if not...
|
19K |
| 118 | polish | pbakaus/impeccable |
First : Use the frontend-design skill for design principles and anti-patterns. Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished. Pre-Polish Assessment Understand the current state and goals: Review completeness : Is it functionally complete? Are there known issues to preserve (mark with TODOs)? What's the quality bar? (MVP vs flagship feature?) When does it ship? (How much time for polish?) Identif...
|
18.9K |
| 119 | free-tool-strategy | coreyhaines31/marketingskills |
Free Tool Strategy (Engineering as Marketing) You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness. Initial Assessment 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 speci...
|
18.9K |
| 120 | signup-flow-cro | coreyhaines31/marketingskills |
Signup Flow CRO You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation. Initial Assessment 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. Before providing recomme...
|
18.6K |
| 121 | critique | pbakaus/impeccable |
Conduct a holistic design critique, evaluating whether the interface actually works—not just technically, but as a designed experience. Think like a design director giving feedback. First : Use the frontend-design skill for design principles and anti-patterns. Design Critique Evaluate the interface across these dimensions: 1. AI Slop Detection (CRITICAL) This is the most important check. Does this look like every other AI-generated interface from 2024-2025? Review the design against ALL the DON'...
|
18.6K |
| 122 | adapt | pbakaus/impeccable |
Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. Assess Adaptation Challenge Understand what needs adaptation and why: Identify the source context : What was it designed for originally? (Desktop web? Mobile app?) What assumptions were made? (Large screen? Mouse input? Fast connection?) What works well in current context? Understand target context : Device : Mobile, tablet, desktop, TV, watch, print? Input method : To...
|
18.5K |
| 123 | audit | pbakaus/impeccable |
Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address. First : Use the frontend-design skill for design principles and anti-patterns. Diagnostic Scan Run comprehensive checks across multiple dimensions: Accessibility (A11y) - Check for: Contrast issues : Text contrast ratios < 4.5:1 (or 7:1 for AAA) Missing ARIA : Interactive elements without proper roles, labe...
|
18.5K |
| 124 | animate | pbakaus/impeccable |
Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone (playful vs serious, energetic vs calm), and performance constraints. Attempt to gather these from the current thread or codebase. If you don't find exact ...
|
18.5K |
| 125 | clarify | pbakaus/impeccable |
Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. Assess Current Copy Identify what makes the text unclear or ineffective: Find clarity problems : Jargon : Technical terms users won't understand Ambiguity : Multiple interpretations possible Passive voice : "Your file has been uploaded" vs "We uploaded your file" Length : Too wordy or too terse Assumptions : Assuming user knowledge they don't have Missing context : Users do...
|
18.4K |
| 126 | colorize | pbakaus/impeccable |
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors. Attempt to gather these from the current thread or codebase. If you don't find exact information and have to infer from existing design ...
|
18.4K |
| 127 | paywall-upgrade-cro | coreyhaines31/marketingskills |
Paywall and Upgrade Screen CRO You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment. Initial Assessment 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 ...
|
18.4K |
| 128 | optimize | pbakaus/impeccable |
Identify and fix performance issues to create faster, smoother user experiences. Assess Performance Issues Understand current performance and identify problems: Measure current state : Core Web Vitals : LCP, FID/INP, CLS scores Load time : Time to interactive, first contentful paint Bundle size : JavaScript, CSS, image sizes Runtime performance : Frame rate, memory usage, CPU usage Network : Request count, payload sizes, waterfall Identify bottlenecks : What's slow? (Initial load? Interactions? ...
|
18.4K |
| 129 | normalize | pbakaus/impeccable |
Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns. Plan Before making changes, deeply understand the context: Discover the design system : Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand: Core design principles and aesthetic direction Target audience and personas Component patterns and...
|
18.3K |
| 130 | teach-impeccable | pbakaus/impeccable |
Gather design context for this project, then persist it for all future sessions. Step 1: Explore the Codebase Before asking questions, thoroughly scan the project to discover what you can: README and docs : Project purpose, target audience, any stated goals Package.json / config files : Tech stack, dependencies, existing design libraries Existing components : Current design patterns, spacing, typography in use Brand assets : Logos, favicons, color values already defined Design tokens / CSS varia...
|
18.3K |
| 131 | ab-test-setup | coreyhaines31/marketingskills |
A/B Test Setup You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results. Initial Assessment 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. Before designing a test, understand: Test Context ...
|
18.3K |
| 132 | bolder | pbakaus/impeccable |
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well. Attempt to gather these from the current thread or codebase. If you don...
|
18.2K |
| 133 | popup-cro | coreyhaines31/marketingskills |
Popup CRO You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception. Initial Assessment 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. Before providing recommendations, understand: Popu...
|
18.1K |
| 134 | delight | pbakaus/impeccable |
Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality (playful vs professional vs quirky vs elegant), and what's appropriate for the domain. Attempt to gather these from the current thread or codebase. If yo...
|
18.1K |
| 135 | distill | pbakaus/impeccable |
Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), and understanding what's truly essential vs nice-to-have for this product. Attempt to gather these from the current thread or codebase. If you don't find exact information and have to inf...
|
18.1K |
| 136 | extract | pbakaus/impeccable |
Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse. Discover Analyze the target area to identify extraction opportunities: Find the design system : Locate your design system, component library, or shared UI directory (grep for "design system", "ui", "components", etc.). Understand its structure: Component organization and naming conventions Design token structure (if any) Documentation patterns Import/export co...
|
17.9K |
| 137 | onboard | pbakaus/impeccable |
Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly. Assess Onboarding Needs Understand what users need to learn and why: Identify the challenge : What are users trying to accomplish? What's confusing or unclear about current experience? Where do users get stuck or drop off? What's the "aha moment" we want users to reach? Understand the users : What's their experience level? (Beginners, power users, mixed?) What's their motivation? (Ex...
|
17.9K |
| 138 | harden | pbakaus/impeccable |
Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. Assess Hardening Needs Identify weaknesses and edge cases: Test with extreme inputs : Very long text (names, descriptions, titles) Very short text (empty, single character) Special characters (emoji, RTL text, accents) Large numbers (millions, billions) Many items (1000+ list items, 50+ options) No data (empty states) Test error scenarios : Network failures ...
|
17.8K |
| 139 | quieter | pbakaus/impeccable |
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. MANDATORY PREPARATION Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well. Attempt to gather these from the current thread or codebase...
|
17.8K |
| 140 | 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...
|
17.7K |
| 141 | react:components | google-labs-code/stitch-skills |
Stitch to React Components You are a frontend engineer focused on transforming designs into clean React code. You follow a modular approach and use automated tools to ensure code quality. Retrieval and networking Namespace discovery : Run list_tools to find the Stitch MCP prefix. Use this prefix (e.g., stitch: ) for all subsequent calls. Metadata fetch : Call [prefix]:get_screen to retrieve the design JSON. Check for existing designs : Before downloading, check if .stitch/designs/{page}.html and...
|
17.2K |
| 142 | design-md | google-labs-code/stitch-skills |
Stitch DESIGN.md Skill You are an expert Design Systems Lead. Your goal is to analyze the provided technical assets and synthesize a "Semantic Design System" into a file named DESIGN.md . Overview This skill helps you create DESIGN.md files that serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values. Prerequisites Access to the Stitch ...
|
16.9K |
| 143 | algorithmic-art | anthropics/skills |
Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms). This happens in two steps: Algorithmic Philosophy Creation (.md file) Express by creating p5.js generative art (.html + .js files) First, undertake this task: ALGORITHMIC PHILOSOPHY CREATION To begin, create an ALGORITHMIC PHILOSOPHY (not static images or templates) that will be interpreted thr...
|
16.8K |
| 144 | web-artifacts-builder | anthropics/skills |
Web Artifacts Builder To build powerful frontend claude.ai artifacts, follow these steps: Initialize the frontend repo using scripts/init-artifact.sh Develop your artifact by editing the generated code Bundle all code into a single HTML file using scripts/bundle-artifact.sh Display artifact to user (Optional) Test the artifact Stack : React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui Design & Style Guidelines VERY IMPORTANT: To avoid what is often referred to as "AI slo...
|
16.5K |
| 145 | doc-coauthoring | anthropics/skills |
Doc Co-Authoring Workflow This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing. When to Offer This Workflow Trigger conditions: User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up" User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" User seems to be starting...
|
16.2K |
| 146 | theme-factory | anthropics/skills |
Theme Factory Skill This skill provides a curated collection of professional font and color themes themes, each with carefully selected color palettes and font pairings. Once a theme is chosen, it can be applied to any artifact. Purpose To apply consistent, professional styling to presentation slide decks, use this skill. Each theme includes: A cohesive color palette with hex codes Complementary font pairings for headers and body text A distinct visual identity suitable for different contexts an...
|
16.2K |
| 147 | typescript-advanced-types | wshobson/agents |
TypeScript Advanced Types Comprehensive guidance for mastering TypeScript's advanced type system including generics, conditional types, mapped types, template literal types, and utility types for building robust, type-safe applications. When to Use This Skill Building type-safe libraries or frameworks Creating reusable generic components Implementing complex type inference logic Designing type-safe API clients Building form validation systems Creating strongly-typed configuration objects Impleme...
|
15.7K |
| 148 | git-commit | github/awesome-copilot |
Git Commit with Conventional Commits Overview Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message. Conventional Commit Format <type>[optional scope]: <description> [optional body] [optional footer(s)] Commit Types Type Purpose feat New feature fix Bug fix docs Documentation only style Formatting/style (no logic) refactor Code refactor (no feature/fix) perf Performance improvement test Ad...
|
15.3K |
| 149 | stitch-loop | google-labs-code/stitch-skills |
Stitch Build Loop You are an autonomous frontend builder participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration. Overview The Build Loop pattern enables continuous, autonomous website development through a "baton" system. Each iteration: Reads the current task from a baton file ( .stitch/next-prompt.md ) Generates a page using Stitch MCP tools Integrates the page into the site str...
|
15.2K |
| 150 | brand-guidelines | anthropics/skills |
Anthropic Brand Styling Overview To access Anthropic's official brand identity and style resources, use this skill. Keywords : branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design Brand Guidelines Colors Main Colors: Dark: 141413 - Primary text and dark backgrounds Light: faf9f5 - Light backgrounds and text on dark Mid Gray: b0aea5 - Secondary elements Light Gray: e8e6dc - Subtle backgrounds Accent Co...
|
15K |