Installation

Open Claude Code and run this command:

/plugin install publishing-skills@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

Four composable, platform-aware skills for a governed editorial pipeline:

Skill	Responsibility
`blog-topic-research`	Finds current, traceable demand and rejects weak or duplicate topic ideas.
`blog-editorial-calendar`	Balances the backlog, reserves work, schedules approved drafts, and reconciles CMS state.
`seo-blog-writer`	Researches and drafts one source-grounded article, validates its bundle, and hands it to an approved adapter.
`blog-figure-svg`	Produces accessible, static SVG figures and optional reviewed PNG renders from supported article evidence.

The skills default to read-only research or local draft creation. Scheduling, CMS writes, live publication, destructive replacement, new software installation, and credential use remain explicit owner-approved actions.

Skills (4) plugin-local skills

blog-editorial-calendar View full skill →

Operate an evidence-backed editorial queue, balance topic and format coverage, schedule approved drafts, and reconcile backlog state with the publishing system.

ReadWebSearchWebFetchWriteEdit

Editorial Calendar Operations

Overview

Maintain a durable editorial backlog and select the next work from evidence rather than intuition. This skill balances configured topic clusters and post formats, reserves publishing slots, and reconciles local state with the real CMS before changing the queue.

It coordinates blog-topic-research and seo-blog-writer; it does not replace their research, drafting, review, or publishing controls.

Prerequisites

An approved config.json defining target_platform, author, UTC cadence, cluster targets, format targets, and CMS tag mappings
A writable backlog.json with stable IDs, titles, clusters, formats, evidence URLs, priorities, statuses, and scheduled timestamps
Read-only CMS listing access for sync; separate approved write access only when the user requests scheduling or publication
blog-topic-research for backlog replenishment and seo-blog-writer for draft production
Topic and format target weights that each total approximately 1.0

Tool Discipline

Use Read to inspect configuration and backlog state. Use WebSearch and WebFetch only to confirm public evidence or read the authorized CMS inventory. Use Write or Edit for reviewed, secretless state updates; never write credentials, raw access tokens, or unpublished sensitive content into receipts.

Instructions

Parse the requested action: status, next, add, mark-done, or sync. Reject unknown actions and mutually incompatible scheduling flags.
Read and validate config.json and backlog.json. Confirm unique IDs, valid statuses, parseable UTC timestamps, nonnegative priorities, and target weights near 1.0.
Run a read-only reconciliation before selection. Match CMS records by stable CMS ID first, canonical URL second, and normalized slug only as a last resort. Report ambiguous matches instead of guessing.
For next, score only eligible ready items. Rank cluster deficit first, then format deficit, evidence strength, explicit priority, and oldest creation time. Record the score factors so the choice is reproducible.
Reserve the selected item with a stable run ID. For --draft, invoke the writer without a publish time. Otherwise choose the next free configured UTC slot or validate each explicit slot.
Require review before any live publish or schedule mutation. Pass the topic scaffold and approved target to seo-blog-writer; do not copy CMS credentials into the handoff.
Commit the state transition only after the downstream operation returns a durable draft …

blog-figure-svg View full skill →

Design accessible, source-backed SVG editorial figures and optionally rasterize reviewed assets for a blog or CMS.

ReadWriteEditBash(command:*)Bash(magick:*)Bash(identify:*)Bash(rsvg-convert:*)Bash(inkscape:*)Bash(python3:*)

Accessible Editorial SVG Figures

Overview

Create lightweight editorial artwork whose visual claims are traceable to the approved article or source data. Supported shapes are process flows, comparison bars, taxonomies, terminal mocks, and 1600x840 feature cards.

The editable SVG is the source of truth. PNG rasterization is optional, and CMS upload remains a separate approved action.

Prerequisites

Final or near-final article copy with the intended anchor paragraph
Approved title, caption, data points, source URLs, brand palette, and output directory
A writable local draft directory such as tmp/blog-drafts/
For PNG output, one installed rasterizer: ImageMagick, rsvg-convert, Inkscape, or CairoSVG
Optional pngquant or oxipng for lossless or reviewed lossy compression

Tool Discipline

Use Read to inspect the approved article and brand tokens. Use Write or Edit for local SVG, caption, and receipt files. The scoped Bash commands may only detect or invoke the named local renderers and Python validator; never interpolate untrusted titles, SVG fragments, filenames, or shell arguments.

Instructions

Identify the single information structure to communicate. Choose flow for ordered steps, compare for sourced numeric values, taxonomy for categories, terminal for verified command output, or feature for a title card.
Extract the exact facts from the approved source. Record a URL or article anchor for every number, quote, product claim, and terminal line. Omit unsupported content.
Create a safe kebab-case filename, refuse parent traversal or absolute output paths, and avoid overwriting an existing asset unless the owner approves.
Lay out the figure on a responsive SVG viewBox. Use text elements rather than embedded fonts, preserve readable contrast, and keep labels legible at the target display width.
Add a unique <title> and <desc>, then connect them with role="img" and aria-labelledby. Decorative shapes should not add noise to the accessibility tree.
Keep the SVG self-contained: no scripts, event handlers, remote images, external stylesheets, foreignObject, or unreviewed embedded data.
Validate the XML and scan for forbidden active content. Review clipping, reading order, contrast, label accuracy, and source correspondence.
If PNG output is requested, choose an installed rasterizer, pass fully quoted local paths, render at the required dimensions, and verify the output type and dimensions.
Compress only after preserving the SVG source. Compare before/after dimensions and file …

blog-topic-research View full skill →

Build a deduplicated editorial backlog from current, traceable demand and authoritative product evidence.

ReadWebSearchWebFetchWriteEdit

