live_database_ingest
Capture semantic-layer and knowledge updates from a live database schema snapshot.
npx skills add Kaelio/ktx --skill live_database_ingest --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Live Database Ingest Use this skill when the ingest work unit contains raw files under `raw-sources/<connectionId>/live-database/<syncId>/`. ## Workflow 1. Read the table JSON file listed in the work unit. 2. Read `connection.json` to understand the snapshot metadata. 3. Read `foreign-keys.json` when the table has a foreign key or when joins are needed for the semantic-layer source. 4. Create or update one semantic-layer source for the table with `sl_write_source`. 5. Use the physical table name from the raw JSON as the source `table` field. 6. Preserve database comments as `descriptions.db` on tables and columns. 7. Add joins only when the foreign key index names both sides. 8. Write wiki pages only for durable business meaning that is present in table or column comments. 9. Run `sl_validate` for the table source before the work unit completes. Sample values come from the scan record; do not invent values not present in relationship-profile.json. ## Identifier Verification Protocol Before writing a wiki page or SL source on any topic: 1. `discover_data({query: "<topic>"})` - see what wikis, SL sources, and raw tables already exist. Prefer updating existing pages over creating ne
- Workflow
- Identifier Verification Protocol
- Source shape
- Boundaries
What does the live_database_ingest skill do?
Capture semantic-layer and knowledge updates from a live database schema snapshot.
How do I install it?
Run `npx skills add Kaelio/ktx --skill live_database_ingest --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Kaelio/ktx, a repository with 1,526 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.