Writing Tech Post

Community

pedronauck

writing-tech-post

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.

Overview

Publisher	pedronauck
Repository	`skills`
Skill name	`writing-tech-post`
Stars	635
Forks	89
Bundled files	25
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
25 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by pedronauck on GitHub. Read the source before you install it.

Installation

Install the Writing Tech Post AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/pedronauck/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/mine/writing-tech-post .claude/skills/writing-tech-post

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Writing Tech Post in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Writing Tech Post on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Writing Tech Post is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Writing Engineering Posts

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 workflow.

Establish the reader, main point, and supported facts from available context. Ask only for missing information that materially affects the requested output.
For a new post, choose a useful primary archetype and outline. For an existing draft, retain working structure and edit the requested scope. Frontmatter, rung labels, depth tuples, and per-section evidence plans are optional tools unless the publisher requires them.
Explain the mechanism and why it matters. Support quantitative, comparative, security, and capability claims with appropriate evidence and limitations. Distinguish actual measurements, illustrative examples, hypotheses, and work still in progress.
Refine voice and flow where needed. Publisher style matrices, H2 question chains, and first/last-200-word comparisons are editorial heuristics, not universal gates. Do not invent failed mitigations, partial victories, benchmark results, or lessons to satisfy an arc.
Before external publication, apply references/pre-publish-checklist.md to the relevant claims and disclosure obligations. Draft delivery is not publication authorization. The optional linter reports heuristics; human factual review owns unsupported claims and disclosure decisions.

Reference router

Read the reference for the current archetype or editing concern, not every phase:

Structure: references/archetypes-and-structure.md; optional depth diagnosis: references/depth-and-abstraction.md.
Incident: references/postmortems.md; migration: references/migrations.md; performance: references/performance-deep-dive.md.
AI/agents: references/ai-and-agents.md; security/reliability: references/security-and-reliability.md.
Evidence/assets: references/evidence-diagrams-code.md; narrative: references/narrative-and-pacing.md.
Voice/disclosure: references/voice-and-disclosure.md; a requested publisher register: references/publisher-voice-matrix.md; specific prose problems: references/anti-patterns.md.

Use an assets/outline.<archetype>.md template only when useful; omit irrelevant sections. Run helpers through this skill's absolute directory: python3 <writing-tech-post-dir>/scripts/lint-post.py <draft.md>. --strict makes heuristic warnings fail for an explicitly chosen editorial gate. A clean lint result does not prove factuality or disclosure readiness.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Writing Tech Post AI skill do?

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.

Why use Writing Tech Post on TypingMind?

Because you install it once and use it with any model. Writing Tech Post is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Writing Tech Post in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pedronauck/skills/tree/main/skills/mine/writing-tech-post. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Writing Tech Post?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Writing Tech Post?

As many as you like. As long as a model supports skills, you can use Writing Tech Post with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Writing Tech Post AI skill free?

It is published on GitHub by pedronauck. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Writing Engineering Posts

Reference router

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now