Loading the registry…
Mastery and big picture skill for the Lennart Poettering / systemd ecosystem. Covers the full blog canon: "Fitting Everything Together" OS architecture vision, UKI/PCR/TPM trusted boot chain, Discoverable Partitions Specification, LUKS2 hardware unlock (FIDO2/TPM2/PKCS#11), factory reset + stateless systems, dynamic users, portable services, developer workflow (sysext + nspawn off host /usr), systemd v256–v260 feature landscape, mkosi, casync, Amutable (2026 company), and how everything maps to yubiOS (YubiKey replaces TPM2 for secrets). Use when: - Designing or reviewing yubiOS architecture decisions - Deciding which modularity mechanism to use (sysext vs portable service vs nspawn) - Understanding PCR assignments, UKI sections, boot phases, or rollback protection - Explaining why a specific systemd component was chosen over an alternative - Auditing whether a yubiOS design goal is met - Questions about LUKS2 hardware unlock mechanics (FIDO2, TPM2, PKCS#11) - Understanding DPS partition types, systemd-dissect, systemd-repart - Developer workflow: testing builds with sysext, running nspawn off host /usr - Dynamic users, StateDirectory, portable services, portablectl - Researching systemd v256–v260 features relevant to yubiOS - Any "big picture", "why does this work this way", or "what would Lennart do" question Trigger phrases: "0pointer vision", "fitting everything together", "hermetic /usr", "trust chain", "PCR", "UKI", "boot phases", "FIDO2 unlock", "DPS", "discoverable partitions", "portable service", "sysext", "dynamic user", "factory reset", "stateless system", "Amutable", "architecture decision", "image-based OS", "big picture", "what would Lennart do", "why use X instead of Y".
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.
15 critical findings reported by cisco-skill-scanner, agent-audit-kit, 13 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 -- 'yubi-os/yubios (0pointer-mastery)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'yubi-os/yubios (0pointer-mastery)' ~/.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
307 findings · 61.5s
v0.3.74
83 findings · 26.6s
v0.1.0
3 findings · 6.9s
v0.1.0
25 findings · 6.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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 15, 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 418 findings above stand exactly as their scanners reported them, at full severity.