For platform teams whose samples org grew faster than anyone could keep it green
Sample TriageA sample is an executable promise - size the portfolio to the hours that keep it green.
Describe the platform and paste one line per sample repo or top-level directory. Your browser runs the skill's ordered triage rules - scan hits first, then retired pins and languages left out, the adoption path, owners, duplicates, single-concern repos to merge, red and unused - sums the kept upkeep against capacity, ranks the shape, reads the freshness contract against the sandbox and gives every archive a successor. Then the strategy, and the cleanup plan.
The platform, and a short interview free
The register free
The triage free
What the page flags
The gates
Every repo and its verdict
The portfolio shape, ranked
Area by area
Your register and index free
The portfolio register the skill builds first - one row per repo - and the canonical index every surface reads: ID, type, job, languages, status, successor.
Register (Markdown)
The portfolio strategy metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved triages
How it works - and what is sourced
The triage follows the skill, first match wins: a secret or vulnerable-dependency hit is fixed or archived this week; a retired SDK or API pin is archived with a redirect, and a language outside the coverage (tier-1 for quickstarts, references and templates; the dominant two or three for scenarios) is community-labelled when green with a community maintainer, archived otherwise; the adoption path - quickstarts, the first call, auth, the top-ticket scenario - is fixed, never archived for lack of an owner; no owner means archive; a duplicate merges into the survivor; a single-concern scenario in its own repo merges into the shared repo; red with measured near-zero usage is archived; the rest is kept. Unmeasured usage is never read as zero.
Kept upkeep uses self-set hours a quarter per artifact and language and is compared with your capacity. Every archive names a successor - the kept artifact serving the same job - or says none. With no sandbox, CI is build, lint and type-check only, and every artifact is "compiled, not run".