Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Write or edit engineering posts with supported claims. An agent skill from pedronauck/skills.
Install Writing Tech Post
$ npx skills add pedronauck/skills --skill writing-tech-post -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pedronauck/skills writing-tech-post --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/pedronauck/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mine/writing-tech-post .claude/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .claude/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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/pedronauck/skills/tree/main/skills/mine/writing-tech-postType 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 pedronauck/skills --skill writing-tech-post -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pedronauck/skills writing-tech-post --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mine/writing-tech-post .agents/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .agents/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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 pedronauck/skills --skill writing-tech-post -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pedronauck/skills writing-tech-post --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mine/writing-tech-post .cursor/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .cursor/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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/pedronauck/skills.git --path skills/mine/writing-tech-post--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 pedronauck/skills --skill writing-tech-post -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pedronauck/skills writing-tech-post --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mine/writing-tech-post .gemini/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .gemini/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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 pedronauck/skills writing-tech-postInstalls 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 pedronauck/skills --skill writing-tech-post -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mine/writing-tech-post .github/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .github/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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 pedronauck/skills --skill writing-tech-post -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pedronauck/skills writing-tech-post --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mine/writing-tech-post .opencode/skills/writing-tech-post && 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-tech-post" agent skill from https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post into .opencode/skills/writing-tech-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tech-post", 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-tech-post- GitHub stars
- 634
- Used in
- 1 other repo
- Token cost
- ~750 tokens
- SKILL.md length
- 297 words
- Files
- 27 (incl. scripts, references, assets)
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- None found
At a glance
Write or edit engineering posts with supported claims. An agent skill from pedronauck/skills.
- Works in 5 steps: Establish the reader, main point, and… → For a new post, choose a useful primary… → Explain the mechanism and why it… → …
- Publication reviews
- Calls python3
- Excludes marketing pages
What it does
Writing Tech Post is an agent skill from pedronauck/skills. Write or edit engineering posts with supported claims. Use for drafts, rewrites, and publication reviews; excludes marketing pages, API references, release notes, and internal specs.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 28 other files, including scripts, reference files and assets (for example `assets/evidence-block.snippets.md`, `assets/frontmatter.template.md` and `assets/outline.ai-agent-post.md`).
It sits in Development, covering Changelog and release notes. The repository describes itself as: My personal favorite skills.
When your agent uses it
- Publication reviews
- Excludes marketing pages
Example prompts
- “/writing-tech-post”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Establish the reader, main point, and supported facts from available context. Ask only for missing information that materially affects the…
- For a new post, choose a useful primary archetype and outline. For an existing draft, retain working structure and edit the requested…
- Explain the mechanism and why it matters. Support quantitative, comparative, security, and capability claims with appropriate evidence and…
- Refine voice and flow where needed. Publisher style matrices, H2 question chains, and first/last-200-word comparisons are editorial…
- Before external publication, apply references/pre-publish-checklist.md to the relevant claims and disclosure obligations. Draft delivery…
What it can do on your machine
Read from SKILL.md and the folder at commit 0422940. 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
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python3
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 Tech Post loads about 750 tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 297 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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 297 words (~750 tokens).
“Produce the requested artifact: a new post, an outline, a focused rewrite, or a publication review. Reuse the accepted brief and evidence. Choose a structure that fits the reader and material; a small edit does not restart an entire authoring…”
- name
- writing-tech-post
- metadata.author
- Pedro Nauck
- metadata.github
- https://github.com/pedronauck
- metadata.repository
- https://github.com/pedronauck/skills
Files
SKILL.md and 26 other files (scripts, references, assets) in skills/mine/writing-tech-post of pedronauck/skills.
- SKILL.md
- assets/evidence-block.snippets.md
- assets/frontmatter.template.md
- assets/outline.ai-agent-post.md
- assets/outline.launch-deep-dive.md
- assets/outline.migration.md
- assets/outline.performance.md
- assets/outline.postmortem.md
- assets/outline.research-translation.md
- assets/outline.security-disclosure.md
- assets/outline.tutorial.md
- references/ai-and-agents.md
- references/anti-patterns.md
- references/archetypes-and-structure.md
- references/depth-and-abstraction.md
- references/evidence-diagrams-code.md
- references/migrations.md
- references/narrative-and-pacing.md
- references/performance-deep-dive.md
- … and 8 more
Open the folder on GitHubat commit 0422940
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in pedronauck/skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Writing Tech Post 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 Tech Post this skillpedronauck/skills | 634 | 1 repos | ~750 | Automated safety check: Pass | None | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from pedronauck/skills
All 65 skills in this repoDeep Review
pedronauck/skills
Review branch diffs, working trees, or PRs in depth with defect, polish and cross-contract coverage.
Yc Apply
pedronauck/skills
Prepare, review, and package Y Combinator application answers and founder-video notes using the live form and verified founder facts.
Professional Communication
pedronauck/skills
Guide technical communication for software developers. An agent skill from pedronauck/skills.
Tauri V2
pedronauck/skills
Tauri v2+ cross-platform app development with Rust backend. An agent skill from pedronauck/skills.
Hormozi Ad Factory
pedronauck/skills
Generates 150-750+ ad variations using Alex Hormozi's combinatorial Hook x Meat x CTA framework.
Yt Master
pedronauck/skills
Plans and improves YouTube ideas, titles, thumbnail concepts, scripts, retention, channel strategy, and metric-based diagnosis.
Related
Categories
Questions about Writing Tech Post
What does Writing Tech Post do?
Write or edit engineering posts with supported claims. An agent skill from pedronauck/skills. Writing Tech Post is an agent skill from pedronauck/skills. Write or edit engineering posts with supported claims.
When should I use Writing Tech Post?
Writing Tech Post fits situations like: publication reviews; excludes marketing pages.
How do I install Writing Tech Post in Claude Code?
Run `npx skills add pedronauck/skills --skill writing-tech-post -a claude-code`. Or copy the skill folder (skills/mine/writing-tech-post in pedronauck/skills) into .claude/skills/writing-tech-post in your project. Claude Code loads it when a task matches its description.
How do I install Writing Tech Post in Codex?
Run `npx skills add pedronauck/skills --skill writing-tech-post -a codex`. Or copy the skill folder (skills/mine/writing-tech-post in pedronauck/skills) into .agents/skills/writing-tech-post in your project. Codex loads it when a task matches its description.
Can I use Writing Tech Post 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 pedronauck/skills --skill writing-tech-post -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-tech-post, .gemini/skills/writing-tech-post, .github/skills/writing-tech-post and .opencode/skills/writing-tech-post in your project.
What does Writing Tech Post need to run?
Going by SKILL.md and its folder, Writing Tech Post needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Writing Tech Post 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 Tech Post 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Writing Tech Post use?
No licence was found for Writing Tech Post or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Tech Post use?
About 750 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 35k tokens, read only when the agent opens those files.
What are the alternatives to Writing Tech Post?
Skills that share tags, products or a category with Writing Tech Post: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Tech Post?
pedronauck (a GitHub user) maintains it in pedronauck/skills, which has 634 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on September 14, 2026.
Source: pedronauck/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.