agentleFS
Sign inStart free
Beskars-CodeBeskars-Code/Skills/skills/setup-gabriel-skills/SKILL.md

setup-gabriel-skills

Skill0 starsChanged 6 days agoMITView on GitHub

Use when the user runs /setup-gabriel-skills or asks to install, set up, or update Gabriel skills. Installs the pack's skills and places AGENTS.md for the harness in use, offering a manual copy if that fails.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Gabriel-Lafrance/Skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository18 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every run: open doctrine.md.

    line 17
  2. Distinctive:

    Verify. Look up skill roots and which harness homes exist, and print those facts instead of asking the user (reference.md).

    line 23
  3. Very specific:

    Ask once where the skills and AGENTS.md should go (reference.md).

    line 25
  4. Distinctive:

    Place AGENTS.md for the chosen scopes and the harnesses in use.

    line 28
  5. Very specific:

    If the skills or AGENTS.md could not be installed, ask once about a manual install (reference.md).

    line 30
  6. Distinctive:

    Delete old pack leftovers and retired pack skill folders when they match, and nothing else (reference.md).

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Gabriel skills

Install this pack's skills, including rules/, and place AGENTS.md where the harness already reads it. User start only, never nested under /task. Install this skill with npx skills@latest add gabriel-lafrance/skills@setup-gabriel-skills -g -y, then run it.

This skill does not install ESLint, Prettier, or editor files.

Read when

  • Every run: open doctrine.md. Skip it and you write files this skill must not touch.
  • At a step that links a section? Open reference.md. Skip it and you overwrite someone else's AGENTS.md or create a harness home.
  • About to ask the user? Use the scope question as written; it already carries the recommendation. Once rules/ is installed, later messages follow Plain language. Skip it and the scope question has no recommendation.

Process

  1. Verify. Look up skill roots and which harness homes exist, and print those facts instead of asking the user (reference.md).
  2. Ask once where the skills and AGENTS.md should go (reference.md). Wait.
  3. Install or update pack skills for the chosen scopes (reference.md).
  4. Place AGENTS.md for the chosen scopes and the harnesses in use. Never overwrite a file that is not this pack's (reference.md).
  5. If the skills or AGENTS.md could not be installed, ask once about a manual install (reference.md). Yes: link the repo and say what to put where for the harnesses in use. No: setup failed. Stop.
  6. Delete old pack leftovers and retired pack skill folders when they match, and nothing else (reference.md).
  7. Report every install, update, delete, skip, or failure, with the reason (reference.md).

Anti-patterns

  • Writing a .cursor/rules or .mdc copy

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