74167 Skills Available

Find awesome
Agent Skills

Agent-Skills.md is a agent skills marketplace, to find the right agent skills for you.

Popular searches

feature-development

기능 개발, 기능 구현, 신규 개발, 피처 개발, 개발 워크플로우 - Guided feature development with codebase understanding and architecture focus. Systematic 7-phase approach from discovery to implementation.

aimskr
aimskr
0

e2e-runner

E2E 테스트, Playwright, 엔드투엔드, 통합 테스트, UI 테스트 - End-to-end testing workflow using Playwright. Generates, runs, and maintains E2E tests for web applications.

aimskr
aimskr
0

doc-coauthoring

문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content.

aimskr
aimskr
0

writing-plans

계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜, 플랜 저장, TODO 저장, 계획 캡처, plan 저장, 플랜 캡처 - Use when you have a spec or requirements for a multi-step task, before touching code. Also captures Plan mode output to structured markdown files.

aimskr
aimskr
0

build-error-resolver

빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결 - Specialized in resolving build errors, compilation failures, and dependency issues. Systematic approach to diagnose and fix build problems.

aimskr
aimskr
0

architect

아키텍처, 설계, 시스템 설계, 구조 설계, 레이어 설계, 블루프린트, 컴포넌트 설계 - Use when designing systems, layer structures, module boundaries, or feature architectures. Provides both high-level system design (Clean Architecture, DDD) and actionable implementation blueprints.

aimskr
aimskr
0

code-reviewer

code review, PR review, quality review, performance review - Expert at reviewing code for quality, adherence to architectural principles, security, and performance. Use this to ensure code meets project standards before merging or after implementation.

aimskr
aimskr
0

prd-strategist

PRD, 기획서, 요구사항, 제품 기획, MVP, 제품 전략 - Use when brainstorming product ideas, creating PRD documents, defining MVP scope, or planning new features. MUST BE USED for any product strategy or requirements documentation tasks.

aimskr
aimskr
0

tdd-workflow

TDD, 테스트 주도 개발, 테스트 먼저, RED-GREEN-REFACTOR - Test-Driven Development workflow. Write tests first, then implement code to make tests pass. Enforces 80%+ coverage.

aimskr
aimskr
0

testing-strategy

테스트, 테스팅, QA, 테스트 전략, 품질 보증, 유닛 테스트, 통합 테스트, E2E, 테스트 커버리지 - Use when designing test strategies, writing test plans, or ensuring quality assurance. Guides systematic testing approach from unit to E2E with proper coverage and scenario design.

aimskr
aimskr
0

ui-ux-design

UI, UX, Design, Implementation, Interaction, Live Review - Create and review high-end frontend interfaces with live browser testing. Focus on distinctive aesthetics and production-grade code while avoiding generic 'AI slop'.

aimskr
aimskr
0

execute

Use when the user wants to execute tasks autonomously, run compounder on a tasks.md file, start autonomous development, compound through a task list, or implement tasks iteratively. Guides autonomous task execution using compound loops.

jero2rome
jero2rome
0

ideate

Use when the user has an idea to brainstorm, wants to design a feature, needs help refining a concept, says "let's ideate", or describes a vague project needing structure. Guides structured brainstorming to produce a clear feature description ready for speckit.

jero2rome
jero2rome
0

init

Initialize a new feature workflow with git worktree. Use when the user wants to start a new feature, create an isolated development branch, says "init worktree", or needs to set up a feature branch for compounder workflow.

jero2rome
jero2rome
0

feature-workflow

Structured workflow for implementing new features with planning, clarification, and documentation. Use when implementing new features, making significant changes, or when the user requests a feature that requires planning and multiple implementation steps. Triggers on feature requests, multi-step implementations, or when explicit planning is beneficial.

roman-16
roman-16
0

coding-guidelines

Coding patterns and guidelines for TypeScript/JavaScript, Rust, and frontend frameworks. Use this skill when writing TypeScript/JavaScript or Rust code, or working with SolidJS, Tailwind CSS, daisyUI, React Native, Expo, or NativeWind. Provides idiomatic patterns and best practices.

roman-16
roman-16
0

skill-creator

Guide for creating effective skills. Use this skill when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.

