triage-func-verdict
Skill1 starsChanged 3 months agoMITView on GitHub
Type: skill (1 model narration) · Used by: func-run-one · Status: LIVE (2026-07-08) You will draft a Jira regression ticket for a red functional verdict. Follow these steps exactly. Inputs (passed by the workflow): run_id, confirm_run_id (from O4). Read: reports/<run_id>/verdict.json, reports/<run_id>/contract.json. Exactly one sentence describing what broke. Rules: - Neutral tone. No blame, no root-cause guessing. - Name the failing test(s), the first error line, team, and env. - Example: "The wizard's 'creates a team' flow fails on redline-dashboard local…
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- k6-browser-testSkill
- k6-load-testSkill
- k6-playwright-converterSkill
- k6-smoke-testSkill
- k6-test-plannerSkill
- apply-ws2-conventionsSkill
- author-resilient-playwrightSkill
- build-status-viewsSkill
- choose-k6-execution-modeSkill
- compare-coreSkill
- compare-to-baselineSkill
- corroborate-2-sourcesSkill
- curate-baselinesSkill
- doc-consistency-checkSkill
- emit-otlp-and-prometheusSkill
- estimate-token-costSkill
- explore-product-structureSkill
- file-perf-regression-jiraSkill
- func-verdictSkill
- heal-playwright-suiteSkill
- k6-profile-benchmarkSkill
- k6-profile-loadSkill
- k6-profile-soakSkill
- k6-profile-spikeSkill
- k6-profile-stressSkill
- learn-via-k6-docsSkill
- link-grafana-panelSkill
- notify-responsible-teamSkill
- open-draft-prSkill
- parse-k6-json-summarySkill
- parse-playwright-summarySkill
- perf-run-logSkill
- run-k6-scriptSkill
- run-ledgerSkill
- run-playwright-suiteSkill
- scope-reviewSkill
- scrub-har-secretsSkill
- triage-perf-verdictSkill
- verify-k6-scriptSkill
- verify-playwright-suiteSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 58
All fields except [NARRATION] are deterministic — copy values verbatim, no invention.
- Very specific: line 62
Write to reports/<run_id>/jira-draft.md.
- Distinctive: line 69
Read and Write only — one model narration call, no MCP.
- Distinctive: line 81
Never quote latency numbers — performance is k6's jurisdiction.
≈ “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.
Files
triage-func-verdict
Draft Jira ticket text for a red functional verdict — 1 AI narration line + deterministic template.
Type: skill (1 model narration) · Used by: func-run-one · Status: LIVE (2026-07-08)
Prompt
You will draft a Jira regression ticket for a red functional verdict. Follow these steps exactly.
1 — Read inputs
Inputs (passed by the workflow): run_id, confirm_run_id (from O4).
Read: reports/<run_id>/verdict.json, reports/<run_id>/contract.json.
2 — Write ONE narration line (model call)
Exactly one sentence describing what broke. Rules:
- Neutral tone. No blame, no root-cause guessing.
- Name the failing test(s), the first error line, team, and env.
- Example: "The wizard's 'creates a team' flow fails on redline-dashboard local as of 2026-07-08 — expect(locator).toBeVisible() failed on the team-slug input."
3 — Assemble the draft ticket (Jira wiki markup — NOT markdown)
h2. Functional Regression — Auto-detected
Team: <team>
Env: <env>
Run ID: <run_id>
Suite: functional (Playwright)
Verdict: red
Date: <started_at from contract, date part only>
Summary: [NARRATION]
h3. Failing tests
| Test | File | Error |
| <failing_tests[].test> | <file> | <error> |
h3. Run stats
- Tests: <passed>/<tests_total> passed, <failed> failed, <skipped> skipped
- Corroborated: sources=2 (confirmation run <confirm_run_id> also red)
h3. Links
- Run ledger: state/run-ledger.jsonl (filter run_id=<run_id>)
h3. Action required
Human review required before this ticket is filed. Route to reviewer subagent next.All fields except [NARRATION] are deterministic — copy values verbatim, no invention.
4 — Write output
Write to reports/<run_id>/jira-draft.md. Return
{ "draft_path": "reports/<run_id>/jira-draft.md", "narration": "<the sentence>" }.
Tools
Read and Write only — one model narration call, no MCP.
Data
- Reads:
reports/<run_id>/verdict.json,reports/<run_id>/contract.json - Writes:
reports/<run_id>/jira-draft.md
Hard rules
- Exactly one model narration line — the rest is templated from the data.
- Draft only —
file-perf-regression-jirais the separate human-gated filing step. - Only runs on corroborated red verdicts — green never reaches this skill.
- Never quote latency numbers — performance is k6's jurisdiction.
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
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.