Concise Technical Writing
Write, edit, and tighten clear concise technical communication. Use when Codex is asked for commit messages, PR descriptions, changelogs, README sections, design notes, implementation summaries, status updates, release notes, bug reports, comments, or to make text shorter, clearer, less verbose, less AI-sounding, or more direct.
Install
$ agentstack add skill-jeremylongworth-source-agentskills-concise-technical-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-jeremylongworth-source-agentskills-concise-technical-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
Concise Technical Writing
Core Workflow
- Identify audience, purpose, required facts, and action needed.
- Preserve technical accuracy; remove throat-clearing, filler, repetition, and vague praise.
- Lead with the change, decision, result, or ask.
- Use concrete nouns and verbs. Avoid inflated phrases.
- Keep structure proportional to the artifact: one-line commits, short PR summaries, scoped release notes, direct docs.
- Include risks, verification, and next steps only when useful.
Style Rules
- Prefer short sentences.
- Use active voice unless the actor is irrelevant.
- Replace abstract phrasing with specific behavior.
- Remove meta-commentary about why something is important.
- Avoid marketing language in engineering artifacts.
- Use bullets for scan-heavy details; use prose for short summaries.
Output Patterns
- Commit: imperative verb + object + qualifier.
- PR: summary, key changes, verification, risk.
- Changelog: user-visible change first.
- Status: done, blocked, next.
- Bug report: observed, expected, reproduction, impact, environment.
Deliverable Shape
For writing/editing work, provide:
- Final concise text first
- Optional brief rationale only when useful
- Preserved technical facts
- Removed ambiguity or verbosity called out only if requested
References
- Read
references/concise-writing-checklist.mdwhen editing technical text for clarity.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jeremylongworth-source
- Source: jeremylongworth-source/AgentSkills
- 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.