data-ingestion
Master orchestration for the knowledge-base pipelines — runs the three syncs, then reconciles the wiki index. Use for the scheduled routine or "ingest data" / "run the pipelines".
SKILL.md.claude/skills/data-ingestion/SKILL.md
GitHubData Ingestion (Master Orchestration)
Run all knowledge-base sync pipelines in succession. This is the command the Data Ingestion routine fires (Tuesday and Friday mornings) — it must run end-to-end without asking questions.
Process
- Sync sessions. Follow
.claude/skills/sync-claude-sessions/SKILL.md. - Sync ecosystem data. Follow
.claude/skills/sync-ecosystem-data/SKILL.md. - Sync curated content. Follow
.claude/skills/sync-curated-content/SKILL.md. - Reconcile the wiki. After all three:
- Verify every file written this run has a row in
wiki/index.md; add any missing rows. - If 3+ indexed entries now share a theme without a topic page, create
wiki/<topic>.mdand register it in the Topic Pages table.
- Verify every file written this run has a row in
Failure handling
A failing pipeline (missing connector, empty source, tool error) must not stop the run: note the failure, continue with the next pipeline, and include it in the report.
Report
End with a single consolidated summary:
## Data Ingestion — YYYY-MM-DD
- Sessions: <n digested | skipped: reason>
- Ecosystem: <sources synced | skipped: reason>
- Curated: <claims extracted | skipped: reason>
- Wiki: <rows added, topic pages created/updated>
When run by a scheduled routine, commit and push to knowledge-base-updates
as the routine prompt instructs — an ephemeral container discards uncommitted
work. Otherwise do not commit unless the user asks.