GITHUB AGENT SKILLS / 技能收录

给你的 AI 助手
装上专业技能

我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。

01 /

按职业浏览 Agent Skills

为不同岗位挑选的高频技能

全部职业
02 /

按使用场景浏览 Agent Skills

从你要完成的任务出发

全部场景
03 /

按创作者浏览 Agent Skills

按 GitHub Stars 排序的优秀创作者

全部创作者

全部 Skills 482556

vercel
vercel/eve

schema

Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.

★ 5.9k
vercel
vercel/eve

programmatic-seo

Use when planning many similar pages from a template and a data set: choosing the pattern, deciding whether the data can carry it, and avoiding the thin-content failure that gets page sets deindexed.

★ 5.9k
vercel
vercel/eve

positioning

Use when working out what a product is, who it's for, and what it competes with: the market alternatives, the ideal customer, the differentiators worth claiming, and the positioning statement that follows.

★ 5.9k
vercel
vercel/eve

messaging

Use when turning settled positioning into the lines other people will reuse: the message hierarchy, value propositions per audience, objection handling, and the proof behind each claim.

★ 5.9k
vercel
vercel/eve

customer-research

Use when you need to find out what customers actually think rather than assume it: what to ask in an interview, how to mine language from reviews and support conversations, and how to tell a real finding from a polite one.

★ 5.9k
vercel
vercel/eve

brand-context

Use before writing or updating the team's shared brand context document: what belongs in it, how it's structured, how to merge new information without losing what's there, and what to keep out.

★ 5.9k
vercel
vercel/eve

resend-build

Use when building, editing, or sending anything in Resend, including broadcasts, templates, segments, and contacts, or when checking what a past send did.

★ 5.9k
vercel
vercel/eve

email-style

Use when writing or editing the copy of an email, newsletter, or broadcast in the house voice, including subject lines and preview text.

★ 5.9k
vercel
vercel/eve

email-adaptation

Use when turning existing copy, a blog post, an announcement, or a brief into an email that works in an inbox, including deciding what to cut and what to link out to.

★ 5.9k
vercel
vercel/eve

deliverability

Use when the question is whether email will reach the inbox, covering sending domain setup, authentication, list hygiene, complaint and bounce rates, or a drop in delivery.

★ 5.9k
vercel
vercel/eve

content-planning

Use when deciding what content to write: matching topics to buyer stages, choosing between searchable and shareable pieces, and grouping topics into pillars and clusters.

★ 5.9k
vercel
vercel/eve

content-editing

Use before handing back any long-form draft: edit in separate passes for sense, voice, reader payoff, proof, and specificity rather than re-reading and tweaking.

★ 5.9k
vercel
vercel/eve

blog-style

Use when drafting or editing a blog post or long-form article in the house voice.

★ 5.9k
vercel
vercel/eve

writing-quality

Writing-quality guardrails for any prose the agent drafts or edits: digest emails, issue summaries, email replies, GitHub and Linear comments. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or tool plumbing.

★ 5.9k
vercel
vercel/eve

triaging-issues

Playbook for triaging GitHub issues: checking for duplicates, applying the repo's existing labels, deciding whether to ask for a reproduction or close, and choosing when to act directly versus report back first. Load whenever asked to triage, label, dedupe, or close issues, whether the request came from a GitHub mention, an email reply, or a Linear delegation. Not needed for composing the weekly digest, answering general questions on a thread, or creating Linear issues.

★ 5.9k
vercel
vercel/eve

github-linear-bridging

Conventions for bridging GitHub and Linear: creating Linear issues from GitHub issues, cross-referencing the two trackers, and checking whether a GitHub issue is already tracked in Linear. Load when asked to create Linear issues from GitHub issues, link the trackers in either direction, or report tracking status. Not needed for work that stays inside one tracker.

★ 5.9k
vercel
vercel/eve

digest-format

How to compose or revise the weekly digest email of a repository's open issues: subject line, grouping, one-line issue summaries, needs-attention and stale criteria, citation format, and the closing follow-up guidance. Load when composing this week's digest or reworking a draft of it. Not for other emails, replies, or GitHub and Linear comments.

★ 5.9k
vercel
vercel/eve

suggest-follow-ups

Suggest high-leverage incident follow-up actions from established root cause and incident context. Activate when asked for follow-ups, action items, preventive measures, or "what should we do so this doesn't happen again" after an incident.

★ 5.9k