Content Writer Agent
mastra-ai/mastra
Authoring playbook for building agents that draft written content — blog posts, marketing copy, social media posts, newsletters, product descriptions, landing pages, or ad copy.
Write or develop a blog post. An agent skill from techwolf-ai/ai-first-toolkit.
Install Write Blog Post
$ npx skills add techwolf-ai/ai-first-toolkit --skill write-blog-post -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit write-blog-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/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .claude/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .claude/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-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 techwolf-ai/ai-first-toolkit --skill write-blog-post -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit write-blog-post --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .agents/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .agents/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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 techwolf-ai/ai-first-toolkit --skill write-blog-post -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit write-blog-post --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .cursor/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .cursor/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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/techwolf-ai/ai-first-toolkit.git --path plugins/content-studio/skills/write-blog-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 techwolf-ai/ai-first-toolkit --skill write-blog-post -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit write-blog-post --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .gemini/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .gemini/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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 techwolf-ai/ai-first-toolkit write-blog-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 techwolf-ai/ai-first-toolkit --skill write-blog-post -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .github/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .github/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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 techwolf-ai/ai-first-toolkit --skill write-blog-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 techwolf-ai/ai-first-toolkit write-blog-post --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/content-studio/skills/write-blog-post .opencode/skills/write-blog-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 "write-blog-post" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-blog-post into .opencode/skills/write-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-blog-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
write-blog-post- GitHub stars
- 132
- Token cost
- ~1.1k tokens
- SKILL.md length
- 572 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write or develop a blog post. An agent skill from techwolf-ai/ai-first-toolkit.
- Works in 4 steps: Run ./scripts/print-published.sh… → Run ./scripts/print-published.sh… → Read guidelines/linkedin.md for style… → …
- Blog content - writing
- SKILL.md covers Before Writing (MANDATORY), Avoid Repetitive Patterns, Style Requirements and Structure, plus 5 more sections
- Runs Shell scripts from its folder
What it does
Write Blog Post is an agent skill from techwolf-ai/ai-first-toolkit. Write or develop a blog post. Use for blog content - writing, drafting, developing ideas into drafts, or editing. Longer-form than LinkedIn (800-1200 words) with section structure.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/check-word-count.sh`).
It sits in Writing & Content, covering Blog and article writing. It works with LinkedIn. The repository describes itself as: Open-source Claude Code skills and Codex skills for AI-first work. Audit, re-engineer, and bootstrap projects with AI-first design principles. The licence is MIT.
When your agent uses it
- Blog content - writing
- Developing ideas into drafts
Example prompts
- “/write-blog-post”
Requirements
- A Bash shell
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run ./scripts/print-published.sh linkedin-post to read ALL published LinkedIn posts
- Run ./scripts/print-published.sh blog-post to read ALL published blog posts
- Read guidelines/linkedin.md for style rules (same voice applies to blog posts)
- Read references/professional-profile.md for background
What it can do on your machine
Read from SKILL.md and the folder at commit 2ee7841. 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/ (Shell), which the agent can run.
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
Write Blog Post loads about 1.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 572 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
The full file from techwolf-ai/ai-first-toolkit at commit 2ee7841, republished under its MIT licence (© techwolf-ai). 572 words, ~1,110 tokens.
Download SKILL.mdSave it as
.claude/skills/write-blog-post/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- write-blog-post
- description
- Write or develop a blog post. Use for blog content - writing, drafting, developing ideas into drafts, or editing. Longer-form than LinkedIn (800-1200 words) with section structure.
Write Blog Post
You are helping write a blog post for the author.
Before Writing (MANDATORY)
You MUST complete these steps before writing ANY content:
- Run
./scripts/print-published.sh linkedin-postto read ALL published LinkedIn posts- Blog posts share the same voice as LinkedIn posts, so these are your primary style reference
- Note core insights and data points already used
- Identify opportunities to reference or build on previous posts
- Run
./scripts/print-published.sh blog-postto read ALL published blog posts- Avoid repeating topics, angles, or arguments already covered
- Note the structure and depth of existing blog posts
- Read
guidelines/linkedin.mdfor style rules (same voice applies to blog posts) - Read
references/professional-profile.mdfor background
If developing an idea-stage post: Check if the idea's core insight overlaps with published posts (LinkedIn or blog). If so, either:
- Find a genuinely different angle
- Explicitly build on the previous piece
- Recommend against developing the idea
Avoid Repetitive Patterns
When reading recent posts, actively note and vary:
Openings: Vary between demand signal, personal anecdote, company experience, surprising data Section flow: Don't always follow the same arc (problem-solution-data-close) Closing lines: Find fresh ways to land the argument Examples: Rotate between company-specific, industry, and broader examples Rhetorical devices: If recent pieces use lists heavily, try flowing narrative, and vice versa
The goal is a consistent voice with varied execution.
Style Requirements
- 800-1200 words (use
wc -wto verify) - English language
- Section headings (## level) to break up the piece into 5-7 sections
- First person throughout
- Conversational tone - read it aloud, does it sound like something you'd say?
- Specific > abstract - lead with concrete examples, generalize later
- No hype words ("revolutionary", "game-changing", "transformative")
- Strong opening - first 2-3 sentences must hook the reader with something concrete
Structure
Blog posts are longer than LinkedIn posts and need more structure. A typical blog post has:
- Hook (80-100 words) - Concrete opening that pulls the reader in
- 3-5 body sections (150-200 words each) - Each with a clear heading and one main point
- Close (50-75 words) - Echo the opening or land the core argument
Each section should earn its place. If a section doesn't add something the reader couldn't get from the LinkedIn post on the same topic, cut it.
Show full SKILL.md (207 more words)Show less
Relationship to LinkedIn Posts
Blog posts often expand on ideas first introduced in LinkedIn posts. When this happens:
- Reference the LinkedIn post briefly, don't re-explain it
- Go deeper on the angle the LinkedIn post couldn't cover in 200 words
- Add the meta-story, the data, or the "why" behind the insight
- Blog posts should reward readers who already saw the LinkedIn post AND stand alone for those who didn't
Process
- If given a topic, develop it into a full draft
- If given an existing idea file (search with
./scripts/search-posts.sh), develop the content - Always check word count against 800-1200 target
- Save to content/posts/blog-post/ with type: blog-post, stage: 02-drafts
Validation
After saving the draft, run the word count checker:
scripts/check-word-count.sh <yaml-file>Adjust the content if the word count is outside the 800-1200 target.
Sub-Agent Review
Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should:
- Check voice consistency against
guidelines/linkedin.md(same voice applies) - Verify each section earns its place and adds depth beyond a LinkedIn post
- Flag any overlap with published posts (LinkedIn or blog)
- Check for hype words, generic phrasing, or sections that could be cut
Incorporate the reviewer's feedback before finalizing.
Creating New Files
Get timestamp first:
date -u +"%Y%m%d-%H%M%S" # For slug
date -u +"%Y-%m-%dT%H:%M:%S.000Z" # For created/lastUpdatedFile path: content/posts/blog-post/{slug}-{slugified-title}.yaml
© techwolf-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in plugins/content-studio/skills/write-blog-post of techwolf-ai/ai-first-toolkit.
- SKILL.md
- scripts/check-word-count.sh
Open the folder on GitHubat commit 2ee7841
Compare with similar skills
Write Blog 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 |
|---|---|---|---|---|---|---|
| Write Blog Post this skilltechwolf-ai/ai-first-toolkit | 132 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Content Writer Agentmastra-ai/mastra | 29k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Content Writerchrispangg/deepagentsdk | 128 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Linkedin Writerflaqai/backlink_skills | 750 | — | ~6k | Automated safety check: Pass | MIT | |
| Social Media Managementmanojbajaj95/claude-gtm-plugin | 104 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Li RepurposeJakeschincariol/linkedin-agent-skill | 1.4k | — | ~680 | Automated safety check: Pass | MIT |
Similar skills
Content Writer
chrispangg/deepagentsdk
Writing content across different platforms and styles. An agent skill from chrispangg/deepagentsdk.
Linkedin Writer
flaqai/backlink_skills
LinkedIn-native long-form article and newsletter writing workflow for LinkedIn and Google-to-LinkedIn topic discovery, business-depth research, professional thought leadership, evidence-led…
Social Media Management
manojbajaj95/claude-gtm-plugin
Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).
Li Repurpose
Jakeschincariol/linkedin-agent-skill
Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts.
Blog Repurpose
AgriciDaniel/claude-blog
Repurpose blog posts for social media, email, video, podcast, and community channels.
More from techwolf-ai/ai-first-toolkit
All 29 skills in this repoTask Profile
techwolf-ai/ai-first-toolkit
Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would…
Token Doctor
techwolf-ai/ai-first-toolkit
Personal diagnosis of where your Claude Code + Cowork spend goes.
Session Search
techwolf-ai/ai-first-toolkit
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac.
Write Opinion
techwolf-ai/ai-first-toolkit
Write or develop an opinion piece (opiniestuk/op-ed). An agent skill from techwolf-ai/ai-first-toolkit.
AI Firstify
techwolf-ai/ai-first-toolkit
Analyze, re-engineer, or bootstrap projects to align with AI-first design principles.
Analyze Performance
techwolf-ai/ai-first-toolkit
Analyze engagement patterns across published posts to identify what works.
Related
Works with
Categories
Questions about Write Blog Post
What does Write Blog Post do?
Write or develop a blog post. An agent skill from techwolf-ai/ai-first-toolkit. Write Blog Post is an agent skill from techwolf-ai/ai-first-toolkit. Write or develop a blog post.
When should I use Write Blog Post?
Write Blog Post fits situations like: blog content - writing; developing ideas into drafts.
How do I install Write Blog Post in Claude Code?
Run `npx skills add techwolf-ai/ai-first-toolkit --skill write-blog-post -a claude-code`. Or copy the skill folder (plugins/content-studio/skills/write-blog-post in techwolf-ai/ai-first-toolkit) into .claude/skills/write-blog-post in your project. Claude Code loads it when a task matches its description.
How do I install Write Blog Post in Codex?
Run `npx skills add techwolf-ai/ai-first-toolkit --skill write-blog-post -a codex`. Or copy the skill folder (plugins/content-studio/skills/write-blog-post in techwolf-ai/ai-first-toolkit) into .agents/skills/write-blog-post in your project. Codex loads it when a task matches its description.
Can I use Write Blog 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 techwolf-ai/ai-first-toolkit --skill write-blog-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/write-blog-post, .gemini/skills/write-blog-post, .github/skills/write-blog-post and .opencode/skills/write-blog-post in your project.
What does Write Blog Post need to run?
Going by SKILL.md and its folder, Write Blog Post needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Write Blog 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 Write Blog 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 Write Blog Post use?
Write Blog Post is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Blog Post use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Write Blog Post?
Skills that share tags, products or a category with Write Blog Post: Content Writer Agent (mastra-ai/mastra, 29k stars), Content Writer (chrispangg/deepagentsdk, 128 stars), Linkedin Writer (flaqai/backlink_skills, 750 stars) and Social Media Management (manojbajaj95/claude-gtm-plugin, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Blog Post?
techwolf-ai (a GitHub organization) maintains it in techwolf-ai/ai-first-toolkit, which has 132 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on September 29, 2026.
Source: techwolf-ai/ai-first-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.