agentleFS
FYClamityDestinyFYClamityDestiny/vetted/skills/report/SKILL.md

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

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.
  • ansvisorSkill

    opportunities

    Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

    Also in 3 projects that use this

  • soilmassSkill

    export

    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

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • tokyubevoxelverseSkill

    checkup

    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

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 5 projects that use this

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
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/references/vetting.md and ${CLAUDE_PLUGIN_ROOT}/references/sources.md first.

    line 8

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Authorowner, account age, verified?, notable other work
LicenseSPDX ID, plus what it means in plain words (e.g. "AGPL: if you host a modified version, you must publish your source code")
Activitycreated, last update, latest version, stars or downloads, open issues, top contributors
Stacklanguages, main dependencies, how it runs (CLI / Docker / library / app / extension / MCP)
Contentstop-level folders or files and what each holds
Installthe 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.