BF catalyst-design
Catalyst design guidance skill. Based on a layered, traceable, and dynamically evolving methodology system (fusing catalyst-search retrieval results, user-acquired materials via AI/skills, and external channels), it provides advice on catalyst composition selection, structural design, synthesis strategy, and performance optimization. Runs standalone; also collaborates with catalyst-search — consuming its structured literature output (matrix) for sharper targeting and feeding new evidence back into the methodology base.
Catalyst design guidance skill.
As a process F 44/100 · Will not run — References files that are not bundled: references/design_methodology.md, references/methodology_update_protocol.md, references/methodology_registry.md
How to improve
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/design_methodology.md - warning
missing-refreference to a missing file: references/methodology_update_protocol.md - warning
missing-refreference to a missing file: references/methodology_registry.md - warning
missing-refreference to a missing file: templates/design_proposal.md - warning
missing-refreference to a missing file: templates/citation_gb7714.md - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 44/100
- 0Tools and files. 5 referenced file(s) missing: references/design_methodology.md, references/methodology_update_protocol.md, references/methodology_registry.md
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (catalyst-design) differs from the folder (catalyst-design-skill)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 82 steps
- 100Execution cost. Instruction body is 2618 tokens
- low 22 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)
- +1No license
- +2Single-language instructions
- +3Description length 524: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 82 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.