Conciseness

Mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows, e.g. "Product Hunt is a website where users discover and share new products. It's primarily used by tech enthusiasts, entrepreneurs, and early adopters..." and the fluff "so you can focus on the integration logic rather than auth plumbing." It is not a 4 because the what-is-Product-Hunt paragraph is clear over-explanation, and not a 2 because the bulk is lean executable guidance rather than heavily padded.

Actionability

Provides copy-paste-ready commands covering the common cases — install (npm install -g @membranehq/cli@latest), login, connection ensure, action list/run with --input JSON, and request proxying with a flag table. It is not a 4 because the examples comprehensively cover install through execution with concrete flags and JSON output, matching the fully-executable anchor.

Workflow Clarity

There is a clear sequence (install → authenticate → ensure connection → wait for ready → search actions → run/proxy) with feedback loops ("poll again", "Keep polling until state is no longer BUILDING") and explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR). It is not a 5 because the "Step 2" referenced in the text is not visibly labeled as a step, creating a minor sequencing gap; not a 3 because validation checkpoints and error-recovery loops are present.

Progressive Disclosure

No bundle files exist, and the single SKILL.md is organized into well-labeled sections (Overview, Working with Product Hunt, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references. It is not a 5 because the skill exceeds 50 lines and the "Product Hunt Overview" nested list (Posts/Post, Comments/Comment) is low-value padding that could be trimmed; not a 3 because structure is clear and content is appropriately placed.

Specificity

"Manage data, records, and automate workflows" names the Product Hunt domain but the actions are generic and not Product-Hunt-specific (no mention of posts, comments, topics, or makers), matching the anchor where the domain is named but actions are minimal/generic. It is not a 3 because no concrete PH-specific action is enumerated, and not a 1 because the domain is explicitly identified.

Completeness

It states a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Product Hunt data"), fitting the anchor for both present with the "when" being somewhat generic. It is not a 5 because neither the what nor the when uses concrete trigger phrases, and not a 3 because the "Use when" clause is explicit so it is not capped at 3.

Trigger Term Quality

"Product Hunt" and "Product Hunt data" are relevant natural keywords, but common user phrasings and synonyms (e.g. "posts", "comments", "ProductHunt") are missing, fitting the anchor for some relevant keywords without common variations. It is not a 4 because coverage lacks the natural terms users would actually say, and not a 2 because the core term is the natural one rather than only technical jargon.

Distinctiveness Conflict Risk

"Product Hunt integration... interact with Product Hunt data" targets a distinct named service with low conflict risk, matching the anchor for mostly distinct with minor overlap risk. It is not a 5 because the templated "interact with X data" phrasing could be shared across similar integration skills, and not a 3 because the named app makes it clearly more specific than broad-overlap examples.