AF foundation-stakeholder-briefings
Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.
Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of…
As a process F 49/100 · Will not run — References files that are not bundled: ../foundation-stakeholder-update/SKILL.md, ../discover-stakeholder-summary/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../foundation-stakeholder-update/SKILL.md - warning
missing-refreference to a missing file: ../discover-stakeholder-summary/SKILL.md
Process rating: all ten parameters 49/100
- 0Tools and files. 2 referenced file(s) missing: ../foundation-stakeholder-update/SKILL.md, ../discover-stakeholder-summary/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1812 tokens
- 100Progress reporting. Reports progress
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)
- +2Single-language instructions
- +3Description length 518: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 40 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.