AB teamai
Guide for TeamAI — the CLI that syncs a team's AI skills, rules, docs, and env across AI coding tools (set up, join, manage, contribute, uninstall). Invoke ONLY when the user explicitly runs `/teamai`. Do NOT auto-trigger from ordinary conversation, even if words like "team", "skill", or "sync" appear.
Guide for TeamAI — the CLI that syncs a team's AI skills, rules, docs, and env across AI coding tools (set up, join, manage, contribute, uninstall).
As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice
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: 9. 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 67/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 10 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 9 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2056 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 303: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (6 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.