Maintainer of this skill?
Automated security scan — not a certification.
by AgriciDaniel
Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at AI-Marketing-Hub/claude-blog (AI Marketing Hub Pro community); public releases ship here.
# Add to your Claude Code skills
git clone https://github.com/AgriciDaniel/claude-blogLast scanned: 5/8/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-08T05:59:19.934Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": false
}See how claude-blog compares with popular alternatives.
claude-blog is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by AgriciDaniel. Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at AI-Marketing-Hub/claude-blog (AI Marketing Hub Pro community); public releases ship here. It has 2,393 GitHub stars.
Yes. claude-blog passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/AgriciDaniel/claude-blog" and add it to your Claude Code skills directory (see the Installation section above).
claude-blog is primarily written in Python. It is open-source under AgriciDaniel on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude-blog against similar tools.
No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
claude-blog)claude-blog is a Claude Code skill suite that writes, optimizes, audits, localizes, and refreshes blog content at scale. Every article is evaluated for Google-aligned usefulness and internal AI citation readiness heuristics. Version 2.3.1 was prepared on 2026-10-13.
The core promise is simple: the user is never the first reviewer. A 5-gate Blog Delivery Contract scores every draft against a 100-point rubric, blocks delivery below 90, verifies artifacts and links, and iterates up to 3 times before escalation.
This is the public, MIT-licensed distribution at
AgriciDaniel/claude-blog.
The publishing workflow is documented in
docs/PUBLISHING.md.
Blog: See how claude-blog works
Watch the original demo on YouTube.
claude-blog is a full-lifecycle blog engine for strategy, briefs, outlines, writing, rewriting, analysis, schema, AI citation readiness, site audits, topic clusters, multilingual publishing, audio narration, and content decay detection.
Current v2.3.1 shape: 32 skill directories = 1 orchestrator + 31 sub-skills; 30 user-facing /blog commands (blog-chart is internal, not a command). It also includes 5 specialized agents, repository consistency and public-release validators, 22 core references, 12 templates, a pytest suite (run python3 -m pytest --collect-only -q | tail -1 for the current count), and the bundled Claude Blog Brain at ./brain.
Every draft ships as an artifact folder with the markdown source, rendered HTML, PDF, real hero.<ext>, 3 viewport screenshots, review.md, and preflight-report.json. The renderer uses XSS-safe JSON-LD handling, dark-mode-aware CSS, and the same source for every output format.
Solo bloggers and creators can ship high-quality posts without spending hours on SEO, schema, source checks, and internal linking.
Marketing teams and agencies can run consistent multi-post workflows across brands, languages, authors, and platforms with /blog cluster, /blog multilingual, /blog persona, /blog brand, and /blog discourse.
Claude Code skill builders can study a layered Agent Skills architecture (a directive layer of SKILL.md files, an orchestration layer of one routing skill plus agents, and an execution layer of scripts) with orchestrator routing, sub-skill dispatch, agent handoffs, code-enforced delivery gates, installer hardening, and CI coherence checks.
Most user-installable Claude Code skill plugins should ship to ~/.claude/skills/<name>/ for skill content, ~/.claude/agents/<name>.md for agents, and ~/.claude/scripts/<helper>.py for Python helpers.
This answer is intentionally kept in the README because it demonstrates the GEO and SEO writing pattern claude-blog produces: answer-first summary, explicit paths, source-ready structure, and a compact FAQ-ready section that AI systems can quote without extra context.
A condensed specimen of a generated article:
---
title: "Where Should a Claude Code Skill Plugin Install Itself?"
description: "A working answer to the install-path question..."
date: "2026-05-18"
author: "Daniel Agrici"
tags: [claude-code, skills, plugins, installation]
canonical: "https://example.com/blog/skill-plugin-install-path"
---
## Where Should a Claude Code Skill Plugin Install Itself?
The short answer: most user-installable Claude Code skill plugins
should ship to `~/.claude/skills/<name>/` for skill content,
`~/.claude/agents/<name>.md` for agents, and
`~/.claude/scripts/<helper>.py` for any Python helpers.
### Key Takeaways
- `~/.claude/skills/` is the SKILL.md surface area.
- `~/.claude/agents/` holds agent markdown files.
- The full article includes sourced citations, FAQ, and schema JSON-LD.
The orchestrator in skills/blog/SKILL.md parses /blog input, detects the target platform, loads only the references it needs, routes to a sub-skill, and coordinates agents plus scripts through the delivery contract.
| Layer | Count | Where |
|---|---|---|
| Skill directories | 32 | skills/blog plus skills/blog-* |
| Orchestrator | 1 | skills/blog/SKILL.md |
| Sub-skills | 31 | skills/blog-*/SKILL.md |
User-facing /blog commands |
30 | skills/blog/SKILL.md routing table |
| Internal-only sub-skill | 1 | skills/blog-chart/SKILL.md |
| Specialized agents | 5 | agents/blog-*.md |
| Root scripts | 22 | scripts/*.py |
| References | 22 | skills/blog/references/*.md |
| Templates | 12 | skills/blog/templates/*.md |
| Tests | pytest suite | tests/ (python3 -m pytest --collect-only -q | tail -1 for the count) |
More architecture detail lives in docs/ARCHITECTURE.md.
Every /blog write and /blog rewrite result must pass the delivery contract before it is shown to the user.
| Gate | Enforces | Implementation |
|---|---|---|
| 1. Capability Discovery | Required tools, agents, env vars, and optional dependencies are known before writing | scripts/blog_preflight.py --gate 1 |
| 2. Format Completeness | .md, .html, .pdf, and a real hero image exist and are valid: no leftover [IMAGE], [CHART] or [INTERNAL-LINK] markers, slug-style filenames, hero decodes and is at least 1200x630, PDF opens with at least one page, the HTML's blog-source-sha256 matches the .md, and static HTML checks (lang, title, meta description, one H1, heading order, og tags, no noindex, alt text, no active content) |
scripts/blog_render.py, scripts/generate_hero.py, scripts/blog_preflight.py |
| 3. Visual Verification | Screenshots render at 375, 768, and 1280 widths, JSON-LD is valid, dark mode holds, SVGs do not overflow, no hidden article text | patchright or playwright |
| 4. Content Review | blog-reviewer score is 90+ with zero P0 issues, a matching nonce, and no change to the draft after the nonce was issued (a stale review is a violation) |
agents/blog-reviewer.md |
| 5. Asset and Link Integrity | Images resolve, og:image exists, links satisfy the verified URL policy, word count matches schema within 5% |
scripts/blog_preflight.py --gate 5 |
The order is fixed: draft, resolve markers and visuals, render, issue the review nonce, review, run the gates, and re-render, re-issue and re-review after any edit (maximum 3 iterations). The renderer's own footer link is checked for its scheme only, so a fully local article can pass Gate 5 offline; external links need network access, and a failure there may be a network or DNS problem rather than a dead link. The review nonce stops accidents and casual forgery; it does not stop a process running as the same user that can read its state file. The full sequence and every check live in one place: skills/blog/references/blog-delivery-contract.md.
Hero image ladder: Banana MCP, direct Gemini API, premium stock APIs, then Openverse. First working source wins. The ladder is specified in the same contract.