菜单
Run 15 health checks on wiki/ (structural, semantic, provenance). Use weekly or after wiki-ingest batches. Read-only — does not auto-fix. Do NOT use to fix issues (use wiki-ingest / wiki-cross-linker). Obsidian wiki 健全性チェック・健康檢查。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | wiki-lint |
| description | Run 15 health checks on wiki/ (structural, semantic, provenance). Use weekly or after wiki-ingest batches. Read-only — does not auto-fix. Do NOT use to fix issues (use wiki-ingest / wiki-cross-linker). Obsidian wiki 健全性チェック・健康檢查。 |
Runs 15 health checks across the wiki and reports issues without modifying pages. User decides which fixes to apply.
See lint-checks.md for full check definitions.
.obsidian-wiki.config for OBSIDIAN_WIKI_VAULT_PATH (defaults wiki/). If only legacy .env exists, instruct user to run /wiki-setup to migrate./wiki-setup and /wiki-ingest first".Build:
wiki/.manifest.json (for L10 check)Execute all 15 checks defined in lint-checks.md:
Structural (must-fix):
Semantic (should-fix):
## Source wikilinks are handled by L14)aliases: should be present and non-empty; authority: references/language-policy.md)/wiki-merge)Provenance (advisory):
## Source wikilink format (basename / no path / no .md; basename matches source_path stem)Severity: L01–L04, L07 → error (L14 path/extension violations also → error). L05, L06, L08, L09, L10, L12, L13, L14 (missing/empty/basename-mismatch), L15 → warning. L11 → info.
The mechanical subset (L01–L04, L07, L14 — both its error and warning forms — plus a PARSE error lane for unreadable pages) can be run in seconds via scripts/wiki_lint_check.py instead of manually — read-only, same as this skill's charter.
Use the format in lint-checks.md. Group by severity (errors first), then by check ID. Show file path with line number where applicable.
If errors > 50, collapse to "showing first 50 of N errors" and ask if user wants to see all. Long lint reports are signal — propose a remediation strategy rather than dumping everything.
Append to wiki/log.md:
| YYYY-MM-DD | lint | scope=full | <E> errors, <W> warnings, <I> info |
Group issues by their fix recipe (per the table in lint-checks.md):
Top fixes (by impact):
1. Re-run `/wiki-ingest` on 3 sources → resolves 8 issues (L01, L09)
2. Run `/wiki-cross-linker` → likely resolves most L06 orphans
3. Hand-fix 2 broken wikilinks (L07) — see report above
4. Run `/wiki-auto-research` on 5 Open Questions surfaced (L11)
wiki/<category>/*.md)Write scope: only appends one entry to wiki/log.md per run (audit trail). No other writes.
| Trigger | Why |
|---|---|
| Weekly cadence | Catch stale pages, orphans, broken links from organic drift |
After large /wiki-ingest batch (>10 pages) | Verify format compliance before pages compound |
Before /wiki-auto-research campaign | Identify Open Questions inventory to prioritize |
| After page-format spec changes | Mass re-validate against new spec |
| On-demand when wiki "feels off" | Exploratory diagnostic |
Append-only bitemporal store for validated operational-KPI series-points (US SEC primary-source layer). Persists file-per-series JSON keyed by company+kpi_id under a durable DATA dir, keeping full history so a restatement appends a superseding record and a point-in-time query sees only what was known then. 営業 KPI 二時制追加専用ストア。營運 KPI 雙時態 唯附加儲存層。
Layer-1 unified data fetch across US/JP/TW/KR/CN equities + macro — one pack.py facade, auto market detection from ticker suffix (.TW/.KS/.SS/.T/ bare-4-digit), 7 pack types (snapshot / memo-fetch / comps-multiples / screener-batch / regime-pack / kpi-quarterly / kpi-topline-backfill). Emits a raw data pack（原始資料包，非渲染卡片）— structured JSON straight from source clients including SEC EDGAR, EDINET, TWSE, and FRED (+14 more) through a shared cache layer; use this for a 資料層 health check, verifying cache writes/hits (快取), or fetching by source name (EDINET/EDGAR/TWSE/etc). Pure I/O, no analysis — for regime classification/判斷 (e.g. an Investment Clock verdict), use analysis-macro-regime instead. Consolidates the per-country data-{us,jp,tw,kr,cn} client scripts behind one CLI + shared cache layer.
Deliver a Mental-Model-first briefing before asking the user to decide a non-trivial engineering fork — the default, not optional. Also fires reactively when they're lost on the question, the explanation, or the stakes — including a 2nd consecutive check-question, which trips the repeated-confusion guard back to the Mental Model.
Family entry router for loom-discovery, the loom problem-space station. Use when unsure which discovery skill applies, or when a product idea's target users are still unclear (說不清是給誰用的 / not sure who this is for / 誰のためかまだ不明) — comes BEFORE product-principles. Routes worth-doing asks (值不值得做 / worth my time budget) to business-value, and user-needs asks (需求研究 / user research / ユーザーインサイト) to user-insights. Non-discovery asks redirect to their family entries. Members share no artifact and no agent.
Router for loom-interface-design — design a product's interface/interaction/UX in any modality (GUI/TUI/CLI). Routes to design-system (→ DESIGN.md) + interaction-flows (→ ui-flows.md). Use for 'design the UI/UX', screen flow, TUI/CLI layout.
The loom-product-principles family entry: intake + routing. Start here on a new product/feature idea when 不確定從哪開始 / 'where do I start' — checks the on-ramp criteria, then hands off to the member skill.