Conciseness

The body is mostly operational CLI content Claude would not know, but it opens with padding Claude already knows ("Google My Business helps local businesses manage their online presence across Google, including Search and Maps...") and includes light marketing fluff ("so you can focus on the integration logic rather than auth plumbing"). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the intro paragraph is clearly removable.

Actionability

It provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a popular-actions table with real keys and flag reference. It is not 5 because there is no fully-worked end-to-end example with realistic parameters for a representative action, leaving a minor gap in covering the common cases.

Workflow Clarity

The connect → search → run sequence is clear and the connection-readiness branch (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) includes a real poll-and-re-poll feedback loop. However, the popular-actions table includes destructive operations (Delete Location, Delete Place Action Link) with no validation/verification guidance, which caps workflow clarity at 3 per the destructive-operations rule; a broken 'skip to Step 2' reference with no labeled Step 2 further weakens the sequence.

Progressive Disclosure

No bundle files exist, and the body is organized into well-labeled sections (Overview, Working with GMB, Install, Auth, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with easy navigation. It is not 5 because the skill exceeds 50 lines and the sizable popular-actions table is inlined rather than split into a separate reference, leaving minor organization gaps.

Specificity

The description names the domain and entities ("Manage Businesses, Users") but the only action verb is the generic "Manage", which is minimal rather than concrete — matching the anchor where actions are minimal or generic. It does not reach 3 because there is no second distinct concrete action (e.g. 'list', 'create', 'answer'), only one generic verb applied to two nouns.

Completeness

Both halves are present: "what" via "Google My Business integration. Manage Businesses, Users." and an explicit "when" via "Use when the user wants to interact with Google My Business data." It is not a 5 because the trigger is a single generic clause rather than concrete varied trigger phrases, matching 'Has both what and when; when could be more explicit or specific'. The present 'Use when...' clause means the missing-trigger cap at 3 does not apply.

Trigger Term Quality

It repeats the natural product name "Google My Business" and phrases like "interact with Google My Business data", but offers no common synonyms or variations a user might say (GMB, business listings, reviews, locations, posts, Q&A). This fits 'some relevant keywords but missing common variations or synonyms' rather than 4, which requires broader natural-term coverage.

Distinctiveness Conflict Risk

Naming the specific product "Google My Business" gives it a clear niche and the trigger references that product directly, so conflict risk is low. It stops short of 5 because the generic "Manage Businesses, Users" could overlap with other business-management skills, fitting 'mostly distinct; minor overlap risk'.