add system-diagnostic skill

_build-log.md

@@ -55,3 +55,11 @@
 **Files updated:** skills/daily-briefing/SKILL.md, skills/shutdown-routine/SKILL.md, skills/weekly-review/SKILL.md
 
 ---
+
+## Video 9 — System Diagnostic
+**Date:** 2026-04-05
+**Findings:** All 9 skills have index entries and SKILL.md files; no trigger collisions; AGENTS.md functional but missing file naming conventions; no MCP connectors yet (documented as TBD); vikunja-tasks added outside video series (no build log entry); meeting-notes skill never built
+**Recommendations:** Email drafts skill, meeting notes skill, document file naming conventions in AGENTS.md
+**Files created:** system-health-report.md (workspace root)
+
+---

system-diagnostic/SKILL.md

@@ -55,17 +55,10 @@ For each `SKILL.md`, verify:
 - [ ] Has `description` frontmatter field (this is the primary trigger mechanism — missing or vague descriptions cause skills to not fire)
 - [ ] Body has at least minimal instructions (not just a stub)
 
-### 6. Build Log Currency
+### 6. Dependencies Check
-
-- Check which videos are logged in `skills/_build-log.md`
-- Note any skills that exist but have no corresponding build log entry
-- Flag if the log appears to be missing entries (e.g., a skill exists with no record of when or why it was built)
-
-### 7. Dependencies Check
 
 For any skill that lists dependencies (tools, CLIs, MCP connectors):
-- Note whether those dependencies are confirmed available or still pending
+- Note whether those dependencies are confirmed available
-- Flag anything that's listed as "TBD" or "future" and has been that way for a while
 
 ---