BC local-falcon
Expert guidance on AI Visibility and Local SEO from Local Falcon, the pioneer of geo-grid rank tracking. Provides deep knowledge on optimizing for AI search platforms (ChatGPT, Gemini, AI Mode, AI Overviews, Grok), local pack rankings, Google Business Profile optimization, and actionable strategies for agencies, enterprises, and SMBs. Includes guidance on using Local Falcon's MCP server for data-driven analysis.
As a process C 59/100 · Has gaps — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5354 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "documentation" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "categories" - note
frontmatter-keyunknown frontmatter key "capabilities" - note
frontmatter-keyunknown frontmatter key "mcp_integration" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "invocation"
Process rating: all ten parameters 59/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (local-falcon) differs from the folder (local-visibility-skill)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 6 branches
- 70Execution cost. Instruction body is 5354 tokens
- 100Steps. 93 steps
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
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)
- -246 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 415: enough signal without eating the budget
- +4Structure: 53 headings
- +3Step-by-step instructions: 93 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.