agentleFS
Ming00777Ming00777/ai-workflow-advisor/skills/setup-guide/SKILL.md

setup-guide

Skill1 starsChanged 58 days agoMITView on GitHub

Provide a safe, source-aware setup and verification guide for a selected CLI, MCP server, or Agent from the local catalog; default to links and read-only checks rather than executing installation.

  • Pipes a download into a shell

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill only after the user selects a specific catalog entry.

    line 8
  2. Distinctive:

    update and uninstall path.

    line 18
  3. Distinctive:

    Prefer package-manager and signed release instructions from the official source.

    line 25
  4. Distinctive:

    Never ask the user to paste secrets into chat.

    line 26
  5. Distinctive:

    If no stable public setup path is recorded, return a product overview and a verification checklist instead of making up a command.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 6 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

Setup Guide

Use this skill only after the user selects a specific catalog entry.

Required guide sections

  • what the tool does;
  • official documentation, source repository, and release/install page when available;
  • prerequisites;
  • installation or connection steps;
  • authentication and requested permissions;
  • a read-only verification command or test prompt;
  • update and uninstall path;
  • source and maintenance status;
  • likely failure points.

Safety

  1. Present commands for review before running them. Do not use curl | bash, package installation, OAuth, or configuration writes without explicit authorization for that action.
  2. Prefer package-manager and signed release instructions from the official source. Community tools must be labeled and must not be presented as vendor software.
  3. Never ask the user to paste secrets into chat. Use environment-variable or local credential-store guidance with redaction.
  4. For MCP, describe whether it uses stdio, SSE, or Streamable HTTP, and state what data the server can receive.
  5. If no stable public setup path is recorded, return a product overview and a verification checklist instead of making up a command.

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.