Agent skills

Skills you can use with AI coding agents, indexed from public GitHub repositories.

Latest Most Popular

effect-ts This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from 'effect'. Also covers Effect + Next.js integration with @prb/effect-next.
enitrat/skill-issue 12
effect-testing Comprehensive testing patterns for Effect-TS services, errors, layers, and effects. Use this skill when writing tests for Effect-based code.
enitrat/skill-issue 12
vercel-react-best-practices React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
enitrat/skill-issue 12
pr-creator Guide PR authoring from creation through review completion. Use when creating/submitting/authoring pull requests, writing PR descriptions, responding to reviewer comments, or implementing review feedback. Covers the full PR lifecycle - creating PRs linked to issues, handling review comments (triaging, responding, implementing suggestions), and getting PRs merged.
enitrat/skill-issue 12
pr-review Perform thorough, constructive pull request reviews using parallel specialized agents. Use when user wants to review a PR, provide code review feedback, or assess code changes. Features confidence-scored issues, validation filtering, and batched GitHub comments.
enitrat/skill-issue 12
github-issue Comprehensive GitHub issue lifecycle management from creation through resolution. Use when creating/viewing/editing/managing GitHub issues, writing issue descriptions, creating sub-issues, linking parent/child issues, dumping issue trees to markdown, or pushing issues from files. Covers the full issue lifecycle - creating issues with conventional commit titles, managing sub-issues and cross-repo references, editing issue content, viewing and listing issues, dumping issue trees with YAML frontmatter, round-trip workflows (dump→edit→push), linking issues, commenting, labeling, and closing. Supports meta-tickets, component issues, and cross-repo sub-issue tracking.
enitrat/skill-issue 12
ask-questions-if-underspecified Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
enitrat/skill-issue 12
d2-diagram Comprehensive tool for creating D2 diagrams based on descriptions and requirements. This skill should be used when creating visual diagrams, system architectures, flowcharts, network topologies, data flows, or any visual representation that can be expressed as a diagram. Triggers include requests to "create a diagram," "visualize," "draw an architecture," "show relationships," or when converting textual descriptions into visual diagrams.
enitrat/skill-issue 12
skill-creator Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
enitrat/skill-issue 12
sudocode ALWAYS use this skill for ALL sudocode spec and issue operations. Use when user mentions "spec", "issue", "ready", "blocked", "implement", "feature", "plan", or "feedback" with sudocode specs and issues. PROACTIVELY use at start of implementation tasks to check ready issues and understand work context. Operations include viewing (show_spec, show_issue, list_issues, list_specs), creating/modifying (upsert_spec, upsert_issue), planning features, breaking down work, creating dependency graphs, and providing implementation feedback.
sudocode-ai/sudocode 263
data_analysis High-performance data analysis using Polars - load, transform, aggregate, visualize and export tabular data. Use for CSV/JSON/Parquet processing, statistical analysis, time series, and creating charts.
ArtificialAnalysis/Stirrup 338
history-autopsy Only invoke when explicitly requested via "历史速览"、"@history-autopsy" or "history autopsy". Do NOT auto-trigger.
unix2dos/skills 2
learn-tech Only invoke when explicitly requested via "学习"、"讲解"、"teach me"、"@learn-tech". Do NOT auto-trigger.
unix2dos/skills 2
go-code-review Use when reviewing Go code for performance, concurrency safety, security vulnerabilities, or readability issues
unix2dos/skills 2
wisdom-decoder Only invoke when explicitly requested via "智慧解码"、"@wisdom-decoder" or "wisdom decoder". Do NOT auto-trigger.
unix2dos/skills 2
insight-miner Only invoke when explicitly requested via "洞见"、"@insight-miner" or "insight". Do NOT auto-trigger.
unix2dos/skills 2
code-refactor Use when refactoring Go code for better structure, maintainability, extensibility, or testability - follows SOLID principles and idiomatic Go patterns
unix2dos/skills 2
confidence-check Use when starting complex tasks like feature development, bug fixes, or code refactoring - runs a pre-implementation confidence check to avoid wasting tokens on wrong directions
unix2dos/skills 2
book-recommender Only invoke when explicitly requested via "推荐一本书"、"书籍推荐"、"@book-rec" or "book recommendation". Do NOT auto-trigger.
unix2dos/skills 2
code-simplifier Use when code has excessive complexity, deep nesting, unused abstractions, or violates YAGNI/KISS/DRY principles and needs simplification or cleanup
unix2dos/skills 2
strategic-product-advisor Only invoke when explicitly requested via "产品方向"、"怎么赚钱"、"竞品分析"、"@strategic-product-advisor". Do NOT auto-trigger.
unix2dos/skills 2
ui-ux-auditor Only invoke when explicitly requested via "UI审查"、"设计审计"、"@ui-ux-auditor" or "design audit". Do NOT auto-trigger.
unix2dos/skills 2
technical-content-optimizer Only invoke when explicitly requested via "润色博客"、"技术博客优化"、"@technical-content-optimizer" or "polish blog". Do NOT auto-trigger.
unix2dos/skills 2
autoresearch Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.
unix2dos/skills 2