Label compatibility evidence
Source declarations, format inference, and test results stay separate. Possible support is never presented as verified.
Platform index
Choose Skills by Agent platform
Platform pages go beyond filtering: they explain install paths, compatibility evidence, permission boundaries, and portability limits across clients.
- Page type
- Platform pages
- Publish rule
- Evidence-gated
- Primary job
- Support decisions
Platform pages
Start with the environment where the Skill will run
The same SKILL.md is not automatically compatible with every agent client. Explicit declarations, static inference, and real tests are shown separately.
EvidenceSourceComputedTestedEditorial
Platform compatibilityEvidence labeled
Codex Skills
Agent Skills for Codex workflows. Compare installation paths, permission actions, and source evidence before adding one to your stack.
ExplorePlatform compatibilityEvidence labeled
Claude Code Skills
Find source-traceable Skills for Claude Code, with declared, inferred, and unverified compatibility clearly separated.
ExplorePlatform compatibilityEvidence labeled
Cursor Skills
Explore Skills for Cursor project workflows, separating native support from portable workflows.
ExplorePlatform compatibility pilotPilot
OpenClaw Skills
A pilot compatibility view for OpenClaw that only promotes Skills with explicit or reproducible evidence.
ExplorePage 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.
Explain installation differences
Show install locations, commands, triggers, credentials, and uninstall or rollback paths.
Index only qualified platforms
A platform needs at least 12 candidates, four qualified details, and a distinct compatibility matrix.
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.