agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/eval-promotion-advice/SKILL.md

eval-promotion-advice

Skill2 starsChanged 4 months agoMITView on GitHub

Advise how EVAL findings should be promoted. Use when EVAL needs to suggest local task, CodeFlowMu issue draft, FCoP issue draft, or hold while applying public safety boundaries and ADMIN approval requirements.

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:

    Use when an observation may need follow-up beyond the EVAL file.

    line 10
  2. Distinctive:

    Run safe-public-draft thinking before public issue drafts.

    line 15
  3. Very specific:

    Keep admin_approved false by default.

    line 16
  4. Distinctive:

    Do not submit GitHub issues.

    line 25
  5. Distinctive:

    Do not bypass ADMIN.

    line 26
  6. Very specific:

    Do not archive/delete/move lifecycle.

    line 27

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

EVAL Promotion Advice

When to use

Use when an observation may need follow-up beyond the EVAL file.

Rules

  • Suggest target only.
  • Run safe-public-draft thinking before public issue drafts.
  • Keep admin_approved false by default.
  • Require ADMIN for public submission.

Required output

Use docs/skills/eval-playbook/promotion-advice.md.

Forbidden actions

  • Do not submit GitHub issues.
  • Do not bypass ADMIN.
  • Do not archive/delete/move lifecycle.

Minimal example

Target: local_task
Reason: project docs need update
Required authority: PM

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