SKILLEMALL.ai

BC relay-80-100-workflow

Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite for in-memory Postgres testing, mock sandbox patterns, test-fix-rerun loops, verify gates after every edit, and the full lifecycle from implementation through passing tests to commit.

AgentWorkforce/relay Agent Skills author: AgentWorkforce 1 file body ≈ 6 344 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates…

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedurePostgreSQLSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
56/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: relay-80-100-workflow (AgentWorkforce/relay)

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 6344 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 56/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 22 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 6344 tokens
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • low 14 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 501: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (11 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.