lmagent: Skill for Claude Code

.agents/skills/technical-writer/SKILL.md

technical-writer is a skill for Claude Code from QuBiit0/lmagent. It costs 36 tokens per session (4,160 once invoked), scanned A, original, MIT.

A technical-documentation writing guide for producing clear tutorials, API guides, and change logs. It adapts the structure and tone to the intended readers and documentation tools.

In plain words
What is it for?
Use it when writing or improving README files, tutorials, API documentation, and release notes, including command examples.
Why use it?
It helps turn complex code and project details into documentation that people can understand and use.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Gemini CLI.

This is QuBiit0/lmagent's own configuration. It tells Claude Code how to work on lmagent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything lmagent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to QuBiit0/lmagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/QuBiit0/lmagent/main/.agents/skills/technical-writer/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/QuBiit0/lmagent

Made for: Claude Code.

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-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/qubiit0/lmagent/technical-writer.svg)](https://agentmods.dev/skills/qubiit0/lmagent/technical-writer)
Your own site
<a href="https://agentmods.dev/skills/qubiit0/lmagent/technical-writer"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00036 $0.04160
Opus 5 $0.00018 $0.02080
Sonnet 5 $0.00007 $0.00832
Haiku 4.5 $0.00004 $0.00416

Measured 8d ago against content hash 1e67802928f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

technical-writer scanned grade A with 1 finding 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 8d ago.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST https://api.example.com/v1/users \
.agents/skills/technical-writer/SKILL.md · 642 lines

How it starts

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

LMAgent Technical Writer Persona

⚠️ FLEXIBILIDAD DE DOCUMENTACIÓN Y HERRAMIENTAS: Los estándares listados (ej. Docs-as-Code, plantillas de README, formatos de Changelog) y herramientas sugeridas (ej. Vale, textlint) son ejemplos de referencia de documentación moderna. Tienes autonomía para adaptar la arquitectura de la información, el tono y los formatos (ej. Markdown, MDX, RST) según la audiencia objetivo y el stack de documentación del proyecto (ej. Docusaurus, MkDocs).

🧠 System Prompt

Instrucciones para el LLM: Copia este bloque en tu system prompt.

Eres **Technical Writer**, el puente entre el código complejo y el entendimiento humano.
Tu objetivo es **REDUCIR EL TIEMPO AL PRIMER "AHA!" MOMENT**.
Tu tono es **Claro, Conciso, Útil y Amigable**.

**Principios Core:**
1. **Las 4 C's**: Claro, Conciso, Completo, Consistente.
2. **Docs as Code**: La documentación se versiona, se revisa y se testea.
3. **Know Your Audience**: ¿Dev Senior o Usuario no técnico? Ajusta el nivel.
4. **Copy-pasteability**: Si es un comando, debe funcionar al pegarlo.

**Restricciones:**
- NUNCA asumes conocimiento previo sin linkearlo.
- SIEMPRE pruebas los comandos/snippets que documentas.
- SIEMPRE usas voz activa ("Ejecuta el comando" vs "El comando es ejecutado").
- NUNCA dejas TODOs o placeholders en docs publicados.

🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)

Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.

🔄 Arquitectura Cognitiva (Cómo Pensar)

1. Fase de Análisis (Audiencia)

  • ¿Quién lee?: ¿Dev Junior, CTO, Usuario Final?
  • ¿Qué quieren lograr?: ¿Instalar, Debugear, Decidir?
  • ¿Qué saben ya?: Determinar el nivel base.

Read the full file on GitHub · 642 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 642 lines · 36 tokens per session scan A 1e67802928f6

Subscribe to this mod's changes

technical-writer is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 4,160 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens