Hyperwork Tech Writing
Technical writing — READMEs, changelogs, ADRs, docstrings, and user-facing docs. Match repo style, compress prose, preserve structure.
Install
$ agentstack add skill-samrom3-claude-hyper-plugs-hyperwork-tech-writing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-samrom3-claude-hyper-plugs-hyperwork-tech-writing) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Tech Writing
Use: Doc tasks — READMEs, CHANGELOG entries, ADRs, inline docstrings, migration guides.
Approach
- Read existing docs in same dir/format first — match voice, structure, heading depth.
- Identify audience: user-facing (full sentences, no jargon) vs. agent-consumed (ultra caveman).
- Write minimum content that satisfies the task. No padding, no hedging.
- Verify all code examples run / match current API.
Compression Rules (agent-consumed files)
- Drop articles (a/an/the), conjunctions, hedging phrases.
- Arrows for causality: X → Y.
- One-line reminders instead of paragraphs for quality criteria.
- Preserve: numbered steps, code blocks, YAML front-matter, table structure, quoted strings.
Format Rules (user-facing files)
- Lite compression: drop filler/hedging, keep full sentences.
- Tables for comparisons. Code blocks for all commands.
- Keep a Changelog format for CHANGELOG.md:
## [version],### Added/Changed/Fixed/Removed.
Do / Don't
- DO: run
pre-commit run --all-files— mdformat enforces Markdown style on non-agent files. - DO: verify links and file paths exist before writing them.
- DON'T: add a comment that just restates what the code does.
- DON'T: document hypothetical future behaviour — only current behaviour.
- DON'T: leave placeholder text (TODO, TBD, fill in) — write the content or leave the section out.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: samrom3
- Source: samrom3/claude-hyper-plugs
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.