Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
A skill your agent uses when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns…
Install Writing For A Technical Audience
$ npx skills add ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ed3dai/ed3d-plugins writing-for-a-technical-audience --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/ed3dai/ed3d-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .claude/skills/writing-for-a-technical-audience && 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 "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .claude/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audienceType 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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ed3dai/ed3d-plugins writing-for-a-technical-audience --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .agents/skills/writing-for-a-technical-audience && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .agents/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ed3dai/ed3d-plugins writing-for-a-technical-audience --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .cursor/skills/writing-for-a-technical-audience && 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 "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .cursor/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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/ed3dai/ed3d-plugins.git --path plugins/ed3d-house-style/skills/writing-for-a-technical-audience--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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ed3dai/ed3d-plugins writing-for-a-technical-audience --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .gemini/skills/writing-for-a-technical-audience && 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 "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .gemini/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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 ed3dai/ed3d-plugins writing-for-a-technical-audienceInstalls 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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .github/skills/writing-for-a-technical-audience && 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 "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .github/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ed3dai/ed3d-plugins writing-for-a-technical-audience --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ed3d-house-style/skills/writing-for-a-technical-audience .opencode/skills/writing-for-a-technical-audience && 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 "writing-for-a-technical-audience" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-house-style/skills/writing-for-a-technical-audience into .opencode/skills/writing-for-a-technical-audience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-for-a-technical-audience", 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
writing-for-a-technical-audience- GitHub stars
- 250
- Token cost
- ~3.9k tokens
- SKILL.md length
- 1,763 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns…
- Works in 6 steps: Clarity → Conciseness → Consistency → …
- Writing documentation
- SKILL.md covers Overview, When to Use, The Three Pillars and Avoid AI Writing Patterns, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing For A Technical Audience is an agent skill from ed3dai/ed3d-plugins. Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: Ed's repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If you're lucky.
When your agent uses it
- Writing documentation
- Technical content for developers - enforces clarity
- Authenticity while avoiding AI writing patterns that signal inauthenticity
Example prompts
- “/writing-for-a-technical-audience”
Requirements
- Python 3
- Node.js
- A credential in YOUR_API_KEY
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Clarity
- Conciseness
- Consistency
- Assumes Too Much
- Perfect World Examples
- Vague and Unhelpful
What it can do on your machine
Read from SKILL.md and the folder at commit 0c90f4b. 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 python, markdown, javascript and typescript).
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
Writing For A Technical Audience loads about 3.9k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,763 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,763 words (~3,862 tokens).
“Core principle: Technical writing must be clear, concise, and authentic. Clarity and technical depth are not opposites - you can have both. Avoid AI writing patterns that make content feel robotic or inauthentic.  Why this matters: Developers value their…”
- name
- writing-for-a-technical-audience
- user-invocable
- false
Files
Just SKILL.md in plugins/ed3d-house-style/skills/writing-for-a-technical-audience of ed3dai/ed3d-plugins.
Open the folder on GitHubat commit 0c90f4b
Compare with similar skills
Writing For A Technical Audience 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 |
|---|---|---|---|---|---|---|
| Writing For A Technical Audience this skilled3dai/ed3d-plugins | 250 | — | ~3.9k | Automated safety check: Pass | None | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 173 | 38 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT | |
| Stop SlopXe/site | 732 | 8 repos | ~423 | Automated safety check: Pass | MIT |
Similar skills
- Official
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Stop Slop
Xe/site
Remove AI writing patterns from prose. An agent skill from Xe/site.
Chinese Text Humanizer
op7418/Humanizer-zh
Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.
More from ed3dai/ed3d-plugins
All 34 skills in this repoSystematic Debugging
ed3dai/ed3d-plugins
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…
Testing Skills With Subagents
ed3dai/ed3d-plugins
A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
Brainstorming
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
Writing Good Tests
ed3dai/ed3d-plugins
A skill your agent uses when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Writing Skills
ed3dai/ed3d-plugins
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…
Coding Effectively
ed3dai/ed3d-plugins
ALWAYS use this skill when writing or refactoring code. An agent skill from ed3dai/ed3d-plugins.
Related
Categories
Questions about Writing For A Technical Audience
What does Writing For A Technical Audience do?
A skill your agent uses when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns…. Writing For A Technical Audience is an agent skill from ed3dai/ed3d-plugins.
When should I use Writing For A Technical Audience?
Writing For A Technical Audience fits situations like: writing documentation; technical content for developers - enforces clarity; authenticity while avoiding AI writing patterns that signal inauthenticity.
How do I install Writing For A Technical Audience in Claude Code?
Run `npx skills add ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a claude-code`. Or copy the skill folder (plugins/ed3d-house-style/skills/writing-for-a-technical-audience in ed3dai/ed3d-plugins) into .claude/skills/writing-for-a-technical-audience in your project. Claude Code loads it when a task matches its description.
How do I install Writing For A Technical Audience in Codex?
Run `npx skills add ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a codex`. Or copy the skill folder (plugins/ed3d-house-style/skills/writing-for-a-technical-audience in ed3dai/ed3d-plugins) into .agents/skills/writing-for-a-technical-audience in your project. Codex loads it when a task matches its description.
Can I use Writing For A Technical Audience 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 ed3dai/ed3d-plugins --skill writing-for-a-technical-audience -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-for-a-technical-audience, .gemini/skills/writing-for-a-technical-audience, .github/skills/writing-for-a-technical-audience and .opencode/skills/writing-for-a-technical-audience in your project.
What does Writing For A Technical Audience need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing For A Technical Audience is instructions for the agent only. Our summary lists: Python 3; Node.js; A credential in YOUR_API_KEY.
Does Writing For A Technical Audience 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 Writing For A Technical Audience 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 Writing For A Technical Audience use?
No licence was found for Writing For A Technical Audience or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing For A Technical Audience use?
About 3.9k tokens (SKILL.md is roughly 15k 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 Writing For A Technical Audience?
Skills that share tags, products or a category with Writing For A Technical Audience: Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing For A Technical Audience?
ed3dai (a GitHub organization) maintains it in ed3dai/ed3d-plugins, which has 250 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 6, 2026.
Source: ed3dai/ed3d-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.