BF ai-expert-team
Use when a complex problem needs a structured expert team rather than a single general answer. Runs a Single-CEO Expert Council with a Nuwa-style decision lens, Agency-style specialist selection, NEXUS handoffs, evidence-backed expert reports, and a verification layer before final synthesis.
Runs a Single-CEO Expert Council with a Nuwa-style decision lens, Agency-style specialist selection, NEXUS handoffs, evidence-backed expert reports, and a…
As a process F 63/100 · Will not run — References files that are not bundled: assets/agency-agents, assets/nuwa-skill, assets/.gitignore
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 292 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 6446 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: assets/agency-agents - warning
missing-refreference to a missing file: assets/nuwa-skill - warning
missing-refreference to a missing file: assets/.gitignore
Process rating: all ten parameters 63/100
- 0Tools and files. 3 referenced file(s) missing: assets/agency-agents, assets/nuwa-skill, assets/.gitignore
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 33 mutating operations with no state check
- 60Consistency. The Hermes dialect needs category and tags
- 70Execution cost. Instruction body is 6446 tokens
- 100Steps. 225 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (8 tags): a typed call is more reliable
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 292: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 225 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.