BF workflow-architect
Discover your actual workflow through conversation or observation, then generate a tailored skills bundle that encodes it as loadable agent skills with trigger conditions. Use when you want to understand your own process, formalize it, or share it with collaborators. Also use when a session feels aimless — this skill gives it structure. Do not use this skill for unrelated requests; route to the nearest named specialist.
Discover your actual workflow through conversation or observation, then generate a tailored skills bundle that encodes it as loadable agent skills with…
As a process F 57/100 · Will not run — References files that are not bundled: templates/manifest.yaml.tmpl, templates/decision-map.md.tmpl, templates/kanban-board-setup.sh.tmpl
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 25. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/manifest.yaml.tmpl - warning
missing-refreference to a missing file: templates/decision-map.md.tmpl - warning
missing-refreference to a missing file: templates/kanban-board-setup.sh.tmpl - warning
missing-refreference to a missing file: templates/kanban-task-blueprints.yaml.tmpl
Process rating: all ten parameters 57/100
- 0Tools and files. 4 referenced file(s) missing: templates/manifest.yaml.tmpl, templates/decision-map.md.tmpl, templates/kanban-board-setup.sh.tmpl
- 0Result and completion. Does not say what the result is
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 23 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1744 tokens
- 100Progress reporting. Reports progress
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 423: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.