claude-blog

A Claude Code skill ecosystem (Python) that provides many blog-focused commands to generate, optimize, audit, and manage content at scale. It includes SEO/quality scoring, citation/fact-checking support, editorial planning (briefs/calendars/strategy), media helpers (SVG charts and Gemini-based images/audio), and optional integrations such as Google APIs and CMS taxonomy management.

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ Ai Ml ai-ml blog seo claude-code-skill python content-optimization citations fact-checking cms-integration
⚙ Agent Friendliness
45
/ 100
Can an agent use this?
🔒 Security
53
/ 100
Is it safe for agents?
⚡ Reliability
36
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
70
Error Messages
0
Auth Simplicity
55
Rate Limits
25

🔒 Security

TLS Enforcement
70
Auth Strength
60
Scope Granularity
35
Dep. Hygiene
55
Secret Handling
45

The tool integrates with third-party APIs (Google, Gemini, CMS) using API keys/OAuth (reported at a high level). The provided content does not describe how secrets are stored/loaded, whether they are redacted in logs, or whether strict scope minimization is enforced. Dependency hygiene is not verifiable from the provided snippet; common libraries (requests, google-api-python-client, jsonschema, spacy, etc.) are used, but no vulnerability/CVE policy or lockfile review is shown.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
50
Error Recovery
40
AF Security Reliability

Best When

You are using Claude Code and want an extensible set of blog-production and optimization workflows (generation, auditing, schema/media helpers) with optional Google/CMS integrations.

Avoid When

You require a documented public REST/GraphQL API with stable contract and SDKs for programmatic access by non-CLI systems.

Use Cases

  • Generate new blog posts from a topic with structured outputs (outline/brief/article/schema).
  • Rewrite and optimize existing posts (SEO checks, quality audit, schema/geo/citation readiness).
  • Plan content calendars and ideate topics/strategy per niche.
  • Create/validate JSON-LD schema markup and repurpose content for other channels.
  • Run audits across a directory/site (health assessment, keyword cannibalization detection, fact-checking).
  • Generate visual assets (SVG charts) and optionally generate images/audio via Gemini.
  • Use Google APIs for SEO/insights tasks (PSI/CrUX/GSC/GA4/NLP/YouTube keywords).
  • Manage taxonomy/tags in supported CMS platforms via their APIs.

Not For

  • A traditional web service API for serving content over HTTP to other applications.
  • Use as a fully offline/on-prem tool without any external API dependencies (Google/Gemini/CMS).
  • Use where strict data residency/compliance guarantees are required (not specified).
  • Use where you need robust, standardized API error codes/pagination semantics (it is CLI/skill-based).

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: Google API key (Tier 0) for some Google endpoints. OAuth for Google Search Console / Indexing APIs (Tier 1). CMS credentials for WordPress/Shopify/Ghost/Strapi/Sanity integrations (per configured endpoints). Optional Gemini credentials for image generation and Gemini TTS for audio (requires Google AI API key per README).
OAuth: Yes Scopes: No

Auth is primarily via user-supplied credentials/config for third-party services (Google APIs, CMS providers, Gemini). The README mentions OAuth at a high level for Google Search Console/Indexing, but does not specify OAuth scope granularity or a consistent credential interface format in the provided content.

Pricing

Free tier: Yes
Requires CC: No

The project itself is MIT-licensed and installable; external services (Google APIs, Gemini, CMS APIs) may incur usage-based costs depending on provider quotas/plans. No project-level pricing tiers are described.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • This is a Claude Code skill/command ecosystem rather than a standard network API; an agent must operate through the CLI/Claude Code command interface.
  • Many commands depend on external credentials (Google, CMS, Gemini). Failures may be due to missing/invalid credentials or quota limits.
  • Operations that modify or generate content (write/rewrite/calendar/taxonomy sync) may not be idempotent unless explicitly designed that way (not evidenced in provided content).
  • Rate limiting/quota handling is not clearly documented in the provided README.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for claude-blog.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

6475
Packages Evaluated
19928
Need Evaluation
586
Need Re-evaluation
Community Powered