technical-documentation

technical-documentation is a skill for Claude Code, Codex from TrentM6/baseline-core. It costs 33 tokens per session (2,041 once invoked), scanned A, original, MIT.

A method for writing clear product documentation, including user guides, help articles, feature explanations, onboarding content, release notes, and knowledge bases.

In plain words
What is it for?
Use it to document how a product works, explain tasks with examples, support onboarding, and maintain help content.
Why use it?
It makes information easier to find and follow, while reducing confusion caused by inaccurate or outdated instructions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Follow the [Workflow Orchestration Pattern](../../frameworks/workflow-orchestration.md) for the universal workflow approach. Below are the documentation-specifi.

Good fit Use it to document how a product works, explain tasks with examples, support onboarding, and maintain help content.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/TrentM6/baseline-core
agentmods
npx agentmods add skills/trentm6/baseline-core/technical-documentation

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for technical-documentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/trentm6/baseline-core/technical-documentation/github.svg)](https://agentmods.dev/skills/trentm6/baseline-core/technical-documentation)
Your own site
<a href="https://agentmods.dev/skills/trentm6/baseline-core/technical-documentation"><img src="https://agentmods.dev/badge/skills/trentm6/baseline-core/technical-documentation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for technical-documentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/trentm6/baseline-core/technical-documentation"><img src="https://agentmods.dev/badge/skills/trentm6/baseline-core/technical-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,041 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.02041
Opus 5.5 $0.00013 $0.00816
Sonnet 5.5 $0.00007 $0.00408
Haiku 4.5 $0.00003 $0.00204

Measured yesterday against content hash 372cdac39591, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

technical-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/technical-documentation/technical-documentation-skill.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Technical Documentation

Product documentation helps users understand, use, and troubleshoot products. Good documentation is clear, accurate, findable, and maintained. It reduces support burden and improves user success.


Core Principles

  1. Write for the reader, not yourself. Documentation serves users. What do they need to know? What are they trying to do?

  2. Accuracy is non-negotiable. Wrong documentation is worse than no documentation. Verify everything.

  3. Show, don't just tell. Examples, screenshots, and code samples make abstract concepts concrete.

  4. Scannable first, readable second. Users scan for answers. Make structure obvious. They'll read when they find the right section.

  5. Maintenance is half the work. Outdated docs erode trust. Build in processes to keep docs current.

  6. Link, don't repeat. Single source of truth. Link to authoritative content rather than duplicating.

  7. Progressive disclosure. Start simple, go deep. Quick start first, advanced topics later.

Industry Principles

  1. Task-oriented structure. Organize around what users want to do, not how the product is built.

  2. Consistent terminology. Use the same words for the same things. Create a glossary if needed.

  3. Accessible language. Clear, simple language. Avoid jargon unless defining it.

  4. Visual hierarchy. Headers, lists, code blocks, callouts — structure helps navigation.

  5. Test with real users. Can they complete tasks using your docs? If not, revise.


Workflow

Follow the Workflow Orchestration Pattern for the universal workflow approach. Below are the documentation-specific details for each step.

1. Clarify Before Starting

Before writing documentation, understand:

  • Who is the audience? New user, power user, admin?
  • What's the purpose? Learn a concept, complete a task, troubleshoot?
  • What's the scope? Single feature, entire product, quick start?
  • What format? Tutorial, reference, how-to, explanation?
  • What exists already? Building on existing docs or starting fresh?
  • Who maintains it? What's the update process?

Read the full file on GitHub · 295 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 295 lines · 33 tokens per session scan A 372cdac39591

Subscribe to this mod's changes

technical-documentation is a skill published in the GitHub repository TrentM6/baseline-core (23 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 2,041 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-17.

Related

technical-documentation compared with skills from other repositories

technical-documentation next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
technical-documentationTrentM6/baseline-coreSkill232d agoMITA33Claude Code, Codex
orbit-notionnexu-io/open-designSkill108ktodayApache-2.0A117Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill37ktodayApache-2.0A123Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skillsSkill50ktodayMITA48Claude Code
report-to-pdfasgeirtj/system_prompts_leaksSkill72ktodayCC0-1.0A17Claude Code, Codex
legal-holdanthropics/claude-for-legalSkill10k2d agoApache-2.0A68Claude Code
artifact-template-minimal-letterheadasgeirtj/system_prompts_leaksSkill72ktodayCC0-1.0A54Claude Code, Codex