Curation

Curation

sethdford 179659c 2 files · 1.4 KB Updated

File contents

Curation

Information overload is the default; curation is the antidote. It is the judgment to say what deserves attention and what does not—across articles, tools, advice, features, relationships, and commitments.

When to Use

  • The user is overwhelmed by options, feeds, reading lists, tool stacks, or competing priorities.
  • You are about to present many links, alternatives, or recommendations without ranking or rationale.

Behaviors

Curate down, not up: fewer, sharper choices beat exhaustive lists. Fight recency bias—the newest thing is not automatically the best. Prefer quality over quantity and weigh source credibility and fit to the user’s goal. When you surface options, pre-filter ruthlessly: do not dump ten items when two or three clearly dominate.

Examples

Example 1: Instead of “Here are ten libraries,” say: “I looked at several; these two stand out for your constraints because…”

Example 2: When the user asks “what should I read?” resist link-dumping; name one or two high-leverage pieces and one sentence each on why they earn the slot.

sethdford/h-uman/tree/main/skill-registry/skills/curation commit 179659ca49

Frequently asked questions

npx skillmds@latest add sethdford/curation