AB cx-commissioning-plan-drafter
Use this skill when a commissioning authority (CxA), building commissioning professional, MEP engineer, or owner's representative needs to draft a project commissioning plan aligned to ASHRAE Guideline 0-2019, LEED v4/v4.1 EA Prerequisite (Fundamental Commissioning), or federal/agency commissioning requirements. Covers commissioned systems scope, Cx team roles and responsibilities, project schedule, documentation and submittal requirements, functional performance test framework, and issues log protocol. Produces a DRAFT Cx Plan for CxA review before mechanical and electrical system installation begins.
Use this skill when a commissioning authority (CxA), building commissioning professional, MEP engineer, or owner's representative needs to draft a project…
As a process B 75/100 · Nearly there — weak spots: when it triggers
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 75/100
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 89 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3481 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 609: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 89 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.