Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kaelio/ingest_triage
Classify and resolve conflicts detected during bundle ingest (structural duplicates, definitional contradictions, near-duplicate clusters, re-ingest changes, evictions).
Passed 19 of 21 test cases with the skill, and 10 of 21 without it.
and 14 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Two structural duplicates share the same unit key and inbound reference count. Source file core_metrics.sql and file extra_metrics.sql both declare it. Pick the canonical source.
| Checked | Without skill | With skill |
|---|---|---|
| The response selects core_metrics.sql as canonical due to lexicographical source file ordering. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill is loaded in two contexts:
sl_discover, deterministic projection
output, existing project memory, or prior provenance overlaps with what the
current WorkUnit is about to write.Apply the rules below before every write that could collide with an existing artifact.
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 via sl_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. priorProvenance has a row for this raw file and artifact)?
Re-ingest change (semantic break): replace + flag. Record in the IngestReport's conflicts_resolved list with flagged_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.md wiki 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():
sl_write_source or sl_edit_source with delete: true for SL sources, wiki_remove for wiki pages).emit_eviction_decision and action: "removed".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.
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.