BB compassionate-systems-awareness-orchestrator
Orchestrate compassionate systems tools from issue or aspiration to wise action. Use when a class needs a complete inquiry workflow.
Orchestrate compassionate systems tools from issue or aspiration to wise action.
As a process B 68/100 · Nearly there — weak spots: result and completion, failures and branches, running it twice
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
frontmatter-keyunknown frontmatter key "effort" - note
frontmatter-keyunknown frontmatter key "skill_id" - note
frontmatter-keyunknown frontmatter key "skill_name" - note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "evidence_strength" - note
frontmatter-keyunknown frontmatter key "evidence_sources" - note
frontmatter-keyunknown frontmatter key "input_schema" - note
frontmatter-keyunknown frontmatter key "output_schema" - note
frontmatter-keyunknown frontmatter key "chains_well_with" - note
frontmatter-keyunknown frontmatter key "teacher_time" - note
edit-residuethe text marks something as outdated (lines 40): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 68/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 41 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 3050 tokens
- low 10 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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 132: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.