Conciseness

The body is mostly lean operational commands with focused Membrane-specific detail; minor over-explanation like "so you can focus on the integration logic rather than auth plumbing" could be trimmed, fitting anchor 4 over 5.

Actionability

Concrete executable commands (membrane login, connection ensure, action run, request) plus a flags table cover common cases copy-paste ready; the inconsistent membrane vs npx @membranehq/cli@latest invocation and placeholder substitution keep it at 4 rather than 5.

Workflow Clarity

The install→authenticate→connect→search→run sequence has explicit state-machine feedback loops (poll until READY, re-poll after client action, check error field), but the "Step 2" and "1b" labels reference unlabeled steps, a minor navigation gap matching anchor 4.

Progressive Disclosure

The single file is well-sectioned with clear headers and no nested references; at ~140 lines it exceeds the simple-skill 5-case threshold and the proxy flags table is reference-like material kept inline, fitting anchor 4.

Specificity

"Manage data, records, and automate workflows" names the EduMe domain but the actions are generic ("manage data", "automate workflows") rather than concrete, matching anchor 2 over anchor 3 whose actions must be concrete.

Completeness

Both "what" ("EduMe integration. Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with EduMe data") are present and explicit, but the "when" could be more specific, matching anchor 4 rather than 5.

Trigger Term Quality

The explicit trigger "Use when the user wants to interact with EduMe data" supplies a relevant keyword but misses common natural variations users would say (training, lessons, learning paths, onboarding), fitting anchor 3.

Distinctiveness Conflict Risk

Naming a specific platform ("EduMe integration") gives a clear niche with minimal conflict risk, though the generic "manage data" phrasing leaves minor overlap with general data skills, fitting anchor 4.