agentleFS
clairelily2020clairelily2020/creator-workflows/skills/workflow-install-gate/SKILL.md

workflow-install-gate

Skill0 starsChanged 21 days agoMITView on GitHub

Evaluate whether to install, update, create, or skip an external AI skill, GitHub workflow, plugin, MCP server, connector, automation, or agent package. Use when the user asks about installing a skill repo, adding a plugin, adopting a workflow framework, comparing a new tool with existing local workflows, avoiding duplicate skills, checking maintenance quality, or deciding whether to fold an idea into an existing skill. Outputs an install decision with overlap, useful delta, risk, local changes, and rollback notes.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. clairelily2020/workflow-skills★ 198% same

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

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    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 before installing or creating any external skill, plugin, MCP server, automation, or workflow package.

    line 10
  2. Distinctive:

    Only act when the new package has a clear advantage over the current local setup.

    line 14
  3. Distinctive:

    Search existing skills, agents, automations, scripts, docs, and memory notes.

    line 19
  4. Distinctive:

    If an existing workflow covers 70% or more of the task, update that workflow instead of installing a generic package.

    line 20
  5. Distinctive:

    Prefer actively maintained packages with concrete examples.

    line 24
  6. Distinctive:

    If the action changes an existing skill, first write 2-3 test prompts that represent normal user requests for that skill.

    line 37
  7. Distinctive:

    After the edit, show a before/after comparison against the test prompts or the changed section.

    line 39
  8. Distinctive:

    Do not keep a skill change based only on the editor's self-score.

    line 40
  9. Distinctive:

    Keep a rollback path for every skill edit, using git revert or a file backup when the workspace is not a git repo.

    line 41
  10. Distinctive:

    Do not install broad packs when only one small rule is useful.

    line 44
  11. Distinctive:

    Do not overwrite local custom workflows.

    line 45
  12. Distinctive:

    Keep a rollback note for every install or update.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Workflow Install Gate

Use this skill before installing or creating any external skill, plugin, MCP server, automation, or workflow package.

Decision Rule

Only act when the new package has a clear advantage over the current local setup.

Workflow

  1. Check local overlap
    • Search existing skills, agents, automations, scripts, docs, and memory notes.
    • If an existing workflow covers 70% or more of the task, update that workflow instead of installing a generic package.
  2. Check freshness
    • Review release notes, recent commits, examples, issues, and maintenance signals.
    • Prefer actively maintained packages with concrete examples.
  3. Check real delta
    • Identify what the package improves: speed, quality, reliability, repeatability, safety, or integration coverage.
    • Reject vague benefits like "looks useful" or "popular repo."
  4. Choose the smallest action
    • Skip: duplicate, stale, irrelevant, or no clear upgrade.
    • Update existing workflow: good idea, already mostly covered locally.
    • Create focused local workflow: repeated local task with stable inputs and outputs.
    • Install: actively maintained package with a meaningful advantage.
  5. Skill optimization gate
    • If the action changes an existing skill, first write 2-3 test prompts that represent normal user requests for that skill.
    • Change only one dimension at a time, such as trigger wording, workflow steps, fallback behavior, output format, or safety rules.
    • After the edit, show a before/after comparison against the test prompts or the changed section.
    • Do not keep a skill change based only on the editor's self-score. Require human review or an independent review pass.
    • Keep a rollback path for every skill edit, using git revert or a file backup when the workspace is not a git repo.
  6. Protect the workspace
    • Do not install broad packs when only one small rule is useful.
    • Do not overwrite local custom workflows.
    • Keep a rollback note for every install or update.

Output Format

Decision: Skip / Update existing workflow / Create focused workflow / Install
Reason:
Overlap with existing tools:
Useful delta:
What changes locally:
Validation:
Risk:
Rollback:

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.