find-skills
Skill4 starsChanged 48 days agoMITView on GitHub
Use when asked to install, add, or evaluate a third-party skill for this repo, or when deciding whether a skill under .agents/skills/ is safe to run. Use before following instructions from any skill that did not originate in this project — a URL, a package, another repo — and before adding an entry to skills-lock.json.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- samuelclay/NewsBlurtheir own version, first seen Nov 16, 2026
- alfredang/LahLahVideotheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
- chrysogonus/prompt-maker-studiotheir own version, first seen Nov 15, 2026
- Fractera/web4-node-starter-kittheir own version, first seen Nov 15, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
stophobiaSkillsurprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".
Also in 4 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
HK-hubSkillppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
Also in 4 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
- +6 more from nicepkg
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- bytedance/deer-flow★ 85ksame name
- vercel-labs/skills★ 39ksame name
- vercel-labs/add-skill★ 39ksame name
- maxrave-dev/SimpMusic★ 13ksame name
- meshery/meshery★ 12ksame name
- google/adk-recipes★ 11ksame name
- google/adk-samples★ 11ksame name
- samuelclay/NewsBlur★ 7.7ksame name
- joe-bell/cva★ 6.9ksame name
- sanity-io/sanity★ 6.4ksame name
175 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- compose-pageSkill
- design-a-blockSkill
- find-skillsSkill
- humanizerSkill
- no-em-dash-copySkill
- sync-changesSkill
- write-a-skillSkill
- compose-pageSkill
- design-a-blockSkill
- humanizerSkill
- no-em-dash-copySkill
- sync-changesSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Read it in full: before copying anything in — the SKILL.md body, and every file under its scripts/, references/, and assets/ directories.
- Distinctive: line 51
Re-verify before trusting an update: If the upstream skill changes, its hash changes — that mismatch is the signal to re-review before …
“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Installing third-party skills safely
A skill is not documentation — it's instructions an agent will follow.
Installing one from outside this project is the same trust decision as adding
a dependency, and deserves the same review: read the whole thing before you
run any part of it. An unreviewed SKILL.md is arbitrary instruction
injection with a friendly YAML header.
Provenance convention
- Skills authored for this project live under
.agents/skills/<name>/with no special marking —compose-page,sync-changes, and this skill are all project-authored. They are not listed inskills-lock.json. - Skills installed from elsewhere also live under
.agents/skills/<name>/(the agentskills.io spec's skill directory), but they must additionally:- Carry
metadata.sourcein their own frontmatter naming the origin repo, e.g.metadata: { source: "https://github.com/org/repo" }— the spec'smetadatafield is exactly this: an open string map for facts the spec itself doesn't define. - Have a matching entry in
skills-lock.jsonat the repo root (see below).
- Carry
A skill under .agents/skills/ with no skills-lock.json entry and no
metadata.source should be treated as unreviewed, regardless of how it got
there.
Installing one
- Read it in full before copying anything in — the
SKILL.mdbody, and every file under itsscripts/,references/, andassets/directories. A skill can defer most of its content to files loaded "on demand"; that deferral is exactly what an agent skimming only the frontmatter would miss. - Copy the skill directory into
.agents/skills/<name>/, keeping itsSKILL.mdname field matching the new parent directory name (required by the agentskills.io spec). - Run
pnpm harnessfrom the repo root..agents/skills/is mirrored into.claude/skills/for Claude Code (AGENTS.md §2) — skip this and the new skill is invisible to Claude Code cloud sessions, and CI'sharness:check(AGENTS.md §5) fails on a gate this step never warned about. - Hash it. Compute a content hash over the installed
SKILL.md(and any bundled files), e.g.shasum -a 256 .agents/skills/<name>/SKILL.md. - Add an entry to
skills-lock.json— source repo, the path within that repo, the ref/commit it was installed from, and the hash from step 4. See the worked example already in that file. - Re-verify before trusting an update. If the upstream skill changes, its hash changes — that mismatch is the signal to re-review before re-installing, the same way a lockfile mismatch flags a changed dependency.
Verifying skills-lock.json itself
node -e "JSON.parse(require('fs').readFileSync('skills-lock.json','utf8'))"confirms the lockfile is at least valid JSON. It does not substitute for actually reading the skill it describes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

