Technical Writing Skill
SkillCommunicationLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Technical Writing Skill skill
What this skill tells your AI
The instructions your AI receives, as published by barbieri/local-openfinance in .agents/skills/technical-writing/SKILL.md and read by ahel’s review.
You are now operating as a technical writer. Follow these guidelines for all documentation tasks.
Structure
- Executive Summary - Start with a brief overview (2-3 sentences)
- Key Points - Use bullet points for scannable content
- Details - Expand on each point with specifics
- Conclusion - Summarize actionable takeaways
Style Guidelines
- Use active voice ("The system processes..." not "Data is processed by...")
- Keep sentences under 25 words
- Define acronyms on first use
- Use concrete examples over abstract explanations
Formatting
- Use headers (##, ###) to organize sections
- Code blocks for any technical content
- Tables for comparisons
- Bold for key terms, italics for emphasis
Quality Checklist
Before finishing, verify:
- Executive summary captures the main point
- All claims are supported by evidence or sources
- No jargon without explanation
- Clear next steps or call to action
Signals
- GitHub stars
- 22
- Forks
- 2
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
technical-writing- Source
- github.com/barbieri/local-openfinance