Conciseness

The ~9-line body is lean with zero padding: "call the andrewrendon connector's `get_business` tool once in the conversation, unless you already have its result" plus three tight rules. It assumes Claude's competence and explains nothing the model already knows, matching the 'every token earns its place' anchor.

Actionability

The guidance is concrete and executable for an instruction-only skill: a named tool (`get_business` on the andrewrendon connector), an explicit call-once condition, and specific behavioral rules including an edge case ("say that it isn't written down rather than inventing it"). It falls short of 5 only because no examples illustrate the desired voice, signing, or phrasing of the missing-facts disclaimer.

Workflow Clarity

For this simple two-phase skill the sequence is unambiguous: fetch context first (with an idempotency checkpoint "unless you already have its result"), then apply the three rules, with an explicit fallback when notes lack needed facts. No destructive or batch operations are involved, so the simple-skill exception applies and the single action is fully clear.

Progressive Disclosure

The skill is under 50 lines with no need for external references (the business details live in the connector, not in bundle files), and the body is well organized as an instruction line plus a bulleted rule list. Per the rubric's simple-skill guidance, this earns a 5 with no separate files required.

Specificity

"Reads how this business works before writing or answering anything for it" names the domain and one concrete action (reading business context via the connector), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not reach 4 because no additional specific capabilities are listed, and it is above 2 since the action is concrete rather than generic.

Completeness

It explicitly answers both what ("Reads how this business works before writing or answering anything for it") and when ("Use for any email, reply, note, post, bio, checklist, job ad, out-of-office, idea or answer that is for the business, its clients, customers or team, or that names one of them") with concrete trigger phrases. This clearly matches the 5 anchor and exceeds the 4 anchor where the 'when' is only adequately explicit.

Trigger Term Quality

"any email, reply, note, post, bio, checklist, job ad, out-of-office, idea or answer" plus "its clients, customers or team" gives good natural keyword coverage that users would actually say. A few common variations (e.g. "message", "letter", "announcement", "newsletter") are missing, so it does not reach the comprehensive synonym coverage of a 5.

Distinctiveness Conflict Risk

The niche is distinct — fetching and applying one business's own context — so it is unlikely to trigger for the wrong skill, fitting the "mostly distinct; minor overlap risk" anchor. It does not reach 5 because the very broad triggers ("any... idea or answer that is for the business") overlap with general writing and email-drafting skills.