zenstory SKILL.md skillA
zenstory from zenstory-ai/zenstory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zenstory-ai/zenstory/zenstory@v0.2.0Pins v0.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zenstory-ai/zenstory
- Path
apps/cli/skill/zenstory/SKILL.md- Versions recorded
- 5
- Latest version
- v0.2.0, committed Oct 15, 2026
- First version recorded
- Sep 27, 2026
- Size
- 9,910 bytes
- Repository stars
- 76
- License
- MIT
Reads, writes and organizes the user's novel projects stored in ZenStory (chapters/drafts, outlines, character profiles, lore/world-building, materials) through the ZenStory CLI and its Agent API. Use when the user mentions ZenStory, refers to their novel or story project kept in ZenStory, or asks to read, continue, draft, revise, or reorganize chapters, outlines, characters or settings stored there, or to check continuity across a ZenStory project (e.g. "continue chapter 12 in ZenStory…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# ZenStory
ZenStory is an AI-assisted novel writing workbench. Projects hold outlines, draft
chapters, characters, lore and materials as **files** in a folder tree. Use this skill
to read and update those files through the `zenstory` CLI and public Agent API.
## Running the CLI
Use `zenstory ...` if it is installed (`command -v zenstory`). Otherwise use
`npx -y zenstory ...` with exactly the same arguments. Examples below use `zenstory`.
Always add `--json` when you need to parse output. Errors go to stderr; the exit code tells
you what happened: `0` ok, `2` usage error, `3` auth/permission, `4` not found,
`5` rate limited, `1` anything else.
## Setup check (do this first, once per session)
```bash
zenstory whoami --json
```
- Exit `0`: note `scopes.read` / `scopes.write`. Without `write`, you can only read — tell
the user before planning edits.
- Exit `3` ("Not logged in" / key rejected): ask the user to create an Agent API key in
**ZenStory → Settings → Agent** (enable the `write` scope if they want you to edit), then
run this **themselves** in their own terminal and paste the key when prompted (input is
hidden, so the key stays out of shell history):
```bash
…Read the whole file at its exact version.
How to install
mdr add zenstory-ai/zenstory/zenstory@sha256:68e61b23870e1bbcThe line at the top of this page pins the label v0.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hyt6x7hjzylecorw)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 27, 2026 and Oct 15, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.2.0 latest | 2026-10-15 | 681fdaf | 9,910 B | A | view · diff |
| v0.2.0 | 2026-10-12 | 920065d | 9,819 B | A | view · diff |
| v0.2.0 | 2026-10-09 | 034f2eb | 9,846 B | A | view · diff |
| v0.2.0 | 2026-09-27 | c031d90 | 9,846 B | A | view · diff |
| v0.1.0 | 2026-09-27 | 0edebe2 | 7,911 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9910 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zenstory-ai/zenstory · 76 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hyt6x7hjzylecorw GET https://markdownregistry.com/api/v1/resolve?ref=zenstory-ai/zenstory/zenstory GET https://markdownregistry.com/api/v1/blob/68e61b23870e1bbc201440b695114a9c5103411c9341de5f719cbca063171657
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.