Conciseness

The body is code-forward with terse single-line comments ("Async success", "Transform success value") and a one-line definition; the 'vs async/await' section's narrative ("errors hidden", "Error info lost", "errors typed and composable") is mild over-explanation a maximally lean reference could trim, so it sits at 'efficient; minor instances of over-explanation' rather than the 5-anchor's 'every token earns its place'.

Actionability

Examples use the real fp-ts API (TE.right, TE.map, TE.flatMap, TE.tryCatch, pipe, sequenceT, TE.match) and cover common cases (fetch wrapping, chaining, parallel, recovery); the minor gap is that helpers like fetchPosts, fetchComments, toNetworkError, and defaultUser are referenced but not defined, so it is 'mostly executable' rather than fully copy-paste-runnable.

Workflow Clarity

Organized into a logical Create -> Transform -> Execute -> Common Patterns -> comparison progression with an unambiguous single purpose and no destructive/batch operations (so the validation cap does not apply); it does not reach 5 because a reference card has no explicit validation/feedback-loop checkpoints, and at ~95 lines it is outside the under-50-line simple-skill exception that would auto-grant 5.

Progressive Disclosure

No bundle files exist and none are referenced; the content is a self-contained quick-reference card split into clear, well-labeled sections with no buried or nested references, matching 'good structure; most content appropriately placed'; it stops short of 5 because the body exceeds 50 lines, so the under-50-line simple-skill exception for an auto-5 does not cleanly apply.

Specificity

Names the domain ("TaskEither") but the only stated action is "Quick reference for TaskEither"; it does not enumerate concrete capabilities like create/transform/chain/execute, so it matches 'names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.

Completeness

Explicitly answers both: 'what' ("Quick reference for TaskEither") and 'when' ("Use when user needs async error handling, API calls, or Promise-based operations that can fail") with concrete trigger phrases, matching the 5-anchor; the 'Use when' clause is present so the missing-trigger cap does not apply.

Trigger Term Quality

Includes three natural phrases a user would say — "async error handling", "API calls", "Promise-based operations that can fail" — giving good keyword coverage; it sits above the 3-anchor (some keywords, missing variations) but misses synonyms like 'fp-ts', 'monad', 'retry', or 'chain async' that would reach 5.

Distinctiveness Conflict Risk

TaskEither is a specific fp-ts niche giving a clear identity, but the triggers "async error handling" and "API calls" are broad enough to risk minor overlap with general error-handling or retry skills, placing it at 'mostly distinct; minor overlap risk' rather than the 5-anchor's minimal conflict risk.