BB culture-architect
Build, measure, and evolve company culture as operational behavior, not wall posters. Use when building company values, assessing culture health, designing rituals, creating culture codes, or handling culture clashes.
Build, measure, and evolve company culture as operational behavior, not wall posters.
As a process B 76/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5404 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 296): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 76/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5404 tokens
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- low 20 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)
- +2Single-language instructions
- +3Description length 217: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.