01
Trace the source
A listing needs a public repository, an exact skill path, and an install command grounded in the Skills CLI.
Methodology
Trust starts with saying exactly what was checked.
This first release combines a source-led catalog with outcome-led stacks. Its job is to make every inclusion and sequence inspectable.
02
Describe the job
We explain intended use, expected outcomes, and requirements in plain language before promotional claims.
03
Name the limit
Source checks are not security audits. Installation targets are not universal compatibility tests. Ambiguous licenses stay ambiguous.
How a stack earns its place.
Every included skill must have a clear role in the outcome, a deliberate position in the workflow, and a catalog record that keeps its upstream source visible.
Stack curation is separate from compatibility testing, benchmarking, and security auditing. When those checks have not happened, the stack says so plainly.
What a listing can and cannot tell you.
Included
- Repository and exact source path
- Install command and publisher
- License label found upstream
- Plain-language use cases and requirements
Not implied
- A security audit
- Endorsement by every named agent
- Ongoing maintenance guarantees
- A popularity or quality ranking
Inspect the first complete workflow.
Every included skill links back to its own source-led record.