wiki-ingest

When This Skill Activates

• User shares a URL, paste, or local file to capture in the vault.
• The output target is entities/, concepts/, comparisons/, or queries/.
• A vault is resolvable (see step 0).

Output language

Run skillwiki lang at the start. Generate page-body prose, narrative sections, and --human summaries in the resolved language. Frontmatter keys, file names, schema headers, index/log structural lines, citation markers, and wikilink slugs MUST stay English.

Pre-orientation reads (mandatory before any write)

1. SCHEMA.md
2. index.md
3. Last 20–30 entries of log.md
4. (Project context only) projects/{slug}/README.md and last ~5 work-item logs.

Steps (in order — deterministic raw capture and shared publication)

0. Resolve vault and language. Run skillwiki path (fail if NO_VAULT_CONFIGURED) and skillwiki lang. Use the resolved vault path for all writes; use the canonical language for all generated prose.
1. Guard. For each URL: run skillwiki fetch-guard <url>. If exit ≠ 0, STOP and surface the error. Do not retry.
2. Fetch. Use web_fetch (or read local file) under Layer 2 controls (the CLI Layer 2 fetcher applies in tests; in skill runtime use web_fetch directly and treat any error as STOP).
   • Portable local-source rule: follow using-skillwiki → Portable Source References. Do not use source_url: file:///... as the canonical durable reference; prefer commit-pinned GitHub blob/<commit>/<path> when resolvable, else empty source_url plus portable repo-relative prose.
3. Stage pasted text as a file source. skillwiki ingest accepts a readable local source file or HTTP(S) URL; it does not accept literal pasted text. For a paste, stage the exact text in a temporary file outside the vault, then pass its path to the normal command:

   skillwiki ingest <staged-paste-path> \