Shanc vs Claude + Skills
A skill tells Claude how to work. Shanc gives it something to work from.
You can write Claude a skill that explains your data — and re-explain it every time the schema moves. Shanc builds the layer once, keeps it current on its own, and validates every query before it runs. Same Claude, grounded instead of guessing.
Side by side
What's different
A layer, not a prompt
A skill is text you author — it knows only what you thought to write down, and it can't see how your data is really used. Shanc reads your schema, query logs and code directly, so the layer reflects what's in production, including the logic no one documented.
It doesn't go stale between prompts
A skill is a snapshot. The next schema change quietly makes it wrong, and Claude keeps following it confidently. Shanc updates on every commit, so the context Claude reasons over is today's, not the version someone wrote last quarter.
Something actually checks the query
A skill can tell Claude to write better SQL, but nothing enforces it — when the instructions are thin, Claude best-efforts and hallucinates. Shanc validates every query against the layer first, so a wrong join or a made-up column is caught, not returned as a number.
One source of truth, not one per laptop
Skills live with whoever built them. Ten analysts means ten private versions and no company-wide truth. Shanc is one layer everyone's agent draws from, so results are consistent no matter who's asking.