BF geo-human-editor
Audit and rewrite content to remove AI-generated feel by stripping markdown artifacts, eliminating AI vocabulary patterns, flagging hallucination risks, and restoring natural human voice. Use whenever the user mentions content sounding like AI, removing AI tone, making content more human, checking for AI feel, fixing mechanical writing patterns, or scanning for hallucinations and unverified claims in content.
Audit and rewrite content to remove AI-generated feel by stripping markdown artifacts, eliminating AI vocabulary patterns, flagging hallucination risks, and…
As a process F 35/100 · Will not run — References files that are not bundled: references/ai-vocabulary.md, references/patterns.md, references/hallucinations.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/ai-vocabulary.md - warning
missing-refreference to a missing file: references/patterns.md - warning
missing-refreference to a missing file: references/hallucinations.md
Process rating: all ten parameters 35/100
- 0Tools and files. 3 referenced file(s) missing: references/ai-vocabulary.md, references/patterns.md, references/hallucinations.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1146 tokens
- medium 1 test cases, all positive: not one "should refuse" or "should ask first"
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 412: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (5 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.