BD messaging-the-human
Use when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.
Project World supplies when and why to contact a human.
As a process D 44/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
ReferenceAI and agentsData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: messaging-the-human (mvschwarz/openrig)
How to improve
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
- note
edit-residuethe text marks something as outdated (lines 43, 134): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 44/100
- 0Steps. Prose only: no discrete steps
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1944 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 139: enough signal without eating the budget
- +4Structure: 3 headings
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.