How a path earns “reviewed.”
Every Guide is assembled from accepted components, checked against explicit source policies, and published only when its required evidence and relationships are complete.
- Official source
- Normalized facts
- Reviewed components
- Complete Guide
- Published path
We verify the source
Guided reads the official MCP Registry and a reviewed list of Skill publishers. Community lists can reveal candidates, but repeated claims do not become facts.
We normalize what it does
We record bounded facts about each component in a consistent format, including its purpose, compatibility, requirements, freshness, and source evidence.
We keep missing facts visible
If information may be old or the publisher has not stated it, the record says so. Guided does not fill gaps with generated claims.
We compose around an outcome
A Guide connects accepted Skills and MCP servers to one reviewed outcome, assigns each component a role, and puts the working recipe in order.
We publish only complete paths
A Guide remains unavailable until its required components, evidence, relationships, and publication state are complete and current.
We disclose changes
Corrections, stale evidence, and removals stay visible. The official publisher remains the authority for current installation and usage instructions.
“Reviewed” describes a documented process—not a promise that every component is suitable for every situation.