agentleFS
aitofy-devaitofy-dev/jev-awesome-skills/skills/jev-gate/SKILL.md

jev-gate

Skill2 starsChanged 53 days agoMITView on GitHub

Use when a closed choice may already be determined by the repo, such as package manager, test runner, or file location, and you must proceed, ask the user, or stop. Runs @aitofy/jev-awesome-skills. Not for open-ended design.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Read the files that could decide the choice.

    line 13
  2. Very specific:

    Put the evidence in state.

    line 20

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

Gate

You own the options. Jev only says which listed option the context supports.

  1. Read the files that could decide the choice. If one of them already settles it, proceed and do not call Jev.
  2. Otherwise build the question with every real option plus ask_user:
jev questions gate --option pnpm="pnpm-lock.yaml is present" --option ask_user="the lockfile does not decide"
  1. Put the evidence in state. Run jev --dry-run --file request.json, then jev --file request.json from @aitofy/jev-awesome-skills. Do not write a second client.
  2. Apply branch. Stop when harm.score is at or above 1.5. Proceed when the chosen label's probability is at or above 0.9 and determined.noul is at or above 0.9. Otherwise ask. Stop wins.
  3. On "source": "fallback", fail open. Do not invent a probability.

Template: examples/gate.request.json. Offline sample: examples/gate.response.json returns proceed for pnpm.

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.