ingest_triage
Classify and resolve conflicts detected during bundle ingest (structural duplicates, definitional contradictions, near-duplicate clusters, re-ingest changes, evictions).
Install / Use
npx skills add Kaelio/ktx --skill ingest_triageInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of ingest_triage
ingest_triage scores 80/100 on our quality scale, 3655th of 4,706 Development & Engineering skills we index.
Its SKILL.md is 5.4 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.
With 1,601 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ingest_triage is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ingest_triage compared with similar skills
All 4 of these similar skills score higher than ingest_triage; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ingest_triage (this skill)by Kaelio | 80 | 1.6k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.0k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install ingest_triage?
- Run
npx skills add Kaelio/ktx --skill ingest_triage. The install tabs above show the steps for each supported agent. - Which AI agents does ingest_triage work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ingest_triage safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ingest_triage still maintained?
- The repository was last updated about 2 months ago, so ingest_triage is actively maintained.
Skill content
View source on GitHubname: ingest_triage description: Classify and resolve conflicts detected during bundle ingest (structural duplicates, definitional contradictions, near-duplicate clusters, re-ingest changes, evictions). callers: [memory_agent]
Ingest Triage - conflict classification and resolution
This skill is loaded in two contexts:
- By a Stage 3 WorkUnit agent when
sl_discover, deterministic projection output, existing project memory, or prior provenance overlaps with what the current WorkUnit is about to write. - By the Stage 4 reconciliation agent for cross-WorkUnit sweeps, accepted patch overlap, and eviction decisions.
Apply the rules below before every write that could collide with an existing artifact.
Decision tree
-
Is this the same artifact I'm producing now, or a different one with the same name? Read both. If names match and content matches (modulo whitespace): no conflict - skip the write, the prior one stands.
-
If content differs, is it an expression-only change (e.g. a different
sql:body for the same measure name, same grain, same columns)? Re-ingest change (expression-only): silently replace viasl_edit_source. No flag. -
If the difference is structural - grain, columns, filter, join shape - is the current bundle the re-ingest of a previously-ingested bundle (i.e.
priorProvenancehas a row for this raw file and artifact)? Re-ingest change (semantic break): replace + flag. Record in the IngestReport'sconflicts_resolvedlist withflagged_for_human: true. -
If reconciliation sees accepted patches from this same job with no prior-sync row, check for same-ingest contradictions:
| Kind | Detection | Resolution | |---|---|---| | Structural duplicate | Same name, near-identical expression | Elect canonical by: (a) highest inbound-ref count from other sources; tiebreak: (b) lexicographically first unit key; (c) lexicographically first source name. Subsume losers into
<canonical>-variants.mdwiki page. Do NOT flag unless ambiguous. | | Near-duplicate cluster | Different names, overlapping shape (same table, similar formulas) | Same as structural; one canonical, others subsumed. Flag only if no canonical emerges. | | Definitional contradiction | Same name, substantively different formulas (different aggregation, different filters, different columns) | Rename + capture: disambiguate ALL variants with suffix derived from the domain (churn_risk_engagement_based,churn_risk_billing_based) and write a unified wiki page listing every variant with provenance. The contested name does NOT land in the SL. Always flag. | -
Eviction (Stage 4 only): for each entry in
eviction_list():- Remove the artifact (
sl_write_sourceorsl_edit_sourcewithdelete: truefor SL sources,wiki_removefor wiki pages). - Record the removal with
emit_eviction_decisionandaction: "removed".
- Remove the artifact (
Why same-ingest vs re-ingest differs
Within ONE bundle there's no user signal telling us which duplicate wins - we capture all variants and flag. Across bundles, re-uploading IS the signal that the new state is intended - we replace silently for expression changes and flag for semantic breaks.
Naming disambiguation hints
When you rename to disambiguate, prefer domain suffixes that match the containing view/table/collection name: customers.churn_risk_score → customers.churn_risk_engagement_based (if the customer_churn view computes it from engagement); billing.churn_risk_score → billing.churn_risk_billing_based. Avoid numeric suffixes (churn_risk_1, churn_risk_2) - they disclose nothing.
Applying canonical pins
When the Stage 4 system prompt includes a <canonical_pins> block, treat each pin as a prior user decision for that contestedKey.
- If the pinned
canonicalArtifactKeyis present in the Stage Index or already exists in SL, keep it as the canonical artifact for that contested key. - Disambiguate competing artifacts instead of using the contested name for them.
- Do not flag the pinned contested key solely because the variants disagree; the user has already chosen the canonical artifact.
- If the pinned artifact cannot be found and no current WU can recreate it, emit
emit_conflict_resolutionwithflaggedForHuman: trueand explain that the pin references a missing canonical artifact.
When a pin applies cleanly, call emit_conflict_resolution with kind: "definitional_contradiction", artifactKey set to the pinned canonicalArtifactKey, detail describing the pinned election, and flaggedForHuman: false.
What to write in the unified wiki page
When you perform rename + capture, also write one page named <canonical-concept>-definitions.md under the wiki GLOBAL scope. Structure:
- One heading per variant, referencing the disambiguated SL name.
- One paragraph per variant: what it computes, where it came from (raw file + line range), when to use it.
- A closing "Choosing between these" paragraph if the variants are legitimately domain-specific.
Do not attempt to rank variants or pick a "best" - that's user-override territory.
Silence rules
Flag for human review when:
- You did rename + capture for a definitional contradiction (kind 3 above).
- You performed an eviction retention (kind 5, second row).
- An override constraint (from a Stage 4 re-run) conflicts with current inbound refs.
Do NOT flag:
- Same-content duplicate skip (trivial).
- Structural duplicate with clear canonical election.
- Expression-only re-ingest replace.
Related Skills
taste-skill
117.0kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
