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
calibredb
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs). Use when listing books, searching/filtering library records, reading/updating metadata, adding/removing formats, exporting books, maintaining custom columns, running library checks, managing FTS indexing/search, or creating catalogs/backups from a Calibre library.
browser-javascript-tdd
Test-drive browser JavaScript behavior with DOM fixtures, test runners, smoke tests, onload timing, selector refactors, and integration tradeoffs with Selenium or end-to-end tests. Use when adding client-side behavior, debugging DOM tests, choosing between JS unit tests and browser functional tests, or making JavaScript testable without overusing Selenium.
broken-link-building
Run broken link building and link equity salvage workflows by finding relevant resource pages, checking outbound link status, verifying dead URLs, qualifying dead backlinks, preparing replacement outreach, and mapping old owned URLs to redirects. Use when finding broken link prospects, replacing dead resources, recovering lost backlinks, or auditing old URLs after migrations and redesigns.
book-toc-lab
Design and pressure-test useful nonfiction book promises, scopes, recommendation loops, and takeaway-first tables of contents before drafting. Use when planning, outlining, scoping, restructuring, validating, or testing a practical book, guide, manual, course-like book, or other reader-outcome-focused long-form nonfiction.
book-seed-marketing
Plan seed marketing for useful nonfiction books so the first 500-1000 target readers can start word of mouth. Use when choosing launch channels, planning a podcast or digital book tour, Amazon PPC, event giveaways, bulk sales, writing in public, content schedules, or email capture for a practical book.
book-sales-optimization
Optimize useful nonfiction book sales after the book is already working, including Amazon or retailer funnels, cover thumbnail clarity, store descriptions, authentic reviews, extra formats, pricing, upsells, piracy hooks, and fan engagement. Use when improving a book product page, purchase funnel, format strategy, pricing, direct sales, or post-launch growth.
book-reader-conversations
Plan and synthesize pre-draft reader conversations for useful nonfiction books, including listening interviews, teaching calls, reader-language capture, promise validation, scope refinement, and TOC testing. Use when validating a practical book idea, finding target readers, preparing interview prompts, testing a table of contents, or turning reader conversations into book decisions.
beta-reader-feedback
Plan beta reading rounds for practical nonfiction and turn reader comments, abandonment, confusion, skepticism, and negative feedback into manuscript revisions. Use when recruiting beta readers, preparing reader instructions, synthesizing feedback, deciding whether a book is ready, or improving a draft from real reader data.
b2b-trust-engineering
Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak.
b2b-timing-engine
Design recurring B2B buyer-presence systems that keep a company remembered until pain becomes urgent, using time-based visibility cadence instead of unreliable intent signals or linear funnel assumptions. Use when buyers know the company but deals stall, follow-up is inconsistent, the team waits for triggers, expands markets too early, or wants a 4-6 week account visibility rhythm.
b2b-sales-constraint-diagnosis
Diagnose the single B2B sales constraint currently limiting pipeline or revenue and route to the right repair workflow. Use when sales feels stuck, pipeline is weak, leads ghost, outbound is not working, conversion is unclear, or the team is debating whether to fix reach, messaging, follow-up timing, or trust.
b2b-resonance-audit
Audit and rewrite B2B sales messaging so the right buyers quickly understand the painful problem, concrete outcome, and mechanism behind the offer. Use when buyers see the company but do not remember it, cannot explain what it does, do not connect it to a trigger, or messaging sounds clever, vague, over-complex, generic, or too simplified for the buyer's world.
b2b-reach-engineering
Build B2B reach systems that make a defined market aware of the company through named accounts, real buyers, controlled delivery channels, and first-touch saturation. Use when the right market may not know the company exists, outbound gets little signal, brand awareness is vague, the target market is too broad, or the team needs a concrete account list and reach plan.
authority-credibility
Use when presenting or auditing expertise, credentials, certifications, advisory boards, expert quotes, trust badges, medical claims, legal claims, financial claims, institutional logos, titles, uniforms, or authority signals that could create undue deference.
alpinejs-django
Use when adding, changing, or debugging Alpine.js behavior in Django-rendered templates, especially when Alpine.js coexists with HTMX partial updates.
adaptive-experimentation-strategy
Plan adaptive experimentation strategies beyond fixed-horizon A/B tests. Use when evaluating sequential testing, early stopping, multi-armed bandits, Thompson sampling, contextual bandits, dynamic traffic allocation, exploration/exploitation tradeoffs, or readiness for adaptive testing infrastructure.
ab-testing-platform-strategy
Plan A/B testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.
ab-test-results-readout
Analyze and communicate A/B test results with metric readouts, subgroup analysis, data-quality checks, ad hoc investigation, visualization, and launch recommendations. Use when interpreting experiment results, preparing an A/B test report, explaining flat or mixed results, checking guardrails, segmenting test/control data, or turning experiment data into a product decision.