CC gbp-local-seo-intent
Google Business Profile register: element, primary and supporting keywords, search intent, landing page, post dates, review rating and reply status, visibility and status. Use for local SEO.
The skill promises to organize Google Business Profile data for local SEO: keywords, search intent, landing pages, post dates, ratings, and reply status. Sounds useful for agencies managing local sites on paper.
Six files total, but quality scored 73 and process only 54. No critical errors found, though the low process score signals weak logic structure. Never ran on models, never tested in sandbox. That means the actual output remains unknown.
Don't install it. The skill is a raw prototype: without model runs, you won't know whether it extracts useful profile data or just piles everything into a heap.
Google Business Profile register: element, primary and supporting keywords, search intent, landing page, post dates, review rating and reply status…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 190 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 5813 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo"
Process rating: all ten parameters 54/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5813 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 190: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (2 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.