agentleFS
Sign inStart free
VodouAIVodouAI/OS/skills/vodou-core/qa-report/SKILL.md

qa-report

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Show the latest VODOU QA scorecard as human-readable markdown in chat — score, per-step table, and failure tails from the real runner output

7 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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    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:

    After the scorecard, optionally add up to two lines: how stale it is (compare the stamp to now) and whether tonight's runner (task 50, …

    line 38
  2. Very specific:

    If the script returns empty, say the runner has not produced a scorecard yet and point at ./vodou-core call Vodou-script-executor …

    line 40

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

VODOU QA — Latest Scorecard

Overview

Prints the most recent QA scorecard (.vodou/qa/latest.md, rewritten by scripts/qa/qa.sh on every run) directly into the chat window. The numbers come from the runner, injected pre-LLM — never from the model.

Instructions

⚠️ AUTO-EXECUTE ON LOAD. No greeting, no preamble.

Step 1: Fetch the scorecard (AUTO-EXECUTE)

Call Vodou-script-executor::execute_script with {"server_name":"vodou-qa","script_name":"qa-report","params":{}}.

Step 2: Render it verbatim

Display the returned markdown exactly as returned — heading, score line, step table, and every failure block with its log path. Do not summarize, re-order, round, or re-word any number. Unescape \n into real newlines so the table renders.

Step 3: Add at most two lines of context

After the scorecard, optionally add up to two lines: how stale it is (compare the stamp to now) and whether tonight's runner (task 50, 03:10) has fired since. Nothing else.

If the script returns empty, say the runner has not produced a scorecard yet and point at ./vodou-core call Vodou-script-executor execute_script '{"server_name":"vodou-qa","script_name":"qa-nightly"}'. Do not invent results.

<!-- AGENT_ACTIONS: {"initial_steps": [{"server": "Vodou-script-executor", "tool": "execute_script", "args": {"server_name": "vodou-qa", "script_name": "qa-report", "params": {}}}]} -->

Notes

  • Source of truth: PLANS/0.6.28/VODOU-QA/
  • Scorecard files: .vodou/qa/latest.md (human) / .vodou/qa/latest.json (machine)
  • Findings register for dedupe: PLANS/0.6.28/VODOU-QA/BREAKAGE-BASELINE.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