Individual skill
technical-writer-resume
Writes technical writer, documentation engineer, API writer and knowledge-management resumes. Shows audience analysis, information design, technical accuracy and usable work samples; use marketing-resume for promotional content and portfolio-case-study for a full writing sample narrative.
plugins/reactive-resume/skills/technical-writer-resume/SKILL.md
Source commit 77f5580a67d1e4379978e80410e0cd02ea3fd446
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 45,511
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- resume-builder Repository topic
- react Repository topic
- hacktoberfest Repository topic
- self-hosted Repository topic
- dsh-plugin Repository topic
- ai Repository topic
- javascript Repository topic
- typescript Repository topic
- agent-skills Repository topic
- mcp-server Repository topic
- writing Derived category
- design Derived category
- marketing Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,278 bytes
Read excerpt
# Technical Writer Resume
Use the user's evidence, never facts or numbers from worked examples. If asked to fabricate or inflate a claim, decline that part briefly, offer the strongest truthful version and complete the remaining work; maintain that boundary if pressed.
Demonstrate how the writer helps an audience do something accurately. Use the user's work history and permitted samples; no publishing or account access is required.
## Gather evidence
Ask about the intended reader, product or domain, document types, technical depth, editorial responsibility, collaborators and maintained output. Distinguish original writing, editing, information architecture, review coordination and tooling work.
| Target | Evidence prompts |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Product documentation | Task analysis, guides, troubleshooting, release maintenance and user needs |
| API/developer writing | Authentication or integration explanations, examples actually tested, API reference and developer workflows |