create-blog-article
Create an SEO-optimized blog article for a Claude Code component with AI-generated cover image
Install / Use
npx skills add davila7/claude-code-templatesInstalls into whichever agent you are using.
Claude Commands
Claude Code slash commands
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of create-blog-article
create-blog-article scores 96/100 on our quality scale, 45th of 1,155 Content & Media skills we index (top 4%).
Its Claude Commands is 14 KB long, well organised into 17 sections with 16 code examples: a thorough specification that gives an agent plenty to work with.
With 33,517 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 2 days ago, so create-blog-article is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
create-blog-article compared with similar skills
All 4 of these similar skills score higher than create-blog-article; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| create-blog-article (this skill)by davila7 | 96 | 33.5k | 2d ago | Claude Commands |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
Frequently asked questions
- How do I install create-blog-article?
- Run
npx skills add davila7/claude-code-templates. The install tabs above show the steps for each supported agent. - Which AI agents does create-blog-article work with?
- It is written for Claude Code and Zed, as a Claude Commands file. Other agents that read the same format can often use it too.
- Is create-blog-article safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is create-blog-article still maintained?
- The repository was last updated 2 days ago, so create-blog-article is actively maintained.
Skill content
View source on GitHuballowed-tools: Read, Write, Edit, Bash(python3:), Bash(mkdir:), Bash(rm:*) argument-hint: <component-path> description: Create an SEO-optimized blog article for a Claude Code component with AI-generated cover image
Create Blog Article for Claude Code Component
You will create a complete, SEO-optimized blog article for a Claude Code component.
Component Path Argument
Component path provided: $ARGUMENTS
Expected format examples:
development-team/frontend-developer(for agents)supabase(for MCPs)productivity/nowait(for skills)
Step 1: Identify Component Type and Read Component File
Based on the path structure, determine the component type:
- If path has
/, could be an agent, MCP, command, skill, or hook in a folder - Single word could be MCP, command, or skill
Read the component file:
- Agents:
cli-tool/components/agents/$ARGUMENTS.md(e.g.,development-team/frontend-developer.md) - MCPs:
cli-tool/components/mcps/$ARGUMENTS.json(e.g.,devtools/context7.json) - Skills:
cli-tool/components/skills/$ARGUMENTS/SKILL.md - Commands:
cli-tool/components/commands/$ARGUMENTS.md(e.g.,setup/ci-cd-pipeline.md) - Hooks:
cli-tool/components/hooks/$ARGUMENTS.md
CRITICAL: Use find or grep to locate the actual file path first, then extract folder/name structure.
Extract from the component file:
name: Component namedescription: Component descriptiontools: Available tools (for agents)- Key capabilities and focus areas from the content
Step 2: Generate Component-Specific Blog ID and Names
From the component path, create:
-
Blog ID: Convert path to blog-friendly ID
- Example:
development-team/frontend-developer→frontend-developer-agent - Example:
supabase→supabase-mcp - Example:
productivity/nowait→nowait-skill
- Example:
-
Component Name: Human-readable name
- Example:
frontend-developer→Frontend Developer - Example:
supabase→Supabase
- Example:
-
Component Type: Uppercase type
- AGENT, MCP, SKILL, COMMAND, HOOK
Step 3: Generate Cover Image FIRST
CRITICAL: Generate the cover image BEFORE creating the HTML file.
Use the Python script to generate the image:
python3 scripts/generate_blog_images.py
But first, temporarily add a new entry to docs/blog/blog-articles.json with:
{
"id": "[blog-id]",
"title": "Temporary",
"description": "Temporary",
"url": "[blog-id]/",
"image": "https://www.aitmpl.com/blog/assets/[blog-id]-cover.png",
"category": "[Component Type]",
"publishDate": "2025-01-15",
"readTime": "4 min read",
"tags": ["Claude Code"],
"difficulty": "basic",
"featured": true,
"order": 999
}
Then run the script, which will:
- Detect the new entry
- Find the component path
- Generate the image at
docs/blog/assets/[blog-id]-cover.png
After image generation, update the entry with correct information.
Step 4: Create Blog Article HTML
Create directory:
mkdir -p docs/blog/[blog-id]
CRITICAL PROCESS:
-
First, READ the template file completely:
Read docs/blog/code-reviewer-agent/index.html -
Copy the ENTIRE content to the new file location:
Write docs/blog/[blog-id]/index.html -
Then, ONLY replace the specific content sections (listed below)
DO NOT:
- ❌ Create HTML from scratch
- ❌ Use a different template
- ❌ Simplify or remove any scripts
- ❌ Change the header/footer structure
- ❌ Modify CSS paths or class names
Create docs/blog/[blog-id]/index.html using this process:
HTML Template Structure
CRITICAL: Use docs/blog/code-reviewer-agent/index.html as the EXACT base template.
This template includes ALL required components:
- ✅ Header with
class="header"(NOT "blog-header") - ✅ ASCII art logo in terminal-header
- ✅ Copy as Markdown button (
id="copy-markdown-btn") - ✅ Proper article structure:
article-header→article-body→article-content-full - ✅ "Explore Components" banner at the end of content
- ✅ Footer with ASCII art and links
- ✅ CodeCopy script (adds copy buttons to code blocks)
- ✅ MarkdownCopier script (copy entire article as markdown)
- ✅ Mermaid diagram support script
DO NOT create custom HTML structure - copy the template EXACTLY and only replace the content-specific parts.
How to Use the Template:
- Copy the entire file from
code-reviewer-agent/index.html - Only replace these specific content areas:
- SEO meta tags (title, description, keywords, Open Graph)
- Article title and subtitle in
<h1>and<p class="article-subtitle"> - Tags in
<div class="article-tags"> - Main content inside
<div class="article-content-full">(everything between the opening and closing div) - Cover image src and alt text
- Keep EVERYTHING else unchanged:
- Header structure and navigation
- Copy Markdown button
- Footer with ASCII art
- All three scripts at the end (CodeCopy, MarkdownCopier, Mermaid)
- CSS links and paths
Key SEO Elements to Customize:
Title Tag (Line 6):
<title>[Component Name] for Claude Code: [Key Technologies] Expert AI Assistant</title>
Meta Description (Line 26):
<meta name="description" content="Install the [Component Name] for Claude Code to [main benefit]. AI-powered [component type] for [key features].">
Open Graph Tags (Lines 28-32):
<meta property="og:title" content="[Component Name] for Claude Code: [Key Technologies]">
<meta property="og:description" content="Install the [Component Name] for Claude Code...">
Keywords (Line 58): Focus on: Claude Code, Component Type, Main Technologies
<meta name="keywords" content="Claude Code [type], [Component Name], Claude Code [tech1], [tech2], AI [domain] development, ...">
Structured Data (Lines 81-136):
{
"@type": "BlogPosting",
"headline": "[Component Name] for Claude Code: [Technologies]",
"keywords": "Claude Code [type], [Component Name], ...",
"articleSection": "Claude Code [Type]s",
"about": [
{"@type": "Thing", "name": "Claude Code"},
{"@type": "Thing", "name": "[Component Type]"},
...
]
}
Article Header (Lines 189-201):
<h1 class="article-title">[Component Name] for Claude Code: [Technologies]</h1>
<p class="article-subtitle">Learn how to install and use the [Component Name] for Claude Code to [benefits].</p>
<div class="article-tags">
<span class="tag">Claude Code</span>
<span class="tag">[Type]</span>
<span class="tag">[Tech1]</span>
<span class="tag">[Tech2]</span>
</div>
Content Sections:
What is the [Component Name]? (Lines 210-212):
- Brief 2-3 sentence overview
- Focus on what it does and key benefits
- Mention Claude Code and component type
Mermaid Diagram (After "What is..." section): Add a simple Mermaid flow diagram (3-4 nodes max):
<!-- Mermaid Diagram -->
<div class="mermaid-diagram" style="background: #1a1a1a; border: 1px solid #333; border-radius: 8px; padding: 2rem; margin: 2rem 0; text-align: center;">
<pre class="mermaid">
graph LR
A[Input/Trigger] --> B[Component Name]
B --> C[Process/Output]
C --> D[Result]
style B fill:#F97316,stroke:#fff,color:#000
</pre>
</div>
Diagram examples by type:
- Agents:
[👤 User Prompt] --> [🤖 Agent Name] --> [⚛️ Code Output] --> [📦 Your Project] - MCPs:
[💻 Claude Code] --> [🔌 MCP Name] --> [📚 Data/Docs] --> [✨ Result] - Skills:
[👤 User Request] --> [🔍 Skill Auto-Triggered] --> [📚 Progressive Loading] --> [✅ Task Complete] - Commands:
[⚙️ Command Call] --> [🔧 Command Logic] --> [📝 Action] --> [✓ Complete] - Hooks:
[📝 Event] --> [🪝 Hook Name] --> [⚡ Automation] --> [✅ Done]
IMPORTANT:
- Avoid using special characters like
/or\inside Mermaid node labels as they cause syntax errors - Skills are NOT slash commands - they activate automatically when relevant to the user's request
Key Capabilities (Lines 214-223):
- Bullet list of 5-7 main capabilities
- Each capability with brief explanation in parentheses
Installation (Lines 225-241):
<h2>Installation</h2>
<p>Install the [Component Name] using the Claude Code Templates CLI:</p>
<pre><code class="language-bash">npx claude-code-templates@latest --[type] [folder/name]</code></pre>
<p><strong>Where is the [type] installed?</strong></p>
<p>The [type] is saved in <code>.claude/[type]s/[name].[extension]</code> in your project directory:</p>
<pre><code class="language-bash">your-project/
├── .claude/
│ └── [type]s/
│ └── [name].[md|json] # ← [Type] installed here
├── src/
│ └── components/
├── package.json
└── README.md</code></pre>
CRITICAL INSTALLATION COMMAND FORMAT:
- Agents:
--agent folder/name(e.g.,--agent development-team/frontend-developer) - MCPs:
--mcp folder/name(e.g.,--mcp devtools/context7) - Commands:
--command folder/name(e.g.,--command setup/ci-cd) - Skills:
--skill name(e.g.,--skill pdf-processing) - Hooks:
--hook folder/name(e.g.,--hook git/auto-commit)
ALWAYS use the FULL path with folder/ - Use find command to verify the correct path first!
How to Use (Lines 243-251):
<h2>How to Use the [Type]</h2>
<p>Start Claude Code and explicitly request the [type] in your prompt:</p>
<pre><code class="language-bash"># Start Claude Code
claude
# Then write your prompt requesting the [type]
> Use the [name] [type] to [example task]</code></pre>
Usage Examples (Lines 253-277): Create 3 practical examples:
<h3>Example 1: [Specific Use Case]</h3>
<pre><code class="language-bash">claude
> Use the [name] [type] to [specific task with details]</code></pre>
<p><strong>Result:</strong> [Expected outcome]</p>
Official Documentation (Lines 276-277):
<h2>Official Documentation</h2>
<p>For more information about [type]s in Claude Code, see the <a href="https://code.claude.com/docs/en/[appropriate-doc-page]?utm_source=aitmpl&utm_medium=referral&utm_campaign=blog" target="_blank">official documentation</a>.</p>
CRITICAL: All URLs to claude.com documentation MUST include UTM parameters: ?utm_source=aitmpl&utm_medium=referral&utm_campaign=blog
Critical Path Requirements:
- Image path (Line 207):
../assets/[blog-id]-cover.png - CSS paths (Lines 62-63):
../../css/styles.css,../../css/blog.css - Navigation links:
../index.htmlfor blog home,../../index.htmlfor main site
Step 5: Update blog-articles.json
Update the temporary entry in docs/blog/blog-articles.json with complete information:
{
"id": "[blog-id]",
"title": "[Component Name] for Claude Code: [Subtitle with Technologies]",
"description": "Complete guide to the [Component Name] - [what it does]. [Key benefits]. [Installation count if available]+ installations.",
"url": "[blog-id]/",
"image": "assets/[blog-id]-cover.png",
"category": "[Component Type Category]",
"publishDate": "[Current Date YYYY-MM-DD]",
"readTime": "4 min read",
"tags": ["Claude Code", "[Type]", "[Tech1]", "[Tech2]", "[Tech3]"],
"difficulty": "basic|intermediate|advanced",
"featured": true,
"order": [next available order number]
}
Category Guidelines:
- Agents → "Agents"
- MCPs → "MCP"
- Skills → "Skills"
- Commands → "Development" or specific category
- Hooks → "Automation"
Difficulty Guidelines:
- basic: Simple to use, no configuration needed
- intermediate: Requires some setup or understanding
- advanced: Complex workflows or configuration
Scripts at End of HTML:
The template already includes ALL required scripts before </body>:
- CodeCopy script (~180 lines) - Adds copy buttons to code blocks
- MarkdownCopier script (~160 lines) - Copy article as Markdown functionality
- Mermaid script (~15 lines) - Diagram rendering support
CRITICAL: These scripts are ALR
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
