Reason for every item
Explain the Skill's responsibility in the workflow—not just its name.
Curated collections
Combine Skills around complete workflows
Public collections explain sequence, responsibility, and inclusion reasons. Personal saves remain in a private local stack.
- Page type
- Workflow collections
- Publish rule
- Evidence-gated
- Primary job
- Support decisions
Workflow collections
A larger stack is not automatically better
Every stage should fill a distinct workflow gap and disclose inputs, outputs, conflicts, and human approval points.
EvidenceSourceComputedTestedEditorial
Page admission
Not every combination deserves a URL
Every aggregation page needs a distinct decision job, enough qualified entities, and useful content beyond a repeated card list.
Show sequence and conflict
Expose ordering, overlapping instructions, and human approval stages.
Keep personal stacks private
Device-local saves do not create indexable user-generated pages.
EntityIdentity, source, and lifecycle verified
DemandThe page answers a distinct user question
EvidenceAt least two unique value classes
Continuous learning
Pages evolve with real search and product behavior
GSC queries, internal search, saves, install copies, source clicks, and maintenance cost determine whether a page is enriched, merged, paused, or scaled.