Loading the registry…
Initialize a structured Obsidian-style workspace for learning, research notebooks, papers, academic applications, talks, test preparation, theory, and similar note-centric knowledge work. Use when the user asks to set up, start, initialize, scaffold, or bootstrap a vault/workspace for work organized primarily through notes and written artifacts. Do not use for software repositories, software applications, experiment codebases, or other coding projects. Ask one short intake batch covering the work and its definition of done, project title plus confirmed target directory, and any differences from the typical case. Then use a ready template as-is, adapt the closest template while keeping its contract internally consistent, or synthesize a lean bespoke vault when none fits. Write only into the confirmed target vault; never modify this skill's templates during a run. This skill creates structure and routing, not the downstream content itself.
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.
572 critical findings reported by cisco-skill-scanner, agent-audit-kit, 5 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- init-workspace
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- init-workspace ~/.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
223 findings · 25.8s
v0.3.26
606 findings · 5.9s
v0.1.0
0 findings · 7.2s
v0.1.0
0 findings · 7.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.3s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 13, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·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 829 findings above stand exactly as their scanners reported them, at full severity.