███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 4851 | ads-competitor | agricidaniel/claude-ads |
Competitor Ad Intelligence Process Identify target competitors (from user input or industry analysis) Read ads/references/benchmarks.md for industry CPC/CTR/CVR baselines Research competitor ad presence across platforms Analyze ad copy, creative, and messaging themes Estimate competitor spend and keyword strategy Identify gaps and opportunities Generate competitive intelligence report Data Sources Free Intelligence Sources Source Platform What You Can Find Google Ads Transparency Center Google A...
|
3.9K |
| 4852 | spanner-basics | google/skills |
Spanner Basics This skill provides core workflows and guidance for administering and developing with Google Cloud Spanner, a fully managed, mission-critical database service offering global transactional consistency and automatic, synchronous replication for high availability. Core Principles Performance First: Spanner scales horizontally. Efficiency is tied to Primary Key design. Always warn against using monotonically increasing/decreasing values (like sequential timestamps) as the first part ...
|
3.9K |
| 4853 | godot-resources | gamedev-skills/awesome-gamedev-agent-skills |
Godot Resources (4.x) Model game data as reusable, Inspector-editable Resource objects instead of hard-coded values, and load/save them as .tres / .res . Targets Godot 4.7 . When to use Use when representing items, stats, enemy configs, dialogue lines, or level metadata as data; authoring .tres files in the Inspector; or loading/saving custom resources. When not to use: nodes/scene structure → godot-nodes-scenes ; saving the player's runtime progress (engine-agnostic save format/slots) → save-sy...
|
3.9K |
| 4854 | principle-prove-it-works | cursor/plugins |
Prove It Works Verify every task output by checking the real thing directly. Do not infer from proxies, self-reports, or "it compiles." Why: Unverified work has unknown correctness. Indirect verification (file mtimes, output freshness, agent self-reports, cached screenshots) feels cheaper than direct observation. Acting on a wrong inference costs far more than checking the source. Pattern: After completing any task, ask: "how do I prove this actually works?" Check the real thing, not a proxy: Ch...
|
3.9K |
| 4855 | chrome-automation | zc277584121/marketing-skills |
Skill: Chrome Automation (agent-browser) Automate browser tasks in the user's real Chrome session via the agent-browser CLI. Prerequisite : agent-browser must be installed and Chrome must have remote debugging enabled. See references/agent-browser-setup.md if unsure. Core Principle: Reuse the User's Existing Chrome This skill operates on a single Chrome process — the user's real browser. There is no session management, no separate profiles, no launching a fresh Playwright browser. Always Start b...
|
3.9K |
| 4856 | html-diagram | plannotator/effective-html |
HTML Diagram Review the SVG diagrams used throughout references/html-effectiveness/ . There are a bunch in there, and some of them are focused on architecture and whatnot. After reviewing them, create an HTML file that is strictly for visualizing the architecture and understanding the stack. It should not be prose-heavy. It should simplify more into a full-screen diagram and whatnot. Build a high-quality diagram in SVG. Take your time iterating on the diagram more than anything. If it makes sens...
|
3.9K |
| 4857 | benchmark-methodology | affaan-m/ecc |
Benchmark Methodology Use this skill to turn a scoped competitor set into comparable, defensible scores . Each competitor is assessed on the same nine dimensions, with explicit 1–5 rubrics, then captured in a uniform profile card. Consistency is the point: scores are only useful if the same evidence would earn the same number for any competitor. When to Activate A scoped, tiered competitor set from competitive-platform-analysis is ready to score. Need comparable, evidence-anchored scores across ...
|
3.9K |
| 4858 | infrastructure | grafana/skills |
Grafana Cloud Infrastructure Monitoring Docs : https://grafana.com/docs/grafana-cloud/monitor-infrastructure/ Kubernetes Monitoring (k8s-monitoring Helm Chart) helm repo add grafana https://grafana.github.io/helm-charts helm repo update values.yaml cluster : name : production - us - east Show more
|
3.9K |
| 4859 | architect | cursor/plugins |
Output style (plain words, no dashes, no hyphens) Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you , warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only , not read-only . Say it in ...
|
3.9K |
| 4860 | image-generation | zc277584121/marketing-skills |
Image Generation Skill Overview I help you create effective prompts for AI image generation tools like DALL-E, Midjourney, and Stable Diffusion. I understand the nuances of different platforms and can help you achieve specific visual styles. What I can do: Write detailed image generation prompts Optimize prompts for specific AI tools Suggest style keywords and modifiers Create negative prompts to avoid unwanted elements Adapt prompts for different aspect ratios Generate variations and alternativ...
|
3.9K |
| 4861 | mermaid-to-image | zc277584121/marketing-skills |
Skill: Mermaid to Image Convert ```mermaid code blocks in Markdown (or other text) files into PNG images, and replace the code blocks with image references. Useful for platforms that don't render Mermaid natively (GitHub Pages/Jekyll, Dev.to, etc.). When to Use The user asks to convert Mermaid diagrams in a file to images The user wants to render specific Mermaid code blocks as PNG A publishing workflow requires static images instead of Mermaid code blocks Workflow Step 1: Identify target files ...
|
3.9K |
| 4862 | research-synthesis | anthropics/knowledge-work-plugins |
/research-synthesis If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md . Synthesize user research data into actionable insights. See the user-research skill for research methods, interview guides, and analysis frameworks. Usage /research-synthesis $ARGUMENTS What I Accept Interview transcripts or notes Survey results (CSV, pasted data) Usability test recordings or notes Support tickets or feedback NPS/CSAT responses App store reviews Output Research...
|
3.9K |
| 4863 | auth0 | auth0/agent-skills |
Auth0 Detect intent → detect framework → detect tooling → load 2–3 reference files. Step 1: Detect intent Match the request against the What the developer wants column — it describes the goal in plain language, not just the Auth0 term (someone who says "make users confirm with a code from their phone" lands on feature:mfa ). The Intent you pick is a lookup key: in Step 4 it appears verbatim as a section heading ( feature:mfa ) listing which reference files to load. Show more Installs 975 Reposi...
|
3.9K |
| 4864 | roguelike | gamedev-skills/awesome-gamedev-agent-skills |
Roguelike A playbook for roguelikes — the turn engine, procedural dungeons, field-of-view, permadeath, and run economy. This is a compositional skill: it orchestrates procedural generation, tilemaps, save handling, and AI into a run-based game. It does not re-teach noise/RNG or tilemap APIs; it defines the loop and the systems that make a run compelling. When to use Use when building a turn-based, grid-based dungeon crawler where each death ends the run and the world is regenerated — a roguelike...
|
3.9K |
| 4865 | godot-audio | gamedev-skills/awesome-gamedev-agent-skills |
Godot Audio (4.x) Play SFX and music, route them through buses, control volume in decibels, and time gameplay to the beat. Targets Godot 4.7 . When to use Use when playing sound effects or music, routing audio to buses (Master/Music/SFX), adjusting volume/mute from code, adding bus effects (reverb, compressor), positional 3D audio, or syncing events to music. When not to use: engine-agnostic audio design (adaptive music structure, mixing philosophy, ducking patterns) → audio-design ; importing/e...
|
3.9K |
| 4866 | godot-signals-groups | gamedev-skills/awesome-gamedev-agent-skills |
Godot Signals & Groups (4.x) Decouple nodes with the observer pattern (signals) and act on many nodes at once (groups), instead of hard-coding references between scenes. Targets Godot 4.7 . When to use Use when a node needs to tell others "something happened" (player died, item picked up, wave cleared) without holding direct references to them. Use when you need to address a whole category of nodes at once ("pause all enemies", "save every checkpoint"). When not to use: raw signal syntax basics ...
|
3.9K |
| 4867 | ui | unity-technologies/skills |
UI: Build It With a Point of View Prefix your first line with 🥷 inline, not as its own paragraph. Update check (non-blocking). Once per conversation, run bash <skill-base-dir>/scripts/check-update.sh with <skill-base-dir> replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data. If it could have been generated by a defaul...
|
3.9K |
| 4868 | developer-quickstart-guide | samber/developer-relations-skills |
Developer Quickstart Guide You are a developer-documentation specialist. Your artefact is the quickstart page: it carries a reader to a single, visible, verified success, fast enough that they never consider closing the tab. A quickstart is not a tutorial. It deliberately teaches nothing general: one contrived happy path, zero branching. The reader earns proof that the product works before spending real effort on it. Who the reader is Sarah Maddox's definition (ffeathers, 2018), adopted by the G...
|
3.9K |
| 4869 | open-standards-strategy | samber/developer-relations-skills |
Open Standards Strategy You are a technology-standards strategist. You help a company decide what posture to take toward one named specification or protocol, and you make that decision defensible in front of engineering, product and legal. Four rules govern everything below. Decide per standard, never in general. "We support open standards" is a value, not a strategy. The unit of decision is one named spec, one time horizon, one owner. A standard commoditizes the layer it covers. That is its pur...
|
3.9K |
| 4870 | developer-docs-structure-audit | samber/developer-relations-skills |
Docs Structure Audit You are an information architect for developer documentation. Someone has a docs set that already exists and a suspicion that readers cannot find what they need. Say, with evidence, page by page: Which pages sit in the wrong place. Which pages try to do two jobs at once. Which pages were never written. Hand back a queue of small moves the team can actually ship. In scope: placement, coverage, findability. Out of scope: writing the pages, verifying that documented behaviour m...
|
3.9K |
| 4871 | oss-distribution-strategy | samber/developer-relations-skills |
OSS Distribution Strategy You are an open-source distribution strategist. You decide, with the maintainer, which channels keep bringing new users month after month, which get refused, and what each costs to hold. You produce a channel portfolio, a sequence and a review rhythm - not the posts, packages or pull requests themselves. The scarce resource is maintainer hours, not money. Almost every channel is free to enter and expensive to keep accurate - and a neglected channel does not go silent; i...
|
3.9K |
| 4872 | developer-meetup-program | samber/developer-relations-skills |
Developer Meetup Program You are an experienced user-group organizer. The user wants a developer meetup that still happens in eighteen months, with a room that keeps coming back - not a single great evening. A meetup is a subscription, not an event. Optimize everything for the twentieth edition, not the first: a cadence the team can hold when tired, a speaker pipeline that fills itself, a cost base that survives a lost sponsor, and enough shared ownership that the founder can miss a month. Scope...
|
3.9K |
| 4873 | principle-fix-root-causes | cursor/plugins |
Fix Root Causes When debugging, do not paper over symptoms. Trace every problem to its root cause and fix it there. Why: Symptom fixes accumulate. Each workaround makes the system harder to reason about, and the real bug remains. Root-cause fixes are slower upfront but reduce total debugging time. Pattern: Reproduce first (if you can't reproduce it, you can't verify your fix) Ask "why" until you hit the root cause Resist the urge to add guards (adding a nil check to silence a crash is a symptom ...
|
3.9K |
| 4874 | start-learning | rohitg00/ai-engineering-from-scratch |
Start Learning You are onboarding a learner into the AI Engineering from Scratch curriculum: 503 lessons across 20 phases, from linear algebra to autonomous agents. Your job is to produce LEARNING.md — a single file in the current directory that captures why they are learning, where they should start, and what their path looks like. Every later /learn session reads and updates this file, so treat it as the learner's source of truth. Works with any agent. If your environment has a structured ques...
|
3.9K |
| 4875 | principle-encode-lessons-in-structure | cursor/plugins |
Encode Lessons in Structure Encode recurring fixes in mechanisms (tools, code, metadata, automation) instead of textual instructions. Every error, human correction, and unexpected outcome is a learning signal. Capture it, route it, and close the loop. Why: Textual instructions are easy to miss. They require the reader to notice, remember, and comply. Structural mechanisms (lint rules, metadata flags, runtime checks, automation scripts) enforce the rule without cooperation. Pattern: When you catc...
|
3.9K |
| 4876 | godot-export | gamedev-skills/awesome-gamedev-agent-skills |
Godot Export & Builds (4.x) Turn a project into runnable platform builds via export presets and the command line, and handle the web/dedicated-server gotchas. Targets Godot 4.7 . When to use Use when producing a shippable build: installing export templates, creating/editing export presets, exporting from the editor or headless CLI (CI), or troubleshooting web (HTML5) and dedicated-server exports. When not to use: storefront publishing flows → steam-publish / itch-publish ; the networking code of...
|
3.9K |
| 4877 | fps-shooter | gamedev-skills/awesome-gamedev-agent-skills |
FPS Shooter A playbook for first-person shooters — the look/move controller, the shooting model, weapon feel, and combat. This is a compositional skill: it wires a 3D controller, input, and AI into a shooter. It does not re-teach 3D nodes or raycasts; it defines the shooting model and the feel knobs (TTK, recoil, spread) that decide whether the guns feel good. When to use Use when building a first-person game whose core verb is aim and shoot — arena shooter, tactical FPS, PvE shooter, boomer-sho...
|
3.9K |
| 4878 | oss-contributor-onboarding | samber/developer-relations-skills |
Contributor Onboarding You are fixing the path between a stranger who wants to help and a merged pull request with their name on it. Projects lose people at every step of that path: land find work set up change submit survive review return Find the step that leaks, fix it, and prove the fix by walking the path from a clean machine. Diagnose against a published taxonomy, not intuition. Steinmacher et al.'s systematic review of newcomer barriers (Information and Software Technology 59, 2015, a rev...
|
3.9K |
| 4879 | technical-video-script | samber/developer-relations-skills |
Technical Video Script You are a developer-video writer. You produce one artefact: a script someone can record or animate from - every beat carrying what fills the frame, what happens in it, and the exact words spoken over it. You do not record, edit, render or publish. The script is the deliverable: finished when a competent person who did not write it could sit down at a clean machine and shoot it. Route to the matching skill in the References section instead of stretching this one when the ta...
|
3.9K |
| 4880 | oss-governance | samber/developer-relations-skills |
OSS Governance You are an open-source governance advisor. Your job: Work out how the project really makes decisions today. Choose the model that returns the most per maintainer hour. Write that model down as enforceable rules. Make sure the project survives losing any one person or company. Every project already has governance, usually undocumented, living in one person's head. Surface it before designing anything. Write only what really happens: foundations treat unused governance as a review-b...
|
3.9K |
| 4881 | oss-license-strategy | samber/developer-relations-skills |
OSS License Strategy You are an open-source licensing strategist. Help a maintainer or a company decide - with reasons they can defend in public - which license the project ships under and what it asks of contributors, then produce the files that make the decision real. Three rules govern everything below: Refuse legal advice. Explain what each instrument does, what it obliges, and what it has produced for projects that used it. Never assert what a court would decide, never interpret a specific ...
|
3.9K |
| 4882 | devrel-team-structure | samber/developer-relations-skills |
DevRel Team Structure You are a developer relations org designer. You decide, with the person accountable for the function, which parent it reports to, what shape it takes, which functions it covers, how it interlocks with the teams around it, and what would force the next re-org. The output is a DevRel org design brief : a short document a VP can approve and a new hire can read to learn who owns what. You produce the structure, never the job postings, the interview loop, or the work itself - se...
|
3.9K |
| 4883 | devrel-competitor-analysis | samber/developer-relations-skills |
DevRel Competitor Analysis You are a developer relations analyst. Reconstruct what competitors do for developers from the artefacts they leave in public, compare it against the user's own program on the same axes, and hand back a gap plan the team can act on this quarter. A competitor never publishes its DevRel program. It publishes docs, repositories, blog posts, community invites and conference sponsorships - those artefacts are the evidence. Use nothing that needs an account, a purchase, or a...
|
3.9K |
| 4884 | devrel-metrics | samber/developer-relations-skills |
DevRel Metrics You are a developer relations measurement strategist. You decide which numbers a DevRel program reports, what each one is allowed to claim, and what happens when one moves. The output is a measurement framework : five to eight metrics, each with a definition, a source, a baseline, a threshold, an owner and an action, plus one written attribution rule. Every DevRel team can produce numbers; almost none can produce numbers that survive the question "so what would you do differently?...
|
3.9K |
| 4885 | devrel-analytics | samber/developer-relations-skills |
DevRel Analytics You are a developer-relations measurement engineer. You design the tracking plan that makes a DevRel program's numbers real: which event fires on which surface, how a person is recognized across surfaces that share no identifier, how links get tagged, and which funnel views the plan is built to serve. This skill produces a written tracking plan, not a dashboard and not a metric framework. If the user still has to decide which numbers matter, route them to samber/developer-relati...
|
3.9K |
| 4886 | developer-case-study | samber/developer-relations-skills |
Developer Case Study You are writing someone else's engineering story. A developer case study says: these engineers ran this technology in production, here is what changed, here is what it cost them. The reader is an engineer deciding whether the same move works in their own system - not a buyer looking for reassurance. That reader discounts an all-upside narrative on sight. Your leverage is evidence discipline and honesty about the parts that hurt, not prose polish. Scope check Confirm the arte...
|
3.9K |
| 4887 | docs-seo | samber/developer-relations-skills |
Docs SEO You are a technical SEO practitioner working on a documentation site. A general SEO audit never looks for these failure modes: the same page exists once per release and once per locale the title and canonical come from a generator config rather than from a writer preview branches leak into the index thousands of auto-generated reference pages are simultaneously the thinnest and the highest-intent pages on the domain You fix what the site publishes: what search engines can crawl, which U...
|
3.9K |
| 4888 | conference-cfp-submission | samber/developer-relations-skills |
Conference CFP You are a proposal editor who has sat on programme committees. The user has a talk idea and a target event; produce every field of that event's submission form, written so a tired reviewer scoring their fortieth proposal picks this one. The proposal is judged alone. Reviewers cannot see the user's reputation, the demo they would give, or the conversation that produced the idea - only the form. Everything that has to land must be inside the fields. Scope ends at submit. If the user...
|
3.9K |
| 4889 | developer-community-moderation | samber/developer-relations-skills |
Developer Community Moderation You are a community operations lead who writes behavioural policy that a small, tired team can actually execute. Your deliverables are a published code of conduct and the private runbook that makes it real. One rule organises everything below: "a code of conduct that isn't (or can't be) enforced is worse than no code of conduct at all" (opensource.guide). So never ship the document alone - ship the process, the people, and the platform controls that make it true. T...
|
3.9K |
| 4890 | developer-journey-map | samber/developer-relations-skills |
Developer Journey Map You are a developer relations strategist mapping how a developer travels from never having heard of a technology to depending on it - and sometimes to speaking for it. Produce the map and the leak diagnosis. Do not fix the stages. The output is a developer journey map : one table, one row per stage, plus a short diagnosis naming the one stage to work on next. It is a decision artefact, not a poster, and every row must answer: what observable event proves a developer left th...
|
3.9K |
| 4891 | version-migration-guide | samber/developer-relations-skills |
Version Migration Guide You are a developer-documentation specialist. You produce one artefact: the document that carries a working project from version N to version N+1 with the least reading, the fewest surprises, and no trips into the source code. A migration guide is a how-to in the Diátaxis sense - goal-oriented, assumes competence, teaches nothing. The changelog says what happened; the guide says what the reader must now do, in the order they must do it. Every sentence that does not change...
|
3.9K |
| 4892 | tech-press-relations | samber/developer-relations-skills |
Tech Press Relations You are a press-relations lead for developer-facing products. You decide whether there is a story, shape it into something a technical reporter can write, put it in front of the right humans at the right time, and tell the user honestly what the resulting coverage is worth. Press does not convert developers. A developer who reads an article goes to the repository or the docs and decides there: in a 2020 survey of 115 developers, tool selection ran on maturity, usability and ...
|
3.9K |
| 4893 | devrel-content-calendar | samber/developer-relations-skills |
DevRel Content Calendar You are a developer-relations content planner. You turn a pile of ideas, fixed dates, and limited reviewer time into a dated quarterly plan the team can actually ship. Content plans do not fail for lack of ideas. They fail on capacity - review passes nobody counted - and on slots nobody owns. Make both constraints explicit before the calendar exists, then keep the calendar inside them. Interview Ask these one at a time, multiple-choice when possible, and stop once you can...
|
3.9K |
| 4894 | developer-tutorial | samber/developer-relations-skills |
Developer Tutorial You are a developer-education specialist. You produce one artefact: a tutorial that takes a learner who cannot yet do something and leaves them able to do it, having built a working thing with their own hands along the way. A tutorial is not a quickstart. A quickstart proves the product works; a tutorial builds a skill the learner keeps. Spend the extra time that buys on teaching, never on options, theory, or feature tours. Every number in this skill is one of two kinds, class...
|
3.9K |
| 4895 | oss-issue-triage | samber/developer-relations-skills |
OSS Issue Triage You design the system that decides how a project's incoming issues and pull requests get handled - labels, intake, response promise, duty rotation, closing rules - sized to the capacity the maintainers actually have. The queue is not out of control because the labels are wrong. It is out of control because inflow exceeds available attention and no written rule says what happens to the difference. Make that arithmetic explicit, then design around it. Machine-generated submissions...
|
3.9K |
| 4896 | developer-event-sponsorship | samber/developer-relations-skills |
Developer Event Sponsorship You decide where a company's developer-event money goes: which events, at what depth, doing what on site, and what the company can honestly claim in return. Read every package line by line, because tier names carry no meaning across events. A "Gold" at a foundation mega-conference and a "Gold" at a volunteer-run community day differ on the only things that matter: whether contact data exists, whether a stage slot is for sale, which surfaces are sold separately. Develo...
|
3.9K |
| 4897 | tech-podcast-interview-prep | samber/developer-relations-skills |
Podcast Interview Prep You are a media coach for developer-relations practitioners, open-source maintainers and technical founders. Someone else's show has already booked the user; turn a vague "we'll talk about my project" into a prep brief the user can hold on a card during the recording, and into promotion assets afterwards. The booking exists before this skill starts. Route elsewhere instead of continuing when the task is one of these: Pitching hosts and building media relationships: samber/...
|
3.9K |
| 4898 | developer-champions | samber/developer-relations-skills |
Developer Champions You are a community program designer. The user wants a champions or ambassador program: a named, recognised group of unpaid advocates who teach, answer, organise and feed back - and who stay recognised without the program quietly rotting into a stale roster of people who left three years ago. Two things kill these programs: Launching before there is a community worth selecting from. Shipping the title without the lifecycle - no term, no renewal, no way out - so the roster bec...
|
3.9K |
| 4899 | tech-talk-outline | samber/developer-relations-skills |
Conference Talk Outline You are a technical talk architect. You turn an accepted abstract into an outline a speaker can rehearse, time, and cut live on stage. Produce a structured document - not slides, not a script. Slide files come later, from a deck tool. A word-for-word script is actively harmful: talking points survive losing your place on stage, but memorized prose does not. Hold Zach Holman's stance from speaking.io instead - "I just use an outline as a point to channel my thoughts, not a...
|
3.9K |
| 4900 | readme-optimization | samber/developer-relations-skills |
README Optimization You are working on the single page that decides whether a developer tries a project or closes the tab. Diagnose the existing README against evidence, then rewrite it so a stranger can evaluate the project quickly and accurately - including deciding not to use it, which is a correct outcome you should never optimize away. A README is not a documentation type. It is a landing page and a router: it answers what and why in seconds, then sends the reader onward. Judge it on whethe...
|
3.9K |