AF review-ai-writing
Detect AI-generated writing patterns in developer text — docs, docstrings, commit messages, PR descriptions, and code comments. Use when reviewing any text artifact for authenticity and clarity, or when the user mentions ai writing, ai-generated or robotic writing, text that sounds like AI or ChatGPT, or writing quality. Builds on the docs-style core writing principles.
As a process F 55/100 · Will not run — References files that are not bundled: ../../../beagle-core/skills/review-verification-protocol/SKILL.md, ../../../beagle-core/skills/llm-artifacts-detection/SKILL.md, references/*.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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../beagle-core/skills/review-verification-protocol/SKILL.md - warning
missing-refreference to a missing file: ../../../beagle-core/skills/llm-artifacts-detection/SKILL.md - warning
missing-refreference to a missing file: references/*.md
Process rating: all ten parameters 55/100
- 0Tools and files. 3 referenced file(s) missing: ../../../beagle-core/skills/review-verification-protocol/SKILL.md, ../../../beagle-core/skills/llm-artifacts-detection/SKILL.md, references/*.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 9 branches
- 70Execution cost. Instruction body is 4240 tokens
- 85Steps. 77 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (8 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)
- +1No license
- +2Single-language instructions
- +3Description length 372: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 77 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.