← Skills
THE IDEA
Teaches your AI to stand up a new Arkiv project the right way: start from the official template, wire Braga, keep the signing key safe, and write a first create + query — using the MCP and SDK.
The problem today
- Getting started needs a key, a .env, faucet GLM, and testnet wiring before your first write.
- A community `create-arkiv-app` exists but is unsafe — it puts the signing key in a browser-exposed `NEXT_PUBLIC_PRIVATE_KEY`. New devs copy that footgun.
- Shipping a new npm scaffolder is redundant when every dev's AI can scaffold from a skill + MCP + the official template.
What it would do
- Points the AI at the official starter template and how to adapt it to the dev's framework.
- The SAFE key pattern: browser apps use MetaMask via the SDK's custom() transport; servers keep the key server-side — NEVER NEXT_PUBLIC.
- Wires Braga + a runnable first create + query, and how to connect the Arkiv MCP.
WHY IT’S A BETTER EXPERIENCE
- No new npm package to maintain or keep in sync with the SDK.
- Works with whatever AI the dev uses, and adapts to their stack instead of a fixed scaffold.
- Safe-by-default — it actively steers away from the exposed-key footgun.
HOW IT COMPARES
Community create-arkiv-app (CLI)exists but ships NEXT_PUBLIC_PRIVATE_KEY — unsafe. A skill can teach the safe pattern instead.
npm create convex (a CLI)great for a no-AI world. With an AI + MCP + a template, a CLI is redundant.
FEASIBILITY — AND WHY THIS ISN’T HAND-WAVING
Easy to build
A knowledge skill that leans on the existing starter template + the MCP. No package to build.
Grounded in
- `starter-template-typescript` already exists in the Arkiv-Network org — the skill points to it.
- The unsafe community scaffolder is real (uses NEXT_PUBLIC_PRIVATE_KEY).
- The MCP gives any AI direct CRUD via the SDK — the scaffolding can happen through it.
PAIRS WITH