Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add namnh06/astro-seo-blog
Or install specific skill: npx add-skill https://github.com/namnh06/astro-seo-blog
# Description
Write an SEO-optimized blog post for any Astro website. Use when the user wants to create a new blog post, write content for the blog, or mentions "blog post," "SEO content," "write article," or "create blog." Reads BLOG_CONFIG.yaml from project root for business-specific settings and applies universal Google Search Central best practices.
# SKILL.md
name: astro-seo-blog
description: Write an SEO-optimized blog post for any Astro website. Use when the user wants to create a new blog post, write content for the blog, or mentions "blog post," "SEO content," "write article," or "create blog." Reads BLOG_CONFIG.yaml from project root for business-specific settings and applies universal Google Search Central best practices.
license: MIT
compatibility: Designed for Claude Code (or similar products)
metadata:
author: namnh
version: "1.0"
Write SEO-Optimized Astro Blog Post
Write an SEO-optimized blog post about $ARGUMENTS for an Astro website.
Workflow
- Read
BLOG_CONFIG.yamlin the project root - Scan the blog directory to avoid duplicate topics and find related posts
- Apply SEO best practices from references/seo-guidelines.md
- Use the appropriate template from references/templates/
- Write the blog post file to the blog directory
Quick Reference
| Requirement | Value |
|---|---|
| Word count | 1,000-2,000 words |
| Internal links | 6-8 minimum |
| Location mentions | 3-5 times |
| Title length | 50-60 characters |
| Meta description | 150-160 characters |
Configuration
The BLOG_CONFIG.yaml file in the project root contains:
- Business info (name, location, industry)
- Services with URLs (for internal linking)
- Target keywords
- Astro structure type (content collections vs standalone)
- CTA templates
If no config exists, ask the user to create one from assets/blog-config-template.yaml.
Critical Rules
- Date: Always check system date. Content Collections use
YYYY-MM-DD; standalone usesYYYY-MM-DDTHH:MM:SS[timezone](timezone from config). - Title: 50-60 characters, include primary keyword and location.
- Meta description: 150-160 characters.
- Word count: 1,000-2,000 words.
- Internal links: 6-8 minimum (2-3 service pages, 3-4 blog posts, 1-2 homepage/contact).
- Location mentions: 3-5 times, naturally integrated.
- Heading hierarchy: Single H1, H2 for sections, H3 for subsections, never skip levels.
- Standalone template: Every H2 needs a matching entry in the
headingsarray with exactidmatch;titlein BlogLayout props includes site name suffix (Post Title | Business Name).
Additional Resources
- For complete SEO guidelines, see references/seo-guidelines.md
- For Astro file templates, see references/templates/
- For example output, see references/examples/
# README.md
astro-seo-blog
A Claude Code skill that generates SEO-optimized blog posts for Astro websites. It reads your site's configuration, applies Google Search Central best practices, and writes publish-ready blog posts directly into your project.
Usage
/astro-seo-blog [topic]
Examples:
/astro-seo-blog best winter home maintenance tips
/astro-seo-blog how to choose a family dentist
Setup
-
Install the skill — Place this folder in
~/.claude/skills/astro-seo-blog/ -
Add a config to your project — Copy
assets/blog-config-template.yamlto your Astro project root asBLOG_CONFIG.yamland fill in your business details, services, keywords, and Astro structure type. -
Run it — Open Claude Code in your Astro project and use
/astro-seo-blog [topic].
What It Does
- Reads
BLOG_CONFIG.yamlfrom your project root for business-specific context - Scans existing posts to avoid duplicate topics and find related content to link
- Detects your Astro structure (Content Collections or standalone
.astrofiles) - Applies the matching template and SEO guidelines
- Writes a complete blog post file to your configured blog directory
SEO Standards
Each generated post follows these requirements:
| Requirement | Target |
|---|---|
| Word count | 1,000–2,000 |
| Title length | 50–60 characters |
| Meta description | 150–160 characters |
| Internal links | 6–8 minimum |
| Location mentions | 3–5 |
| Heading hierarchy | Single H1, proper H2/H3 nesting |
Content follows E-E-A-T principles (Experience, Expertise, Authoritativeness, Trustworthiness) and Google Search Central guidelines.
Supported Astro Structures
- Content Collections — Markdown files in
src/content/blog/with YAML frontmatter - Standalone —
.astrocomponent files insrc/pages/blog/with exported metadata andBlogLayoutwrapper
Set astro_structure.type in your BLOG_CONFIG.yaml to content_collections or standalone.
File Structure
astro-seo-blog/
├── SKILL.md # Skill definition and instructions
├── assets/
│ └── blog-config-template.yaml # Template to copy into your project
└── references/
├── seo-guidelines.md # Full SEO rules and quality checklist
├── templates/
│ ├── content-collections.md # Markdown post template
│ └── standalone-astro.md # .astro file template
└── examples/
└── sample-post.md # Example output
Configuration Reference
BLOG_CONFIG.yaml sections:
- business — Name, location, industry, local references
- author — Name, title, credentials, bio
- services — Service pages with URLs and keywords (used for internal linking)
- keywords — Primary, secondary, and long-tail target keywords
- pages — Internal linking targets (homepage, contact, about, etc.)
- astro_structure — Structure type, blog directory, file extension, timezone
- frontmatter — Required/optional fields and custom fields
- content — Word count range, location mention targets, linking minimums
- cta_template — Call-to-action section template
- existing_topics — Previously covered topics to avoid duplication
See assets/blog-config-template.yaml for the full template with comments.
This skill follows the Agent Skills specification.
License
MIT
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.