roman-16
roman-16
0

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

roman-16
roman-16
0

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

ashwinrachhavt
ashwinrachhavt
0

planning-with-files

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

ashwinrachhavt
ashwinrachhavt
0

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

ashwinrachhavt
ashwinrachhavt
0

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

ashwinrachhavt
ashwinrachhavt
0

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

ashwinrachhavt
ashwinrachhavt
0

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

ashwinrachhavt
ashwinrachhavt
0

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

ashwinrachhavt
ashwinrachhavt
0

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

ashwinrachhavt
ashwinrachhavt
0

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

ashwinrachhavt
ashwinrachhavt
0

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

ashwinrachhavt
ashwinrachhavt
0

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

ashwinrachhavt
ashwinrachhavt
0

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

ashwinrachhavt
ashwinrachhavt
0

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

ashwinrachhavt
ashwinrachhavt
0

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

ashwinrachhavt
ashwinrachhavt
0

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

ashwinrachhavt
ashwinrachhavt
0

rails-audit-thoughtbot

Perform comprehensive code audits of Ruby on Rails applications based on thoughtbot best practices. Use this skill when the user requests a code audit, code review, quality assessment, or analysis of a Rails application. The skill analyzes the entire codebase focusing on testing practices (RSpec), security vulnerabilities, code design (skinny controllers, domain models, PORO with ActiveModel), Rails conventions, database optimization, and Ruby best practices. Outputs a detailed markdown audit report grouped by category (Testing, Security, Models, Controllers, Code Design, Views) with severity levels (Critical, High, Medium, Low) within each category.

ashwinrachhavt
ashwinrachhavt
0

consult-outside-expert

|

ashwinrachhavt
ashwinrachhavt
0

debug

Systematic debugging workflow with root cause verification before fixing

c-daly
c-daly
0

ctx

View and manage hierarchical context for the current directory

c-daly
c-daly
0

agent-teams-workflow

Coordinate agent teams for multi-domain collaborative implementation from a design doc or plan

c-daly
c-daly
0

develop

PR-based development workflow with SE team simulation

c-daly
c-daly
0

parallel-orchestrate

Orchestrate N independent TDD subagents from a YAML task manifest with worktree isolation

c-daly
c-daly
0

poll

Controlled polling for async operations at specified intervals

c-daly
c-daly
0

pipeline

Full pipeline from design doc through plan, manifest, parallel orchestration, to branch completion

c-daly
c-daly
0

pr-comment

PR review comment workflow - understand the concern before fixing

c-daly
c-daly
0

iterate

Autonomous TDD implementation workflow with phase gates.

c-daly
c-daly
0

remember

Save a learning to persistent memory with automatic scope inference

c-daly
c-daly
0

orchestrate

Workflow orchestrator. Builds task queue from input, dispatches subagents, manages completion.

c-daly
c-daly
0

implement

Auto-started default workflow. Overridden by iterate, debug, or orchestrate when invoked.

c-daly
c-daly
0

plan-to-manifest

Translate a superpowers implementation plan into a parallel orchestration YAML manifest

c-daly
c-daly
0

distill

Distill session episodes into persistent memory patterns

c-daly
c-daly
0

spawn

How to spawn subagents correctly. Use this reference when you need to delegate work to a specialized agent.

c-daly
c-daly
0

Page 1465 of 1484 · 74167 results

Adoption

Agent Skills are supported by leading AI development tools.

FAQ

Frequently asked questions about Agent Skills.

01

What are Agent Skills?

Agent Skills are reusable, production-ready capability packs for AI agents. Each skill lives in its own folder and is described by a SKILL.md file with metadata and instructions.

02

What does this agent-skills.md site do?

Agent Skills is a curated directory that indexes skill repositories and lets you browse, preview, and download skills in a consistent format.

03

Where are skills stored in a repo?

By default, the site scans the skills/ folder. You can also submit a URL that points directly to a specific skills folder.

04

What is required inside SKILL.md?

SKILL.md must include YAML frontmatter with at least name and description. The body contains the actual guidance and steps for the agent.

05

How can I submit a repo?

Click Submit in the header and paste a GitHub URL that points to a skills folder. We’ll parse it and add any valid skills to the directory.