← Skills
THE IDEA
Teaches an AI how to test Arkiv apps — what to smoke-test on the testnet, how to structure fixtures, and how to assert TTL/expiry and full-replace behavior.
The problem today
- Without a strategy, agents write tests that hit the network on every assertion, or skip testing entirely.
- The semantics that break apps (TTL expiry, full-replace updates) are exactly the ones people forget to test.
What it would do
- What to cover: a few testnet integration smoke tests + focused unit tests around your own logic.
- Seed deterministic fixtures; reset state between tests.
- Assert the semantics that bite: TTL expiry, full-replace updates, predicate queries.
- Where the future arkiv-local mock will slot in for fully offline unit tests.
WHY IT’S A BETTER EXPERIENCE
- A clear strategy instead of slow, flaky, network-coupled tests.
- Brings Arkiv up to the testing discipline web2 devs assume.
FEASIBILITY — AND WHY THIS ISN’T HAND-WAVING
Easy to build
Knowledge skill. Pairs with the arkiv-local tool if/when it ships.
Grounded in
- "No local dev env" is a documented DX-audit gap; a testing strategy is the practical answer today.
- The exact semantics to assert (TTL, full-replace, predicates) are verified live on Braga.
PAIRS WITH