Technical Writing
SkillFiles & storageGuide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
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
What this skill tells your AI
The instructions your AI receives, as published by saffron-health/opencode-gui in .agents/skills/technical-writing/SKILL.md and read by ahel’s review.
Audience
Assume readers are at least as smart as you, so do not over-explain. State information once and move on.
Style
Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.
Formatting
- Do not use emojis.
- Do not use bold or italics.
- Use headings, lists, and code blocks only when they add clarity.
- Use fenced code blocks with language identifiers.
Paths
Always use relative file paths: docs/testing.md, not /Users/name/project/docs/testing.md.
Do Not Repeat
Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
Signals
- GitHub stars
- 58
- Forks
- 20
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
technical-writing-2- Source
- github.com/saffron-health/opencode-gui