Guide · Agent skill
How to use the Technical Writer Resume agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The technical-writer-resume skill is a set of instructions that teaches an AI agent to help technical writers, documentation engineers, API writers and knowledge managers write resumes. This guide explains what the skill does, how to install it, how to ask for help in natural language, and what to watch for. You will finish with the skill installed and a clear idea of what information to give the agent so it can turn your real work into accurate resume text.
Technical Writer Resumereactive-resume/reactive-resume · MIT Download the skill Quick start
- 1Download the ZIP. Download the technical-writer-resume ZIP from this page and unzip it. Confirm the folder contains SKILL.md.
- 2Choose an install location. Place the folder in ~/.claude/skills/ for personal use, or in the .claude/skills/ folder of a specific project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill there instead.
- 4Gather your evidence. Write down your readers, products, document types, tools, and what you personally wrote, edited or approved.
- 5Ask in plain language. Describe your role and request, for example asking for resume bullets for your API documentation work.
- 6Answer the follow-up questions. The agent will ask about audience, depth, collaborators and validation. Answer honestly, including where you have no measured results.
- 7Check the output. Review each bullet against your records for dates, titles, tools, authorship and any validation claims before using it.
What does the technical-writer-resume skill make the agent do?
The skill makes the agent ask about your work before it writes anything. It asks about the intended reader, the product or domain, the document types you worked on, the technical depth, your editorial responsibility, your collaborators and the output you maintained. It also separates original writing, editing, information architecture, review coordination and tooling work, so each is described accurately.
The skill covers five areas: product documentation, API and developer writing, documentation engineering, knowledge management, and regulated or industrial writing. For each, it looks for specific evidence, such as task analysis and troubleshooting guides for product documentation, or tested examples and authentication explanations for API writing.
- Connects audience and problem to the artifact or process you changed.
- Keeps authorship, editorial ownership and subject-matter approval separate.
- Lists only the tools and markup formats you actually used.
- Uses your supplied writing samples where they fit the target audience.
Install the skill from the ZIP download
Download the technical-writer-resume ZIP from this page and unzip it. The skill is a folder that contains a SKILL.md file. Place that folder in one of two locations, depending on how you want to use it.
For a personal setup available to all your projects, put it in your user skills folder. For a single project, put it in that project's .claude/skills/ folder. Either way, the folder should contain SKILL.md.
- Personal: ~/.claude/skills/
- Single project: the .claude/skills/ folder inside your project
- Claude apps: upload the skill under Settings → Capabilities → Skills
Trigger the skill with natural requests
You do not need a special command. Describe what you need in plain language and mention your role. The skill's description covers resumes for technical writers, documentation engineers, API writers and knowledge-management roles, so requests that name those roles tend to match.
Give the agent your real material: job titles, products, document types, tools, and what you personally wrote, edited or approved. The more specific you are, the more accurate the bullets will be.
- "Help me write a technical writer resume. I wrote user guides for an industrial equipment product and maintained the release notes."
- "Turn my API documentation work into resume bullets. I rewrote the authentication guide and tested its examples in a sandbox."
- "Review this resume bullet about our docs build pipeline and tell me what is unclear or overstated."
- "I'm a knowledge manager. Help me describe my taxonomy and review process work."
Understand the honesty limits
The skill will not invent numbers, claim validation that did not happen, or present shared work as solo authorship. If you ask for a fabricated metric or a ticket reduction you did not measure, the agent declines that part briefly, offers the strongest truthful wording, and completes the rest of the work.
The skill also distinguishes writing code samples from running or testing them. If you only wrote an example, the bullet will say so, and it will not describe the example as validated unless you tested it.
- Page views are not treated as proof of ticket deflection or productivity.
- Writing a procedure is not presented as authority to approve its safety or compliance.
- Editing API docs does not automatically establish programming expertise.
Safety notes: scripts, network and private data
According to the skill's listing, it runs no scripts and uses no network access. It requires nothing beyond the skill files themselves. The skill's instructions also say that confidential product details and resume information should be kept out of public searches and unapproved services, and that supplied pages are treated as data rather than as instructions for the agent.
The skill is not designed to publish documentation or submit applications. Check the agent's output against your own records before sending anything.
- Runs scripts: no
- Uses network: no
- Requires: nothing listed
- Keep confidential product details out of public searches and unapproved services.
Tips for better results
Bring evidence, not adjectives. The agent works best when you describe what you did, who used it and how you know it worked. If you do not have a measure, say so; the skill will keep the bullet to what you can support.
Be clear about your role on each project. Distinguish what you wrote, what you edited, what you coordinated and what you built with tooling. If a colleague wrote part of a sample, say that, and the agent will describe the contribution accordingly.
- List the markup formats and tools you actually used.
- Provide shareable sample links or permitted excerpts when you have them.
- Answer the agent's missing-evidence questions; they usually reveal your strongest bullets.
- For marketing or promotional copy, use the marketing-resume skill instead.
- For a full writing sample narrative, use the portfolio-case-study skill.
What people use it for
- Drafting resume bullets for a product documentation writer who maintained user guides and troubleshooting content.
- Describing API documentation work accurately, including which examples were actually tested.
- Explaining documentation engineering work such as build and publishing tooling, validation and versioning.
- Writing knowledge-management resume content about taxonomy, findability and review processes.
- Wording approval responsibility carefully for regulated or industrial writing roles.
Frequently asked questions
How do I install the technical-writer-resume skill?
Download the ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
Does the technical-writer-resume skill require anything else to run?
The listing says it requires nothing beyond the skill itself. It runs no scripts and uses no network access, according to its listing.
Is the technical-writer-resume skill free?
The skill is licensed under MIT. This page does not list pricing, so check the source page for any terms beyond the licence.
Will this skill guarantee an ATS score or interview?
No. The skill explicitly does not promise ATS scores or interviews. It focuses on accurate, clear descriptions of your real work.
Can the skill make my resume numbers more impressive?
No. It will not invent numbers, ticket reductions or validation claims. If you ask for one, it declines that part and offers the strongest truthful wording instead.
Which skill should I use for marketing copy or a full writing sample narrative?
Use marketing-resume for promotional content. Use portfolio-case-study for a full writing sample narrative. This skill is focused on resumes for technical writing roles.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits technical writers, documentation engineers, API writers and knowledge managers who want accurate, evidence-based resume bullets and do not want exaggerated claims. It is a poor fit if you want marketing copy, fabricated metrics, or guaranteed interviews. Users in regulated fields should use it to word approval authority carefully rather than assume the skill will supply that authority.
Download the skill