GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoftopenclaw
@openclawAnthropic
@anthropicsOpenAI
@openaiThe Apache Software Foundation
@apacheGitHub
@githubAutoGPT
@Significant-GravitasGarry Tan
@garrytan全部 Skills 482556
create-github-issue
Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.
create-command
Create new commands for the code-anvil application. Commands are stored as .md files in the <cwd>/.anvil/commands directory with YAML frontmatter (name, description) and markdown body containing command steps. Use when users need to add new commands, modify existing commands, or understand the command file structure. Supports special command tags like <lint> and <test> for automated workflows.
create-agent
Create new agents for the code-anvil application. Agents are stored as .md files in the <cwd>/.anvil/agents directory with YAML frontmatter (id, title, description, reasoning, tools, user_prompt) and markdown body containing agent instructions. Use when users need to add new agents, modify existing agents, or understand the agent file structure.
content-creator
Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.
user-research
Structures user research — planning sessions, synthesizing findings, and translating insights into product decisions. Use when planning user interviews, analyzing research data, creating personas or journey maps, or turning qualitative feedback into structured recommendations.
sprint-retrospective
Facilitates team or project retrospectives — what worked, what didn't, action items. Use at the end of a sprint, milestone, or project phase to reflect on what went well, what didn't, and what to try next.
research-with-confidence
Investigates a question systematically before answering — verifying claims through sources, distinguishing known facts from inferences, and calibrating expressed confidence to actual certainty. Use when asked to research a topic, verify a claim, evaluate a technology, or answer a question where accuracy matters more than speed.
prd-writing
Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.
onboarding-guide
Generates a structured onboarding guide for a new agent or human joining a project — covering codebase orientation, process context, first tasks, and key contacts. Use when asked to onboard someone new, write a getting-started guide, or create a "first week" plan for a project.
legal-review
Structures a systematic legal and compliance review of contracts, policies, or technical decisions — identifying key clauses, risks, and questions for counsel. Use when asked to review a contract, check compliance implications, flag legal risks in a technical design, or prepare for a legal consultation. Always surfaces work for qualified counsel; never replaces legal advice.
estimation-planning
Software estimation and planning — story points, velocity, scope negotiation, technical debt budgeting, and statistical forecasting. Use when estimating effort, planning a sprint, negotiating scope with stakeholders, budgeting for technical debt, or forecasting completion dates.
email-drafter
Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.
documentation
Writing effective project documentation — READMEs, API doc comments, and inline comments that explain why. Use when writing or improving documentation — READMEs, doc comments, inline comments, or when code lacks explanation for non-obvious behavior.
devils-advocate
Systematically challenges a plan, decision, or proposal — identifying assumptions, failure modes, and stronger alternatives. Use when asked to critique a plan, stress-test an idea, find weaknesses in a proposal, or when the user says "what am I missing" or "argue against this."
board-of-advisors
Simulates a panel of expert advisors who each evaluate a problem from their distinct perspective — surfacing blind spots and generating more diverse thinking than a single viewpoint. Use when asked to get multiple perspectives, consult experts, think through a decision from different angles, or when a problem benefits from specialist input.
workitem-management
Create, transition, query, and link WorkItems — tasks, stories, bugs, epics. Use when the user asks to add, update, query, or link work items — backlog items, tasks, bugs, user stories, or epics.
team-manager
Create and maintain TeamMember entities — humans and named AI personas that participate in the project with persistent identity, personality, and tiered memory. Use when adding a new persistent team-member (human or named AI), managing the name pool, scaffolding memory trees, or exporting/importing a team-member bundle. Replaces the deprecated actor-profile skill (DEC-20260422_0233-SpryTulip).
team-creator
Compose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto catalog Roles + RoleSlots inside a chartering Scope. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".