report
Skill0 starsChanged 6 days agoMITView on GitHub
One-screen fact sheet on one or more GitHub repos, Hugging Face models, npm/PyPI packages, Docker images, VS Code extensions, MCP servers or Roblox assets — author, license, contents, activity, install, safety rating. Use for "tell me about <x>", "is <x> safe/any good", "report on <url>", /vetted:report <x>[, <y>...].
100 other projects use a version of this.
Adopted by
Most recently taken up by
- SuresoftTechnologies/statica-plugintheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 2026
- veraetogrex-portfolio/solo-sddtheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- matthewdonsemail-lab/logtheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
Used with
Projects with it also use opportunities, export 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.
ansvisorSkillopportunities
Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.
Also in 3 projects that use this
soilmassSkillexport
Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.
Also in 4 projects that use this
GoogleSkillquality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
Also in 3 projects that use this
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 7 projects that use this
tokyubevoxelverseSkillcheckup
Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.
Also in 3 projects that use this
rajnavakotiSkillscan
Run the AI dashboard scanner and generate the HTML report.
Also in 5 projects that use this
Other versions100 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 100
- microsoft/data-formulator★ 17ksame name
- Zafer-Liu/Data-Analysis-Agent★ 2.6ksame name
- H-mmer/pentest-agents★ 815same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- cwinvestments/memstack★ 425same name
- automagik-si/genie★ 353same name
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- ansvisor/ansvisor★ 233same name
- andrew-yangy/gru-ai★ 153same name
90 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
0
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 8
Read ${CLAUDE_PLUGIN_ROOT}/references/vetting.md and ${CLAUDE_PLUGIN_ROOT}/references/sources.md first.
“Common” is measured: kept by at least 6 in 10 of the 73 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
Report
Read ${CLAUDE_PLUGIN_ROOT}/references/vetting.md and ${CLAUDE_PLUGIN_ROOT}/references/sources.md first.
Input: one or more names, URLs or IDs, comma- or newline-separated. Work out the source from the URL or prefix (npm:, pypi:, docker:, vsx:, mcp:, roblox:, hf:; default GitHub). For a bare name, search and pick the clear match (name match plus the most adoption). Anything unclear goes at the end as "couldn't resolve", with the top 2 candidates. Never guess.
More than 3 targets: split them across subagents (cheap model, about 5 each, in parallel). Print one summary table first (Name | Source | What | License | Adoption | Last update | Rating | Fit), then each fact sheet.
Fact sheet
<name> (<source>): one-line description
| Author | owner, account age, verified?, notable other work |
| License | SPDX ID, plus what it means in plain words (e.g. "AGPL: if you host a modified version, you must publish your source code") |
| Activity | created, last update, latest version, stars or downloads, open issues, top contributors |
| Stack | languages, main dependencies, how it runs (CLI / Docker / library / app / extension / MCP) |
| Contents | top-level folders or files and what each holds |
| Install | the pinned command |
| Safety | ✅ ⚠️ ❔ ⛔ with the reasons (full vetting from vetting.md) |
Then Fit: 2-3 lines on whether it fits the user's current projects and what it would replace.
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.

