agentleFS
Sign inStart free
XORwellXORwell/archeflow/skills/score/SKILL.md

score

Skill0 starsChanged 52 days agoMITView on GitHub

Show how useful each ArcheFlow reviewer role has been across runs (signal-to-noise, fix rate, cost) with keep/optimize/remove recommendations. <example>User: "/archeflow:score"</example>

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run <archeflow-root>/lib/archeflow-score.sh report and show its table.

    line 10
  2. Very specific:

    If the user names a team file: <archeflow-root>/lib/archeflow-score.sh recommend <team.yaml> for model-tier suggestions.

    line 11
  3. Very specific:

    No data yet (.archeflow/memory/effectiveness.jsonl missing): say "No scores yet.

    line 12

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

ArcheFlow Effectiveness Scores

  1. Run <archeflow-root>/lib/archeflow-score.sh report and show its table.
  2. If the user names a team file: <archeflow-root>/lib/archeflow-score.sh recommend <team.yaml> for model-tier suggestions.
  3. No data yet (.archeflow/memory/effectiveness.jsonl missing): say "No scores yet. Scores are recorded at the end of each /archeflow:run."

Scores need several runs before they mean anything; say so when fewer than 10 runs are recorded.

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