henrygoldsmith07-wq/Claude-Code / .claude/skills/data-ingestion
data-ingestion
VerifiedMaster 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".
Data 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |