Loading the registry…
Extract and validate the data in a commercial real estate spreadsheet — rent rolls, operating statements, T-12s, budget-variance reports, argus exports, pro formas, broker underwriting models — showing every table in chat for confirmation before writing a traced workbook and a branded extraction report. Use when the input is an .xlsx, .xlsm, .xltx, .csv or .tsv holding CRE data and the wanted output is checked, structured data with provenance. Triggers - extract the data from this workbook, read this rent roll spreadsheet, what is in this xlsx, pull the tenant schedule out of this model, check whether this T-12 foots, validate this rent roll, get the tables out of this spreadsheet, cross-foot this operating statement, tie out these numbers, audit this pro forma's arithmetic. Do NOT use to build, edit, chart or reformat a spreadsheet (use xlsx), or to write an argued memo from a model (use kt-corporate-memo).
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'kyletristentran/kt-cre-design-system (cre-extract-excel-data)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'kyletristentran/kt-cre-design-system (cre-extract-excel-data)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
12 findings · 9.4s
v0.3.74
1 finding · 5.0s
v0.1.0
0 findings · 4.5s
v0.1.0
0 findings · 4.5s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 13 findings above stand exactly as their scanners reported them, at full severity.