Evidence-Backed Blog Topic Research

Overview

Find specific editorial opportunities supported by real user questions and current primary sources. Each accepted topic includes an evidence trail, search intent, version context, known-answer status, and duplicate-risk decision.

This workflow does not invent search volume or treat autocomplete as proof of commercial value. It separates observed demand from editorial judgment.

Prerequisites

Target audience, product or subject boundary, business goal, locale, and preferred language
Existing titles, canonical URLs, slugs, and planned backlog for cannibalization checks
Approved topic clusters and formats, if the publication uses a taxonomy
Current access to public search results, official documentation, changelogs, issue trackers, and relevant community sources
A requested count between 1 and 100; default to 25 when omitted

Tool Discipline

Use Read for the supplied inventory and taxonomy. Use WebSearch to discover candidate questions and WebFetch to verify the actual source page, date, title, and context. Use Write or Edit only after the user approves backlog changes; do not store private community data, credentials, or unnecessary personal information.

Instructions

Confirm scope, audience, locale, time horizon, count, excluded subjects, and the publication's definition of a useful conversion or reader outcome.
Read the existing coverage inventory. Normalize case, punctuation, product names, versions, error codes, and canonical URLs while preserving the original titles.
Search across at least three suitable signal classes: official docs or changelogs, public issue trackers, vendor forums, Stack Overflow, Reddit, or visible search suggestions. Respect access controls and site terms.
Fetch each candidate source. Capture its title, URL, publication or update date when available, exact short evidence excerpt, source type, and whether it is primary or community evidence.
Pair demand evidence with at least one current authoritative source whenever the topic makes product, API, version, legal, medical, financial, performance, or pricing claims.
Classify search intent and format: how-to-fix, how-to-connect, how-to-automate, x-vs-y, what-is, use-case, listicle, migration, or release-recap.
Score evidence explicitly. Use 1 for a single relevant public mention, 2 for repeated or engaged discussion, and 3 for strong repeated demand across independent sources. Label this an editorial signal score, never search volume.
Run duplicate checks against published and planned coverage. Reject a matching …

seo-blog-writer View full skill →

Research, draft, validate, and hand off one source-grounded long-tail article through an approved CMS or static-site adapter.

ReadWebSearchWebFetchWriteEditBash(python3:*)

Source-Grounded SEO Blog Writer

Overview

Turn one approved long-tail topic into a reviewable article bundle: research notes, clean draft, metadata, structured-data recommendations, link inventory, and an adapter handoff. The default is local draft output; live publication is never inferred.

Optimize for reader usefulness and accurate extraction, not keyword stuffing or synthetic authority. Structured data must describe visible page content and does not guarantee rankings or AI citations.

Prerequisites

A specific topic, intended reader, search intent, locale, brand voice, and review owner
Current first-party sources plus independent sources where comparison or risk claims need them
Existing site inventory for internal links and cannibalization checks
A writable local draft directory
For CMS delivery, an approved target and credentials supplied through environment variables or the platform's secret store
For optional local validation scripts, Python 3 and dependencies already approved by the owner

Tool Discipline

Use Read to inspect the editorial brief, brand guidance, and existing coverage. Use WebSearch for discovery and WebFetch to verify current sources. Use Write or Edit for local draft artifacts. The scoped Bash(python3:*) authority is only for reviewed local validation and approved adapter scripts with quoted paths and environment-provided credentials; never echo secrets or place them in prompts, URLs, drafts, fixtures, logs, or receipts.

Instructions

Parse the topic and flags. Reject an empty or overly broad topic. Default to --target static --draft; treat --publish and --publish-at as explicit, mutually exclusive owner instructions.
Check existing titles, slugs, canonical URLs, and intent. Stop or narrow the angle when the proposed post would cannibalize existing coverage.
Research the topic with current sources. For each material claim, record URL, publisher, date, retrieval date, supported statement, and confidence. Prefer official documentation for product behavior and primary data for numbers.
Define the reader's problem, desired outcome, exclusions, format, and claim boundary before drafting. Do not invent metrics, quotes, prices, versions, customer stories, or observed results.
Build an outline that answers the primary question early, then supports it with logically ordered sections. Headings should describe reader tasks or decisions, not mechanically repeat keywords.
Draft in the approved voice. Distinguish fact from inference, date volatile claims, use code only when tested or clearly labeled illustrative, and include limitations where a reasonable reader could be misled.
Add internal links only when they im…

publishing-skills

Installation

What It Does

Skills (4) plugin-local skills

Editorial Calendar Operations

Overview

Prerequisites

Tool Discipline

Instructions

Accessible Editorial SVG Figures

Overview

Prerequisites

Tool Discipline

Instructions

Evidence-Backed Blog Topic Research

Overview

Prerequisites

Tool Discipline

Instructions

Source-Grounded SEO Blog Writer

Overview

Prerequisites

Tool Discipline

Instructions

Ready to use publishing-skills?

Related Plugins

publishing-skills

Installation

What It Does

Skills (4) plugin-local skills

Editorial Calendar Operations

Overview

Prerequisites

Tool Discipline

Instructions

Accessible Editorial SVG Figures

Overview

Prerequisites

Tool Discipline

Instructions

Evidence-Backed Blog Topic Research

Overview

Prerequisites

Tool Discipline

Instructions

Source-Grounded SEO Blog Writer

Overview

Prerequisites

Tool Discipline

Instructions

Ready to use publishing-skills?

Related Plugins

000-jeremy-content-consistency-validator

002-jeremy-yaml-master-agent

003-jeremy-vertex-ai-media-master

004-jeremy-google-cloud-agent-sdk

agent-context-manager

ai-commit-gen