agentleFS
Fili999Fili999/ai-hub/skills/own/self-critique/SKILL.md

self-critique

Skill2 starsChanged 4 days agoMITView on GitHub

Honest retrospective with a per-dimension score on the result, skills, agents, and workflow used. Rate work from 1 to 5 across dimensions (correctness, completeness, robustness, simplicity, verification, process, tools) — what could be done better, which assumptions should have been questioned, which alternatives existed — with concrete proposals for improvement. Use after quality gate according to hub settings.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    After the quality gate of any non-trivial task (setting "at completion", default) or every phase ("at every phase").

    line 14
  2. Very specific:

    If self-critique is disabled in Settings (quality.selfCritique: off).

    line 19

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

Self-Critique and Improvement

Critically dissects both the outcome and how it was achieved, so the next iteration is better. A focused, actionable review.

When to use

  • After the quality gate of any non-trivial task (setting "at completion", default) or every phase ("at every phase"). Reported by route.mjs.
  • Whenever a gate failed, attempts were repeated, or user corrections were required.

When not to use

  • If self-critique is disabled in Settings (quality.selfCritique: off).
  • On small tasks with clean outcomes: the final check suffices.

Point-by-point evaluation

Rate each dimension from 1 to 5, stating the rationale and what is needed to reach a 5. Ground scores in evidence (tests, checks, sources); when in doubt, choose the lower score.

DimensionQuestion
CorrectnessDoes it do what it should, without errors?
CompletenessDoes it satisfy all acceptance criteria?
RobustnessDoes it handle edge cases, errors, Mac and Windows?
SimplicityIs it the minimal, readable solution?
VerificationHow thoroughly is it proven (tests, commands)?
ProcessWas execution efficient and well-ordered?
ToolingDid used skills, agents, and workflows help?

Scale: 5 excellent · 4 good · 3 sufficient · 2 weak · 1 inadequate. Any score under 4 must produce at least one weakness; proposals target lowest scores. No overall average: an average hides weaknesses.

Procedure

  1. Outcome: what is weak, incomplete, or merely acceptable? Actively seek defects rather than confirmation.
  2. Assumptions: which assumptions went unverified? Which, if false, alters the result?
  3. Alternatives: was there a simpler, more robust approach? Why was it not chosen?
  4. Process: where was time or context wasted (redundant reads, superfluous agents, retries)? Where was deeper analysis needed?
  5. Tooling: for each skill, agent, or workflow, what was missing, ambiguous, or misleading?
  6. Proposals: at most 3 actionable improvements, prioritizing lowest scores (e.g. "add check X to quality-gate").
  7. Application, per quality.improvements setting:
    • propose (default): present proposals to user;
    • apply to own skills: edit only skills/own/, agents/own/, or workflows/, run doctor and tests; never touch external items.
  8. A single experience is a hypothesis for improvement, not a universal rule: clarify this when proposing.
  9. Record (if enabled): node "<hub>/scripts/evaluate.mjs" record '<json>' with request, size, workflow, skills, agents, gate, retries, routing, and scores across the seven dimensions (correctness, completeness, robustness, simplicity, verification, process, tools).

Expected output

Evaluation:
Correctness 4/5 — <rationale> → for 5: <what is needed>
Completeness …/5 · Robustness …/5 · Simplicity …/5 · Verification …/5 · Process …/5 · Tooling …/5
Weaknesses of deliverable: …
Assumptions to verify: …
Better alternatives: …
Process improvements: …
Skills/agents/workflow feedback: <name> — <issue>
Proposals (max 3): 1. … — where — how to verify
Applied: … | Proposed to user: …

Attention

  • Self-critique does not reopen user decisions without new facts.
  • Honesty first: if the outcome has limitations, state them clearly even if the gate passed.

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.