The 22 skills · Craft skill · Core Pack and Everything
AGENT SKILL
anchor-discovery: what it makes your agent do, and what it refuses.
anchor-discovery is what your agent runs on a file it has never seen. It reads the bytes before it asks a question, mines the metadata above the header, and looks for the one thing that makes every later check possible: a total the file asserts about itself.
The job anchor-discovery does
The skill produces a source spec: what shape the file is, how to prove its identity, which numbers matter, what total it asserts about itself, and what a wrong version would look like. The anchor is the hard part and the whole point, because a spec that captures everything except the anchor builds a system that extracts numbers nobody can check. It works in a fixed order. Look before you ask, find the header row and treasure the pre header block above it, mine identity evidence from inside the bytes, then compute a candidate anchor and compare it before proposing it. The human confirms, and the confirmed proposal becomes a mechanical check that runs on every refresh after.
What anchor-discovery refuses
A skill is worth what it stops as much as what it produces. These are the refusals written into anchor-discovery, taken from the rules and limits in its own file.
- ✓Guessing at ambiguity. Two columns with one name, a date that could be day first or month first: each is a question for the operator, not a coin flip.
- ✓Proposing an anchor it did not test. The candidate total is computed and compared before it is ever offered.
- ✓Widening a tolerance to make a check pass. Tolerance describes floating point reality, not your confidence in the file.
- ✓Accepting a title as evidence. A cell that would read identically in every export from that system proves nothing about this one.
- ✓Staying quiet about gaps. Every unanchored value and every assumption goes in the summary, because a tidy spec hiding four unknowns is a liability.
8 lines from the anchor-discovery skill file, verbatim
From skills/anchor-discovery/SKILL.md, unedited. Kymira skills are plain text you can
read in full before you install them, which is the point of shipping a method rather than a binary.
**You propose. The human confirms. The engine enforces.** You never compute a number that reaches a page. You are reading a file to work out *what should be checked*, and every proposal you make becomes a mechanical check that runs forever after. Getting a check wrong is recoverable; authoring a figure is not. Read `DOCTRINE.md` (it ships beside these skills) before this skill. Everything here serves those eleven principles.
The failure modes anchor-discovery addresses
These entries in the catalogue of 51 observed failure modes name this skill as what addresses them. Every one was seen in a real build or in our own audits, and none was invented.
The tier anchor-discovery ships in
| Tier | Price | What the tier holds | anchor-discovery |
|---|---|---|---|
| Free | $0 | honest-dataviz and the eleven doctrine principles, published in full | Not in this tier |
| Core Pack | $199 | the thirteen craft skills, one-time purchase, lifetime updates | Included |
| Everything | $349 | all 22 skills, both libraries, the template bank, one-time purchase, lifetime updates | Included |
Both paid tiers are a one-time purchase with lifetime updates, and all sales are final: the files are plain text you keep the moment they arrive, so judge the quality on the free skill and the published doctrine first. The pricing section states exactly what each tier contains.
Installing anchor-discovery
A skill is a folder with a SKILL.md file in it. Installing one is copying that folder where
your agent looks for skills, with no build step and no dependencies.
mkdir -p ~/.claude/skills cp -R Kymira/skills/anchor-discovery ~/.claude/skills/
Or open the unzipped pack in Claude Code and say install Kymira, which installs every skill in your tier, or double-click the installer for your system. Cursor reads the same skill as a rule file: copy anchor-discovery.mdc into .cursor/rules/. Skills are read at startup, so start a new session and ask your agent which skills it has available.
Not for
It does not author numbers and does not build a report. It reads a file and proposes what should be checked, and it cannot tell you whether the source is the right source for the question you are asking. Naming the system of record stays a human ruling.
Last updated 2026-08-29 · Dylan, founder · one of 22 packaged skills, each one a method written down, not a product tour.