Enterprise DNAEnterprise DNA

Skills

Technical Writing (Agentic QE)

by proffesor-for-testing

Write technical posts, docs and tutorials from real experience: lead with value, show examples, cut hard, be honest about trade-offs.

Our verdict

Not reviewed yet

We have not reviewed Technical Writing (Agentic QE) yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About Technical Writing (Agentic QE)

A writing skill from the Agentic QE project. Its five rules are lead with what the reader will gain, show with specific examples, code and numbers, structure for scanning, cut every sentence that does not earn its place, and be honest about trade-offs. It includes a blog post structure and before and after examples.

Best for

Engineers who want to write about their own work clearly

Use cases

  • Write a blog post about a real engineering change
  • Tighten documentation so it is quick to scan
  • Write a tutorial grounded in an actual implementation

Notes

Why it matters

Engineers tend to write about their work in abstract terms. This skill's rules push towards the specific example, which is what readers remember.

Source

  • Skill file: .claude/skills/technical-writing/SKILL.md in proffesor-for-testing/agentic-qe.
  • Repository: 515 GitHub stars, MIT licence. Checked 24 Oct 2026 through the GitHub API.
  • Last change to the skill: 17 Mar 2026.
  • This page was written from the skill's own SKILL.md. It is not an Enterprise DNA source review and the skill has not been installed or tested by us.

Pros

  • Short and easy to apply
  • Before and after examples
  • Pushes for specifics over generalities

Cons

  • Lives inside a quality engineering project
  • Overlaps with other technical writing skills

Key facts

What we have checked

Days since the last commit
0
Checked GitHub
GitHub forks
105
Checked GitHub
GitHub stars
529
Checked GitHub
Open issues
128
Checked GitHub
Releases in the last 90 days
31
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How Technical Writing (Agentic QE) is growing

GitHub stars

520 to 529

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is Technical Writing (Agentic QE) looked after, and what do its setup files show

Health score

75 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 0 days ago
Releases15 of 1531 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 main@13469743237b. What it checks

  • Note No dependency list or install command was found in the skill, so there were no packages to look up on OSV.

Alternatives

Alternatives to Technical Writing (Agentic QE)

RecordTypeHow we knowChecked
technical-writingThis is an alternative to itSkillMatched from the listing text

Compare

Compare Technical Writing (Agentic QE) side by side

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.