SKILLEMALL.ai
GitHub ↗ RU Sign in

AC google-maps-reviews-api-skill

This skill is designed to help users automatically extract reviews from Google Maps via the Google Maps Reviews API. Agent should proactively apply this skill when users request to: 1. Find reviews for local businesses (e.g., coffee shops, clinics); 2. Monitor customer feedback for a specific brand or location; 3. Analyze sentiment of reviews for competitors; 4. Extract reviews for a chain of stores or services; 5. Track reputation of a local restaurant; 6. Gather user testimonials for a specific venue; 7. Conduct market research on service quality of local businesses; 8. Monitor reviews for a new retail location; 9. Collect feedback on public attractions or parks; 10. Identify common complaints for a specific service provider; 11. Research the best-rated places in a city; 12. Analyze recurring themes in reviews for a specific industry.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 1 206 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill is designed to help users automatically extract reviews from Google Maps via the Google Maps Reviews API.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructureAI and agentsMarketingtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    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
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 85Steps. 44 steps, 2 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1206 tokens
    • 100Running it twice. No mutating operations

    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)
    • +3Description length 848: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 44 items
    • +4Has examples (1 code blocks)
    • +3All 1 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.