Prostir
Sign in
Get early access

Case 09

A technical documentation skill: make any AI write docs to your standard, then sell it

Ask AI to write docs and it comes back generic, off-voice, and missing the prerequisites — so you rewrite it every time. In this case you bottle your documentation standard as a Prostir skill: one SKILL.md with your rules (write for the reader's goal, the right doc type, your terminology, a review checklist), plus references and evals. Claude Code validates it and publishes it to a passport at tech-docs.skill.prostir.build. Anyone — or their AI — installs it and writes docs your way. Give it away to grow your name, or price it on your own Stripe and sell it many times.

01

Before: the AI's docs are generic, and your judgment is trapped

  • You ask AI to write the docs. They come back generic, off-voice, and missing the prerequisites — so you rewrite them anyway.
  • You re-explain the same rules every time: the reader, the structure, the terminology. A long prompt drifts; nothing sticks.
  • Your hard-won judgment lives in your head. You sell it by the hour, and it caps out right there.
02

What you do inside Claude Code (about 20 minutes)

You stay in your terminal. Prostir packages, validates, and publishes the skill.

  1. 01
    Add Prostir as an MCP server in Claude Code.

    One command: claude mcp add prostir https://prostir.ai.prostir.build/mcp. Sign in once.

  2. 02
    Create the skill and bring your standard in.

    Claude Code calls prostir_skills_create (slug tech-docs), then prostir_skills_import_files — paste your SKILL.md, pull it from a GitHub repo, or upload a folder. A ZIP is only transport; it's extracted, not stored.

  3. 03
    Write the rules that matter.

    In SKILL.md: write for the reader's goal, state prerequisites up front, pick the right doc type (tutorial / how-to / reference / explanation) and don't mix them, lock your terminology and voice, demand tested examples, add a review checklist. Drop in references/ and evals/.

  4. 04
    Validate.

    prostir_skills_validate checks one SKILL.md, valid frontmatter (name, description), that @file references resolve, script safety, and that evals pass. Fix anything blocking.

  5. 05
    Decide how it's shared and sold.

    Add a logo, choose access (open, key-gated, or OAuth) and price (free, or one-time / subscription on your own Stripe). Access and price are separate.

  6. 06
    Publish and share the passport.

    prostir_skills_publish cuts an immutable version, live at tech-docs.skill.prostir.build. Buyers (or their AI) download the package into .agents/skills/. Ship a 1.1 anytime.

03

What ends up inside the skill

One Agent Skills folder. Claude Code packages and validates it while you watch.

doc skills/tech-docs/SKILL.md The frontmatter (name, description) plus your rules: write for the reader's goal, state prerequisites, pick the right doc type.
doc references/style.md Your terminology, voice (you vs we), casing, and formatting — the standard the AI must follow.
doc references/review-checklist.md What a reviewer checks: prerequisites stated, examples tested, no assumed knowledge, one task per section.
data evals/evals.json Tests that prove the skill writes docs your way before you publish a new version.
04

What this actually looks like in Claude Code

Real prompt, real calls, real result.

Claude Code

Package my documentation style guide as a skill on Prostir, slug tech-docs. I want to sell it. Pull the SKILL.md and references from my GitHub repo.

prostir_skills_create

Creating the skill tech-docs (draft, owner-only). Reserving the slug.

prostir_skills_import_files

Importing from your GitHub repo: skills/tech-docs/SKILL.md plus references/ and evals/. Preview is clean — applying to the draft.

prostir_skills_validate

One SKILL.md, valid frontmatter (name, description), @file references resolve, evals pass. No blocking issues.

Price it $9 one-time on my Stripe, open passport, and use my lime icon.

prostir_skills_publish

Publishing version 1.0 — immutable archive. One-time $9 via your Stripe Connect, open access. Live at tech-docs.skill.prostir.build. ✓ Done.

Live. Share https://tech-docs.skill.prostir.build — buyers check out on your Stripe, download the package, and drop it into .agents/skills/. Ship a 1.1 anytime.

Passport

https://tech-docs.skill.prostir.build · Install into .agents/skills/tech-docs/

05

After: encode once, sell many times

  • Anyone you share it with adds the skill, and their AI writes docs to your standard — right doc type, stated prerequisites, your terminology — from the first draft.
  • It's versioned: fix a rule once, ship a 1.1, and every new install gets the better standard.
  • Give it away to grow your name, or price it on your own Stripe and sell the same skill many times instead of by the hour.

What gets published

A published Prostir skill at https://tech-docs.skill.prostir.build — one Agent Skills-compatible SKILL.md plus your references and evals, versioned and immutable. Set it open and free, key-gated, or priced one-time or by subscription on your own Stripe. Buyers (or their AI) download the package and drop it into .agents/skills/. Encode once, distribute or sell many times. No code.

Related cases

More case studies

Case 01

An AI that writes in your voice, not the chatbot's

 Case 02

Reddit, LinkedIn, X. Three voices in one agent.

 Case 03

A coach's playbook, running as a $29/mo AI agent

Ready to launch?

One afternoon from idea to live link.

Upload what only you have. Write the rules in plain language. Open the link in ChatGPT, Claude, or your site. Ship the agent only you could ship.

Get early access Talk to sales

Need custom scale, white-label, or dedicated setup? Talk to sales.