Claude Blog
AI-powered blog skill suite: 32 skill directories (1 orchestrator + 31 sub-skills) and 5 agents to write, rewrite, audit, and optimize content for Google ran...
Claude Blog is an open-source Claude Code marketplace collection in Image Creation. It bundles 32 skills, 0 slash commands, and 20 subagents to extend Claude Code with verified install commands and live GitHub tracking.
How to Install & Test
Official Claude Code installation commands generated from verified marketplace manifests.
Local Script Execution
This plugin runs shell scripts or local binaries on your computer. Review the code repository before installing.
What this plugin can run:
- 32 contextual agent skill(s)
- 20 dedicated subagent(s)
Installation Time: Running Claude Code marketplace commands resolves dependencies, AST verification, and hooks. This usually takes 10–30 seconds. Wait for the CLI confirmation before proceeding.
Run these slash commands inside your Claude Code interactive session:
Registers the author's plugin catalog with your Claude Code client:
/plugin marketplace add AgriciDaniel/claude-blog
Installs the package into your chosen scope (user, project, or local):
/plugin marketplace add AgriciDaniel/claude-blog
Reloads active plugins in your session without exiting:
/reload-plugins
Test or inspect the plugin locally using official Claude Code CLI commands:
git clone https://github.com/AgriciDaniel/claude-blog.git
Loads the local plugin into this terminal session only:
claude --plugin-dir ./
claude plugin validate ./
claude plugin install ./
Copy this audit-and-install prompt and paste it into Claude Code or your AI coding assistant:
Please inspect the Claude Code marketplace at https://github.com/AgriciDaniel/claude-blog. 1. Read the manifest (.claude-plugin/plugin.json or marketplace.json) and scan components (commands, skills, agents, hooks, and .mcp.json). 2. Summarize every hook lifecycle event, script, command, and external MCP server it defines. 3. Verify whether it requests API keys or accesses sensitive local paths. 4. Ask for my confirmation. Once approved, run: /plugin marketplace add AgriciDaniel/claude-blog /plugin marketplace add AgriciDaniel/claude-blog /reload-plugins
What's Inside This Package
Components declared in the plugin tree: skills, slash commands, dedicated subagents, lifecycle hooks, and MCP servers.
Agent Skills (32)
Specialized Subagents (20)
Overview & Documentation
Claude Blog — AI-powered blog skill suite: 32 skill directories (1 orchestrator + 31 sub-skills) and 5 agents to write, rewrite, audit, and optimize content for Google rankings and AI citations (GEO/AEO). Includes the FLOW framework, topic clusters, multilingual publishing, Google API integration, personas, fact-checking, NotebookLM research, Gemini TTS narration, image generation, and 100-point scoring.
Includes 32 skills, 20 agents.
Add the marketplace with /plugin marketplace add AgriciDaniel/claude-blog, then install any of its 2 plugins with /plugin install <name>@agricidaniel-blog.
Source: AgriciDaniel/claude-blog (2800 GitHub stars as of 2026-11-18).
Frequently Asked Questions
Answers to common questions regarding Claude Blog compatibility, safety, and configuration.
Frequently Asked Questions
Direct answers to common questions about using these skills and tools.
How do I install Claude Blog in Claude Code?
Add the marketplace via "/plugin marketplace add AgriciDaniel/claude-blog", then run "/plugin install claude-blog@agricidaniel-blog". Finally, run "/reload-plugins" to activate the package in your current session.
What capabilities and components are included inside Claude Blog?
Claude Blog bundles 32 contextual skills, 0 custom commands, 20 subagents, no event hooks, and 0 external MCP server connections.
Is Claude Blog safe to run on my machine?
This package is classified as "runs-scripts" risk. It runs locally without unauthorized elevation. Always inspect the code before installing.
How do I test Claude Blog locally without permanent installation?
Clone the repository and run "claude --plugin-dir ./". This loads the plugin strictly for the active terminal session without changing your global settings.