Conciseness

Core guidance is dense and high-signal (Quick Reference table, decision tree), but there is notable duplication: "Effects sao uma valvula de escape... servem pra sincronizar com um sistema externo" is restated in "Quando Nao Usar" and "Quando DE FATO precisa de Effect"; the two-moments intro ("Esta skill entra em dois momentos: (1)... (2)...") repeats verbatim as the first two "Quando Usar" bullets; and "Handoff — Frontend Engineer (skill 04) — recebe o código já revisado" duplicates "Integracao com Pipeline — Frontend Engineer (04): consultar antes de escrever useEffect novo". This is more than minor trimming (anchor 4) but far from padded tutorial prose (anchor 2).

Actionability

Concrete, situation-specific direction throughout: the Quick Reference table maps each case to an exact alternative ("useState + useEffect" → "Calcular durante o render", "useEffect com setState" → "key prop", fetch → "useEffect com cleanup OU lib de fetch"), and the decision tree yields a definite verdict per branch. Not a 5 because the body contains no before/after code — the examples are deferred to anti-patterns.md — so it tells you which API to use but never shows the pattern; per the code-vs-instruction note this stays at mostly-executable rather than fully executable.

Workflow Clarity

The flow is coherent and has explicit validation: two entry points ("ao escrever um useEffect novo, como checklist antes de commitar; ao revisar codigo/PR"), a decision procedure (the Arvore de Decisao), and a completion checkpoint ("Evidencia de Conclusao — código revisado não tem useEffect cobrindo um dos 9 antipadrões... toda sincronização com sistema externo restante está justificada"). Not a 5 because the final verification depends on the 9-antipattern list in anti-patterns.md, which is not present in the bundle, so the checklist cannot be fully executed from the skill as provided.

Progressive Disclosure

The design is right — a lean overview with well-signaled, one-level-deep, accurately annotated references ("[anti-patterns.md](./anti-patterns.md) — 9 antipatterns com exemplo ruim/bom lado a lado", "[alternatives.md](./alternatives.md) — as alternativas em detalhe") — but neither referenced file exists in the bundle (no references/ directory, only SKILL.md present), so both links dangle and the bulk of the detailed guidance is unreachable. Missing core referenced files is more than a minor organization gap (anchor 4); the body structure itself is far better than anchor 3's 'not clearly signaled' case, but navigation fails at runtime.

Specificity

Names the domain and purpose concretely — "Checklist React para decidir quando não usar useEffect em estado derivado, fetch, sincronização e reset de props" — enumerating four specific coverage areas. Not a 5 because it describes one action (deciding/reviewing) applied to topic areas rather than listing multiple distinct concrete actions; the PR-review and suggest-alternative actions from the body are absent. Not a 3 because it goes well beyond 1-2 generic actions with its enumerated scenario coverage.

Completeness

Explicitly answers both parts: the what is "Checklist React para decidir quando não usar useEffect em estado derivado, fetch, sincronização e reset de props" and the when is an explicit "Trigger em:" list of nine concrete trigger phrases. This matches the anchor 5 example structure (clear what + concrete trigger phrases) exactly.

Trigger Term Quality

Nine natural trigger phrases covering the API name ("useEffect"), symptoms ("race condition no fetch", "por que renderizou duas vezes"), patterns ("effect chain", "notificar parent via effect"), and a related API ("useSyncExternalStore"). This is comprehensive for the skill's scope — these are exactly the phrases a developer would say when needing this skill — so it does not fall to 4.

Distinctiveness Conflict Risk

Clear niche (React useEffect avoidance) with distinctive triggers like "effect chain", "notificar parent via effect", and "por que renderizou duas vezes" that virtually no other skill would claim. Not a 4: even the broadest trigger ("useSyncExternalStore") is directly relevant to this skill's alternatives, keeping conflict risk minimal.