Skip to main content
In development. These skills describe what the code does today, which is less than the product will do. Every capability is Experimental until it earns evidence, so check maturity levels before you rely on what a skill tells you.
A skill is a Markdown file your coding agent loads when the task in front of it matches. It runs no code and holds no credentials. It changes what the agent knows before it starts writing. 86d publishes two of them in 86d-store/skills, listed on skills.sh. They exist because reading one Module is not enough to write a second one. An agent that has skimmed modules/products will produce something that compiles, registers, and breaks the storage contract in three places the compiler never sees. The skills carry those parts.

​
Install

Add -g to install for your user instead of the current project, and -y to skip the prompts. If your work stays inside a Store, 86d-store covers it. Add 86d-app when the work touches provisioning, Commands, or a Managed Deployment.

​
What 86d-store covers

Building on the Store Runtime: its Modules, Templates, Storefront, and Store Admin. The skill body carries the parts that apply to every change: how to tell a source checkout apart from a project that installs the packages, what a finished change includes, the gate order, and the import and typing rules the linter enforces. Three reference files carry one contract each, and the agent loads only the one it needs. The item worth naming on its own is the frozen registry check. apps/registry/registry.lock.json hashes every Module’s source subtree, postinstall verifies it, and a stale lock fails during install before a single test runs. Agents lose hours to this. The skill puts it first.

​
What 86d-app covers

Working against 86d.app, the managed plane. The body is the authority boundary: which plane owns which fact, the Command and Change Set model, the three levels of human involvement, and how to read a Workflow result without overstating it. This skill spends a section saying what does not exist. There is no public product-operation API, no Remote OAuth MCP endpoint, and no tool catalog. An agent that assumes one writes code that reads correctly and fails only against production, so the skill tells it to report the gap instead. See agent operations for the current position.

​
How the skills fit with the other tools

None of them can read or change a live Business, Store, Order, Payment, or deployment.

​
What a skill will not do for you

It does not hold credentials, and it should never be given any. It does not promote a capability. Maturity comes from maturityEvidence in apps/registry/registry.json, and a skill that described a Module as ready would be wrong the moment the registry disagreed. Both skills route the agent to the registry instead of caching an answer. It does not replace reading the code. Both skills say so, because a contract summary written three months ago and a test written yesterday disagree, and the test wins.

​
When a skill is wrong

Drift is the failure mode. A contract changes in 86d-store/86d, the skill still describes the old one, and an agent follows the skill into a change that fails review. Open an issue or a pull request on 86d-store/skills with the file that contradicts the skill. Corrections grounded in source land faster than corrections grounded in a design document.