BF ai-communication-culture
Equips leaders to build flat, participative communication cultures that enable successful AI adoption by bridging technical and business teams, democratising data, and establishing feedback loops. Covers the symphony conductor model, soliciting expert feedback, removing bureaucratic obstacles, and building shared responsibility. Use when AI projects fail due to communication breakdowns, when data scientists and business leaders operate in silos, when employees lack channels to provide AI feedback, when hierarchical structures block information flow, or when leaders need to translate between technical and business perspectives.
As a process F 45/100 · Will not run — References files that are not bundled: ai-inclusive-collaboration.md, ai-purpose-driven-questions.md, ai-vision-and-strategy.md
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 634 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ai-inclusive-collaboration.md - warning
missing-refreference to a missing file: ai-purpose-driven-questions.md - warning
missing-refreference to a missing file: ai-vision-and-strategy.md - warning
missing-refreference to a missing file: ../frameworks/radical-candor.md - warning
missing-refreference to a missing file: ../frameworks/psychological-safety.md - warning
missing-refreference to a missing file: ../leadership/business-writing-for-leaders.md - note
frontmatter-keyunknown frontmatter key "complexity" - note
frontmatter-keyunknown frontmatter key "stage" - note
frontmatter-keyunknown frontmatter key "related_skills"
Process rating: all ten parameters 45/100
- 0Tools and files. 6 referenced file(s) missing: ai-inclusive-collaboration.md, ai-purpose-driven-questions.md, ai-vision-and-strategy.md
- 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. 19 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 4546 tokens
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 634: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.