Documentation
Guides live in the repository so they are versioned with the code.
- Architecture overviewSystem shape, modules, ingestion, jobs and deployment modes.
- Decision recordsWhy SQLite, why no Redis, how ranking and licensing were decided.
- Database schemaEvery table, index and convention.
- Verification policyScanners, severities, expiry and appeals.
- Design systemTokens, components and accessibility targets.
- RoadmapPhases and the checks each must pass.
- REST APIPlanned public endpoints and what exists today.
Verification in brief
Each indexed version of a skill is identified by a commit and a content hash. Static scanners look for prompt injection, dangerous commands, credentials, data exfiltration, sensitive file access, vulnerable dependencies and integrity problems.
- Any open critical or high finding makes the version Flagged.
- Verified requires every required check to complete with no open medium finding, and it expires after 30 days.
- Everything else is Unverified, with the reason shown.
When a skill's content changes, the new version starts Unverified. There is no numeric safety score. Static analysis has false positives and false negatives; a label is evidence, not a certificate.
Ranking in brief
Search relevance and quality are separate. Quality is a weighted mix of popularity (logarithmic, at most 18% of the score), recent star growth, maintenance, content freshness, documentation, metadata quality, security status and confirmed compatibility.
- A flagged skill's score is cut to a quarter and it never appears in Trending.
- Trend figures come only from star counts this site has recorded itself; nothing is estimated or back-filled.
- Each skill page lists the factors that count most for its position.