CC gator-gate
Validate and monitor OpenShell GitHub issues and PRs using the gator:* state machine. Use when asked to triage issues/PRs for project validity, gate PRs, run gator, validate submissions, or monitor PRs toward merge readiness.
Validate and monitor OpenShell GitHub issues and PRs using the gator: state machine.
As a process C 57/100 · Has gaps — References files that are not bundled: scripts/agents/gator/skills/gator-gate/SKILL.md, scripts/agents/gator
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 19643 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/agents/gator/skills/gator-gate/SKILL.md - warning
missing-refreference to a missing file: scripts/agents/gator - note
edit-residuethe text marks something as outdated (lines 159, 557, 558, 759, 834): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 57/100
- 0Tools and files. 2 referenced file(s) missing: scripts/agents/gator/skills/gator-gate/SKILL.md, scripts/agents/gator
- 10Execution cost. Instruction body is 19643 tokens: crowds the task out of the window
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 240 steps, 2 vague phrases
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 24 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (17 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
- +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 225: enough signal without eating the budget
- +4Structure: 51 headings
- +3Step-by-step instructions: 240 items
- +4Has examples (31 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.