How do I install the Write Docs skill?

Run npx skillmds@latest add tomevault-io/write-docs-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write Docs?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write Docs by tomevault-io — Agent Skill

Name: Write Docs
Author: tomevault-io

Write Docs

Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Write Docs Skill

Create and maintain documentation for the Abacus docs site (Astro Starlight).

Before Starting

Read existing pages in docs/src/content/docs/ to understand patterns
Check docs/astro.config.mjs for sidebar structure
Understand the section you're adding to (getting-started, providers, cli, deployment, development)

Workflow

Adding a New Page

Create .mdx file in the appropriate directory
Add required frontmatter (see below)
Use existing pages as reference for component usage
Run cd docs && pnpm build to verify

Updating an Existing Page

Read the current page first
Make changes, preserving existing patterns
Run cd docs && pnpm build to verify

Frontmatter

Every page requires:

---
title: Page Title
description: One-line description for SEO
sidebar:
  order: 1  # Position within section
---

Key Rules

Links Must Include Base Path

Internal links need /abacus/ prefix (GitHub Pages requirement):

[Quick Start](/abacus/getting-started/quick-start/)  ✓
[Quick Start](/getting-started/quick-start/)          ✗

Import Components Before Use

import { Steps, Aside } from '@astrojs/starlight/components';

<Steps>
1. First step
2. Second step
</Steps>

<Aside type="tip">Helpful note</Aside>

Code Blocks Need Language Tags

```bash
pnpm cli sync


## Build Verification

**Always verify before committing:**

```bash
cd docs && pnpm build

Common errors:

Missing imports
Invalid frontmatter
Broken links (wrong path or missing /abacus/)

Style Guidelines

Imperative mood ("Run this" not "You should run")
Code examples over abstract descriptions
Keep paragraphs short - users skim
Tables for reference data (env vars, options)

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: write-docs-2description: Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly. Use when this capability is needed.---# Write Docs SkillCreate and maintain documentation for the Abacus docs site (Astro Starlight).## Before Starting1. Read existing pages in `docs/src/content/docs/` to understand patterns2. Check `docs/astro.config.mjs` for sidebar structure3. Understand the section you're adding to (getting-started, providers, cli, deployment, development)## Workflow### Adding a New Page1. Create `.mdx` file in the appropriate directory2. Add required frontmatter (see below)3. Use existing pages as reference for component usage4. Run `cd docs && pnpm build` to verify### Updating an Existing Page1. Read the current page first2. Make changes, preserving existing patterns3. Run `cd docs && pnpm build` to verify## FrontmatterEvery page requires:```mdx---title: Page Titledescription: One-line description for SEOsidebar: order: 1 # Position within section---```## Key Rules### Links Must Include Base PathInternal links need `/abacus/` prefix (GitHub Pages requirement):```mdx[Quick Start](/abacus/getting-started/quick-start/) ✓[Quick Start](/getting-started/quick-start/) ✗```### Import Components Before Use```mdximport { Steps, Aside } from '@astrojs/starlight/components';<Steps>1. First step2. Second step</Steps><Aside type="tip">Helpful note</Aside>```### Code Blocks Need Language Tags```mdx```bashpnpm cli sync``````## Build Verification**Always verify before committing:**```bashcd docs && pnpm build```Common errors:- Missing imports- Invalid frontmatter- Broken links (wrong path or missing `/abacus/`)## Style Guidelines- Imperative mood ("Run this" not "You should run")- Code examples over abstract descriptions- Keep paragraphs short - users skim- Tables for reference data (env vars, options)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/getsentry) — claim your Tome and manage your conversions.

Frequently asked questions