Home / Reports / google_search_console-automation

google_search_console-automation

Validated 5 Jun 2026 · Repository
PRO
41
Poor
1 critical
6 warnings
9 suggestions
93 passed
Domain scores
Anti-Slop
100
Accessibility
100
Enterprise
100
Issues

Critical (1)

1.1-name-charsline 2
Name must be lowercase letters, numbers, and hyphens only
Fix: Use lowercase letters, numbers, and hyphens

Warnings (6)

14.1-no-success-criterialine 1
No concrete success criteria found for eval readiness
Fix: Add pass/fail criteria or measurable outcomes (e.g., 'must return valid JSON', 'output < 100 lines')
19.2-reviewer-no-criterialine 8
Reviewer pattern detected but no evaluation criteria documented
Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)
4.5-desc-no-triggersline 2
Description lacks triggering conditions
Fix: Add phrases like 'Use when...', 'Triggers on...', or 'Applies to...' to help Claude select this skill
1.2-desc-whatline 3
Description missing WHAT clause (action verb) - recommended by agentskills spec
Fix: Consider starting with what the skill does, e.g., 'Creates...', 'Generates...', 'Validates...'
1.2-desc-whenline 3
Description missing WHEN clause - recommended by agentskills spec
Fix: Consider adding 'Use when...' or 'Activate when...' to description
7.3-mcp-no-versionline 1
MCP skill without protocol version specification
Fix: Specify protocol version (e.g., 2024-11-05)

Suggestions (9)

2.9-mcp-tool-unqualifiedline 12
MCP tool reference 'google_search_console' may need server prefix
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
17.4-no-interface-sectionline 8
Input and output contracts exist but lack a dedicated interface section
Fix: Add a ## Interface or ## I/O section to consolidate contract documentation
3.4-gerund-namingline 2
Skill name could use gerund form for clarity
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
18.1-no-confidence-signalline 1
No confidence signal found for orchestrator decision-making
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
18.3-no-structured-outputline 1
No structured output format defined for machine consumption
Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results
4.2-ambiguous-termline 83
Ambiguous term 'many' found
Fix: Replace with specific, measurable criteria
4.3-output-formatline 1
Skill mentions output but doesn't specify format
Fix: Add an '## Output' section with format examples
1.8-unexpected-fieldline 4
Unexpected frontmatter field 'requires'
Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata
7.3-mcp-no-transportline 1
MCP skill without transport type specification
Fix: Specify transport type (stdio, sse, or websocket)
OWASP Agentic (Cat 26)
Agent surface detected — performs consequential actions
2 warning
ASI-01: skippedASI-02: skippedASI-03: skippedASI-04: skippedASI-05: skippedASI-06: skippedASI-07: skippedASI-08: skippedASI-09: skippedASI-10: failASI-11: fail
Badges
skillcheck ✕ passed skillcheck antislop 100 skillcheck WCAG AA skillcheck WCAG AAA skillcheck enterprise
Ship with confidence

Get a report like this for your own skill

Run the free validator to see your structural score, then unlock the substance checks — anti-slop, security, accessibility, agent-readiness — that move a skill from valid to safe to ship.