Rnd Technical Writer
chendongqi/OPB-Skills
Technical article writing assistant. An agent skill from chendongqi/OPB-Skills.
Write clear, engaging technical content from real experience.
Install Technical Writing
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install proffesor-for-testing/agentic-qe technical-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/technical-writing .claude/skills/technical-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .claude/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install proffesor-for-testing/agentic-qe technical-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/skills/technical-writing .agents/skills/technical-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .agents/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install proffesor-for-testing/agentic-qe technical-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/skills/technical-writing .cursor/skills/technical-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .cursor/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/proffesor-for-testing/agentic-qe.git --path assets/skills/technical-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install proffesor-for-testing/agentic-qe technical-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/skills/technical-writing .gemini/skills/technical-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .gemini/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install proffesor-for-testing/agentic-qe technical-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/skills/technical-writing .github/skills/technical-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .github/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install proffesor-for-testing/agentic-qe technical-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/skills/technical-writing .opencode/skills/technical-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-writing" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/technical-writing into .opencode/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
technical-writing- GitHub stars
- 494
- Token cost
- ~1.2k tokens
- SKILL.md length
- 385 words
- Files
- 2
- Skills in repo
- 95
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write clear, engaging technical content from real experience.
- Works in 5 steps: LEAD with value (what will reader… → SHOW, don't tell (specific examples,… → STRUCTURE for scanning (headers, bold,… → …
- Writing blog posts
- SKILL.md covers Quick Reference Card, Audience-Specific Writing, Editing Checklist and Example Transformations, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Technical Writing is an agent skill from proffesor-for-testing/agentic-qe. Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `schemas/output.json`).
It sits in Writing & Content, covering Technical writing and Blog and article writing. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.
When your agent uses it
- Writing blog posts
- Technical articles
Example prompts
- “/technical-writing”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- LEAD with value (what will reader learn/gain?)
- SHOW, don't tell (specific examples, code, numbers)
- STRUCTURE for scanning (headers, bold, short paragraphs)
- CUT ruthlessly (every sentence must earn its place)
- BE honest about trade-offs
What it can do on your machine
Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Technical Writing loads about 1.2k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 385 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 385 words, ~1,221 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-writing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- technical-writing
- description
- Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
- category
- communication
- priority
- medium
- tokenEstimate
- 800
- agents
- qe-quality-analyzer, qe-api-contract-validator
- implementation_status
- optimized
- optimization_version
- 1
- last_optimized
- 2025-12-03
- quick_reference_card
- true
- tags
- writing, documentation, communication, blogs, tutorials
- trust_tier
- 1
Technical Writing
<default_to_action> When writing technical content:
- LEAD with value (what will reader learn/gain?)
- SHOW, don't tell (specific examples, code, numbers)
- STRUCTURE for scanning (headers, bold, short paragraphs)
- CUT ruthlessly (every sentence must earn its place)
- BE honest about trade-offs
Blog Post Structure:
# Title (specific promise)
## Opening (2-3 paragraphs)
- Hook: The problem or insight
- Context: Why this matters
- Promise: What they'll learn
## Body (3-5 sections)
- One clear idea per section
- Support with examples/code/data
## Closing
- Key takeaway (1-2 sentences)
- Action reader can takeBefore/After: ❌ "We implemented a comprehensive testing strategy..." ✅ "We moved exploratory testing into sprint planning. QE now pairs with devs during story refinement." </default_to_action>
Quick Reference Card
Core Principles
| Principle | Bad | Good |
|---|---|---|
| Lead with value | "In today's landscape..." | "Here's how we cut bugs 60%" |
| Show, don't tell | "We improved testing" | "Bug detection: 12→47 per sprint" |
| Be specific | "Performance improved" | "Response time: 2.3s→180ms" |
| Honest trade-offs | "This approach is best" | "TDD slowed velocity 20%, reduced bugs 75%" |
Words to Cut
| Kill | Reason |
|---|---|
| basically, actually, probably | Hedge words |
| leverage, synergy, paradigm | Corporate speak |
| very, really, quite | Unnecessary qualifiers |
| it should be noted that | Just note it |
Audience-Specific Writing
For Developers
- Lead with code or concrete problem
- Show implementation details
- Discuss trade-offs and alternatives
- Link to repos or examples
For QA/QE
- Start with testing challenge
- Show strategy, not just tools
- Include risk assessment
- Provide adaptable heuristics
For Leadership
- Open with business impact
- Use metrics that matter
- Connect technical to outcomes
- Keep technical details concise
Editing Checklist
Before publishing:
- Title promises something specific
- Opening hooks in 30 seconds
- Claims backed by examples
- All unnecessary words cut
- Code examples tested and correct
- Takeaway crystal clear
- Would send to respected colleague
Show full SKILL.md (144 more words)Show less
Example Transformations
Before: "We decided to implement a more comprehensive testing strategy that would allow us to catch bugs earlier in the development lifecycle."
After: "We moved exploratory testing into sprint planning. QE now pairs with devs during story refinement, identifying risks before code is written."
Before: "The benefits of this approach are numerous and include improved quality, faster feedback loops, and better team collaboration."
After: "Three outcomes: bugs found 2 days earlier on average, 30% fewer regression issues, and devs now ask QE for input during design."
Agent Integration
// Generate documentation from code
const docs = await Task("Generate Docs", {
source: 'src/services/PaymentService.ts',
format: 'markdown',
includeExamples: true
}, "qe-quality-analyzer");
// Review documentation quality
const review = await Task("Review Docs", {
files: ['README.md', 'docs/api.md'],
checkClarity: true,
checkCodeExamples: true
}, "qe-quality-analyzer");Agent Coordination Hints
Memory Namespace
aqe/technical-writing/
├── generated-docs/* - Auto-generated documentation
├── reviews/* - Documentation review findings
└── templates/* - Reusable doc templatesFleet Coordination
const docsFleet = await FleetManager.coordinate({
strategy: 'documentation',
agents: [
'qe-quality-analyzer', // Generate and review
'qe-api-contract-validator' // API doc accuracy
],
topology: 'sequential'
});Related Skills
- bug-reporting-excellence - Technical bug writing
- code-review-quality - Review documentation
Remember
You're not writing to impress. You're writing to help people solve problems you've already solved. Be the colleague you wish you'd had.
Write from experience. Only write about what you've done in production. If exploring, say so.
© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in assets/skills/technical-writing of proffesor-for-testing/agentic-qe.
- SKILL.md
- schemas/output.json
Open the folder on GitHubat commit 829d030
Compare with similar skills
Technical Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Writing this skillproffesor-for-testing/agentic-qe | 494 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Rnd Technical Writerchendongqi/OPB-Skills | 125 | — | ~2.5k | Automated safety check: Pass | None | |
| Dynamo Content DesignerDynamoDS/Dynamo | 2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Voicejvm-skills/jvm-skills | 140 | — | ~592 | Automated safety check: Pass | Apache-2.0 | |
| Domodomo Release Documentationdarknecrocities/DomoDomo---All-in-one-Tool | 239 | — | ~17k | Automated safety check: Pass | None | |
| Reading Levelthedaviddias/Front-End-Checklist | 74k | — | ~613 | Automated safety check: Pass | MIT |
Similar skills
Dynamo Content Designer
DynamoDS/Dynamo
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
Voice
jvm-skills/jvm-skills
Make prose sound like Thomas, not like a generic technical writer.
Domodomo Release Documentation
darknecrocities/DomoDomo---All-in-one-Tool
Maintain DomoDomo product documentation, technical tool records, About metrics, blog posts, SEO metadata, sitemap generation, release communication, and contributor guidance.
Reading Level
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing content pages for user experience and SEO.
How To Tutorial Writer
Affitor/affiliate-skills
Write how-to guides and tutorials that naturally integrate affiliate product recommendations.
More from proffesor-for-testing/agentic-qe
All 95 skills in this repoContract Testing
proffesor-for-testing/agentic-qe
Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.
Mutation Testing
proffesor-for-testing/agentic-qe
Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.
Performance Testing
proffesor-for-testing/agentic-qe
Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.
Code Review Quality
proffesor-for-testing/agentic-qe
Conduct context-driven code reviews focusing on quality, testability, and maintainability.
Security Testing
proffesor-for-testing/agentic-qe
Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.
Database Testing
proffesor-for-testing/agentic-qe
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.
Related
Categories
Questions about Technical Writing
What does Technical Writing do?
Write clear, engaging technical content from real experience. Technical Writing is an agent skill from proffesor-for-testing/agentic-qe. Write clear, engaging technical content from real experience.
When should I use Technical Writing?
Technical Writing fits situations like: writing blog posts; technical articles.
How do I install Technical Writing in Claude Code?
Run `npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a claude-code`. Or copy the skill folder (assets/skills/technical-writing in proffesor-for-testing/agentic-qe) into .claude/skills/technical-writing in your project. Claude Code loads it when a task matches its description.
How do I install Technical Writing in Codex?
Run `npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a codex`. Or copy the skill folder (assets/skills/technical-writing in proffesor-for-testing/agentic-qe) into .agents/skills/technical-writing in your project. Codex loads it when a task matches its description.
Can I use Technical Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill technical-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-writing, .gemini/skills/technical-writing, .github/skills/technical-writing and .opencode/skills/technical-writing in your project.
What does Technical Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Writing is instructions for the agent only.
Does Technical Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Technical Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Technical Writing use?
Technical Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Technical Writing use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Technical Writing?
Skills that share tags, products or a category with Technical Writing: Rnd Technical Writer (chendongqi/OPB-Skills, 125 stars), Dynamo Content Designer (DynamoDS/Dynamo, 2k stars), Voice (jvm-skills/jvm-skills, 140 stars) and Domodomo Release Documentation (darknecrocities/DomoDomo---All-in-one-Tool, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Writing?
proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on October 4, 2026.
Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.