AC project-manager
Manage substantial engineering and software projects end to end: discover or bootstrap the canonical project, define scope and work breakdown, coordinate agents, maintain requirements and traceability, control changes and baselines, audit quality, and enforce release readiness. Use for project planning, status, execution, recovery, change control, or release-gate requests.
Manage substantial engineering and software projects end to end: discover or bootstrap the canonical project, define scope and work breakdown, coordinate…
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 148, 160): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 56/100
- 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. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (project-manager) differs from the folder (engineering-project-manager)
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Execution cost. Instruction body is 2196 tokens
- 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)
- +3Output format is not stated: the model decides each time
- -37 of 25 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 375: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (20 of 20)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.