skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
proffesor-for-testing/agentic-qe93 installs

qe-technical-writing

Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.

How do I install this agent skill?

npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill qe-technical-writing
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides technical writing guidelines and includes examples for document generation tasks that process external source code and files, which represents a surface for indirect prompt injection.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

Technical Writing

<default_to_action> When writing technical content:

  1. LEAD with value (what will reader learn/gain?)
  2. SHOW, don't tell (specific examples, code, and numbers you measured or can source)
  3. STRUCTURE for scanning (headers, bold, short paragraphs)
  4. CUT ruthlessly (every sentence must earn its place)
  5. 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 take

Before/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

PrincipleBadGood
Lead with value"In today's landscape...""Here's what changed when we moved testing into refinement"
Show, don't tell"We improved testing""Bugs found per sprint, before and after, from our tracker: [before]→[after]"
Be specific"Performance improved""p95 response time before and after, with how and where it was measured"
Honest trade-offs"This approach is best""TDD slowed our first features; here is what we got back, with the numbers we measured"
Source every figure"Coverage jumped 40%" (from memory)The figure plus where it came from, or no figure at all

Bracketed values are placeholders for your own measured data. Never fill them with plausible-sounding numbers.

Words to Cut

KillReason
basically, actually, probablyHedge words
leverage, synergy, paradigmCorporate speak
very, really, quiteUnnecessary qualifiers
it should be noted thatJust 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

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 now surface during refinement instead of after merge, the regression suite stopped growing with every release, and developers ask QE for input during design." (Add figures only if you measured them, and say where they came from.)


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 templates

Fleet 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


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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/proffesor-for-testing/agentic-qe/qe-technical-writing">View qe-technical-writing on skillZs</a>