agentleFS
Sign inStart free
FYClamityDestinyFYClamityDestiny/vetted/skills/share/SKILL.md

share

Skill0 starsChanged 6 days agoMITView on GitHub

Contribute a Vetted scan result to the public shared-ratings list (opt-in) by opening a pull request, or look up existing shared ratings. Use for "share this rating", "submit to vetted ratings", "has anyone rated X", /vetted:share [name].

  • Commits and pushes

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use origin, review-bugbot 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.
  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 3 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 3 projects that use this

  • MicrosoftSkill

    automate

    Propose an automation from a completed task or a new idea, then create it after approval. Use when the user asks to create an automation or wants scheduled local or cloud agent work.

    Also in 3 projects that use this

  • +3 more from 0mlkrizzz655335v
  • +1 more from 32103210

The file

Create a free account to mount
Files
SKILL.md

Shared ratings

Ratings live in the public repo FYClamityDestiny/vetted under ratings/<source>/<name>@<version>/<github-login>.json (one file per person; the index is docs/ratings.json). The format is in ${CLAUDE_PLUGIN_ROOT}/ratings/README.md.

Look up

fetch https://fyclamitydestiny.github.io/vetted/ratings.json once (cached) and find the item; community: true means 3+ accounts agree. The other skills call this before scanning. A shared rating is a hint, not a verdict. It can only lower the local rating (a shared ⛔ makes it at least ⚠️ until you've read the findings yourself). It never raises one: a ✅ from someone else never skips your own scan. Files can be faked or edited.

Contribute (only when the user says so)

  1. Build the JSON from the scan just done: source, name, exact version/commit/digest, rating, findings (file, line, one-line reason), which scanners ran, the scan.sh version, and the date. No local paths, usernames, tokens or environment details. Show the user the file before sending.
  2. Name the file after the user's own GitHub login (gh api user --jq .login); the bot rejects anything else. For GitHub repos include the full commit. Fork and open a pull request: gh repo fork FYClamityDestiny/vetted --clone=false, then create the file through gh api on the fork's branch and run gh pr create -R FYClamityDestiny/vetted. A pull request is public, so get the user's yes first.
  3. Maintainers merge only ratings they can reproduce with scan.sh.

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.

Check your setup, free