agentleFS
Sign inStart free
blisspixelblisspixel/primr/skills/qa-iteration/SKILL.md

qa-iteration

Skill3 starsChanged 24 days agoApache-2.0View on GitHub

Assess and improve Primr output quality. Use when the user asks to review, grade, refine, or troubleshoot a report or strategy document.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. pueo-labs/primr★ 3100% same

    Edited · 0

    None found.

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

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill after research or strategy generation to evaluate output quality and identify the next corrective action.

    line 35
  2. Very specific:

    Read primr://output/latest when the user does not specify a path.

    line 43
  3. Very specific:

    Run run_qa on the concrete report path.

    line 45
  4. Very specific:

    If the user wants a different deliverable rather than a rewrite, read primr://strategies/available, call estimate_strategy, and get …

    line 49
  5. Distinctive:

    Treat QA as a decision aid, not a final verdict.

    line 57
  6. Distinctive:

    Do not recommend regeneration until you can explain what is weak.

    line 61
  7. Distinctive:

    Keep the follow-up action specific: rerun research, generate a strategy, or revise the report.

    line 63

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

QA Iteration

Purpose

Use this skill after research or strategy generation to evaluate output quality and identify the next corrective action.

Workflow

  1. Read primr://output/latest when the user does not specify a path.
  2. Run run_qa on the concrete report path.
  3. Summarize the weakest sections first.
  4. If the user wants a different deliverable rather than a rewrite, read primr://strategies/available, call estimate_strategy, and get approval before generate_strategy.

Operating Rules

  • Treat QA as a decision aid, not a final verdict.
  • Prioritize factual gaps, missing citations, and thin strategic interpretation.
  • Do not recommend regeneration until you can explain what is weak.
  • Keep the follow-up action specific: rerun research, generate a strategy, or revise the report.

Example


run_qa(report_path="output/exampleco/report.md")

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