Rnd Technical Writer
chendongqi/OPB-Skills
Technical article writing assistant. An agent skill from chendongqi/OPB-Skills.
Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.
$ npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --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/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/writing-and-content/blog-post-writing .claude/skills/blog-post-writing && 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 "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .claude/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writingType 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 seb1n/awesome-ai-agent-skills --skill blog-post-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/writing-and-content/blog-post-writing .agents/skills/blog-post-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .agents/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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 seb1n/awesome-ai-agent-skills --skill blog-post-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/writing-and-content/blog-post-writing .cursor/skills/blog-post-writing && 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 "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .cursor/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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/seb1n/awesome-ai-agent-skills.git --path writing-and-content/blog-post-writing--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 seb1n/awesome-ai-agent-skills --skill blog-post-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/writing-and-content/blog-post-writing .gemini/skills/blog-post-writing && 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 "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .gemini/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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 seb1n/awesome-ai-agent-skills blog-post-writingInstalls 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 seb1n/awesome-ai-agent-skills --skill blog-post-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/writing-and-content/blog-post-writing .github/skills/blog-post-writing && 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 "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .github/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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 seb1n/awesome-ai-agent-skills --skill blog-post-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/writing-and-content/blog-post-writing .opencode/skills/blog-post-writing && 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 "blog-post-writing" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/blog-post-writing into .opencode/skills/blog-post-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-post-writing", 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.
blog-post-writingWrite high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.
Blog Post Writing is an agent skill from seb1n/awesome-ai-agent-skills. Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action. Use when the user requests blog post writing or provides relevant inputs for this workflow.
Its SKILL.md is about 2.5k 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 Blog and article writing and Technical writing. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blog Post Writing loads about 2.5k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 1,408 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.
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.
The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 1,408 words, ~2,474 tokens.
.claude/skills/blog-post-writing/SKILL.md (or your agent's skills folder).This skill enables an AI agent to write well-structured, engaging, and SEO-optimized blog posts across multiple content types — how-to guides, listicles, opinion pieces, case studies, and thought leadership articles. The agent handles the full lifecycle from topic research and outlining through drafting, SEO optimization, and final review, producing publish-ready content tailored to the target audience and brand voice.
Research the Topic and Keywords Investigate the topic to understand its scope, current discourse, and search intent. Identify a primary keyword and 3-5 secondary keywords to target. Analyze the top-ranking content for the primary keyword to understand what angle, depth, and format performs well. Determine whether the search intent is informational ("how to set up CI/CD"), navigational ("GitHub Actions docs"), or transactional ("best CI/CD tools 2025").
Choose the Content Format Select the blog post format that best matches the topic and search intent. Use a how-to guide for process-oriented queries. Use a listicle for comparison or round-up queries. Use an opinion piece for thought leadership and brand positioning. Use a case study for showcasing results and building credibility. The format determines the structural template for the outline.
Build the Outline Create a detailed outline with the title (including the primary keyword), a hook for the introduction, H2 and H3 subheadings for the body, and a conclusion with a call-to-action. Ensure headings are descriptive and incorporate secondary keywords naturally. Plan where to place supporting elements — code blocks, images, blockquotes, statistics, and internal/external links.
Write the Draft Expand the outline into full prose. Open with a hook that creates curiosity, states a surprising fact, or directly addresses the reader's pain point. Follow with a clear thesis sentence that tells the reader what they will gain from the post. Write body sections in a logical progression, using transitions between sections. Close with a summary of key takeaways and a specific CTA — subscribe, download, try the product, or read a related post.
Optimize for SEO Place the primary keyword in the title, first paragraph, at least one H2, and the meta description. Use secondary keywords in subheadings and body text where they fit naturally — never force them. Write a meta description (150-160 characters) that summarizes the post and includes the primary keyword. Add alt text descriptions for any images. Ensure the URL slug is short and keyword-rich.
Review and Polish Proofread for grammar, spelling, and punctuation. Verify all statistics and claims have credible sources. Check that all links work and point to the correct destinations. Read the post aloud (or simulate doing so) to catch awkward phrasing. Ensure the post meets the target word count and that no section feels thin or padded.
Provide the agent with:
Example prompt: "Write a 1,500-word how-to blog post about setting up a CI/CD pipeline with GitHub Actions. Target keyword: 'GitHub Actions CI/CD tutorial.' Audience: junior developers. Tone: friendly and encouraging."
Input: "Write an outline for a listicle: '7 VS Code Extensions Every Python Developer Needs in 2025.' Audience: intermediate Python developers. Fill in the intro and one list item as examples."
Output:
Title: 7 VS Code Extensions Every Python Developer Needs in 2025
Meta description: Boost your Python workflow with these 7 essential VS Code extensions for linting, testing, debugging, and more. Updated for 2025.
Target keyword: VS Code extensions Python
Introduction (filled in):
Visual Studio Code became the most popular code editor among Python developers for good reason — it is fast, free, and infinitely customizable. But a stock VS Code install only scratches the surface. The right extensions can turn it into a full-featured Python IDE with intelligent autocomplete, real-time linting, one-click debugging, and seamless virtual environment management. Here are seven extensions that will save you real time every single day in 2025.
1. Pylance — Supercharged IntelliSense (filled in):
Pylance replaces the default Python language server with a blazing-fast type checker and autocomplete engine built on Pyright. It catches type errors before you run your code, surfaces inline documentation as you type, and handles complex type annotations that the default extension misses entirely. If you write any amount of typed Python — and you should — Pylance is non-negotiable. Install it once and you will wonder how you ever coded without it.
2. Ruff — Lightning-Fast Linting and Formatting [to be filled]
3. Python Test Explorer — Visual Test Runner [to be filled]
4. GitLens — Git History in Your Editor [to be filled]
5. Docker — Container Management [to be filled]
6. Jupyter — Interactive Notebooks Inside VS Code [to be filled]
7. autoDocstring — One-Click Docstrings [to be filled]
Conclusion: Recap the extensions, emphasize that a well-configured editor is a productivity multiplier, and CTA: "Share your favorite Python extension in the comments."
Input: "Write an intro paragraph for a blog post titled 'Why Your Startup Should Adopt Infrastructure as Code on Day One.' Audience: non-technical startup founders. Hook style: surprising statistic."
Output:
Sixty-eight percent of startups that experience a major infrastructure outage in their first year never fully recover the lost customers. That is not a scare tactic — it is a finding from a 2024 Datadog reliability survey. The irony is that most of these outages trace back to manual server configuration: someone fat-fingered a setting, forgot to open a port, or could not reproduce the production environment when it mattered most. Infrastructure as Code (IaC) eliminates this entire category of risk by treating your servers, networks, and deployments as version-controlled code — code that can be reviewed, tested, and rolled back just like the software it runs. You do not need a dedicated DevOps team to get started, and the earlier you adopt it, the less technical debt you accumulate. In this post, we will break down what IaC actually is, why it matters even at the five-person stage, and how to set it up in a single afternoon.
© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in writing-and-content/blog-post-writing of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
Blog Post Writing 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 |
|---|---|---|---|---|---|---|
| Blog Post Writing this skillseb1n/awesome-ai-agent-skills | 206 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Rnd Technical Writerchendongqi/OPB-Skills | 126 | — | ~2.5k | Automated safety check: Pass | None | |
| Dynamo Content DesignerDynamoDS/Dynamo | 2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Voicejvm-skills/jvm-skills | 139 | — | ~592 | Automated safety check: Pass | Apache-2.0 | |
| Domodomo Release Documentationdarknecrocities/DomoDomo---All-in-one-Tool | 239 | — | ~17k | Automated safety check: Pass | None | |
| Reading Levelthedaviddias/Front-End-Checklist | 74k | — | ~613 | Automated safety check: Pass | MIT |
chendongqi/OPB-Skills
Technical article writing assistant. An agent skill from chendongqi/OPB-Skills.
DynamoDS/Dynamo
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
jvm-skills/jvm-skills
Make prose sound like Thomas, not like a generic technical writer.
darknecrocities/DomoDomo---All-in-one-Tool
Maintain DomoDomo product documentation, technical tool records, About metrics, blog posts, SEO metadata, sitemap generation, release communication, and contributor guidance.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing content pages for user experience and SEO.
Affitor/affiliate-skills
Write how-to guides and tutorials that naturally integrate affiliate product recommendations.
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Categories
Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action. Blog Post Writing is an agent skill from seb1n/awesome-ai-agent-skills. Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.
Blog Post Writing fits situations like: the user requests blog post writing; provides relevant inputs for this workflow.
Run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a claude-code`. Or copy the skill folder (writing-and-content/blog-post-writing in seb1n/awesome-ai-agent-skills) into .claude/skills/blog-post-writing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a codex`. Or copy the skill folder (writing-and-content/blog-post-writing in seb1n/awesome-ai-agent-skills) into .agents/skills/blog-post-writing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-post-writing, .gemini/skills/blog-post-writing, .github/skills/blog-post-writing and .opencode/skills/blog-post-writing in your project.
SKILL.md names no scripts, command-line tools or credentials: Blog Post Writing is instructions for the agent only. Our summary lists: Python 3; Docker.
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.
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.
Blog Post Writing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blog Post Writing: Rnd Technical Writer (chendongqi/OPB-Skills, 126 stars), Dynamo Content Designer (DynamoDS/Dynamo, 2k stars), Voice (jvm-skills/jvm-skills, 139 stars) and Domodomo Release Documentation (darknecrocities/DomoDomo---All-in-one-Tool, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.