skills.rest
oletizi
oletiziCOMMUNITY
Explore all skills by this author →
GitHub

editorial-publish

Automates editorial calendar publishing by updating statuses and closing GitHub issues.

Updated Jan 25, 2026
Search Tags:#automation#publish#blog-posts#github-issues#editorial-calendar#content-workflow#calendar-management
One-click install
npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: editorial-publish
Source: https://github.com/oletizi/audiocontrol.org/tree/main/.claude/skills/editorial-publish
Command: npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the publishing workflow for editorial entries by marking them Published on the current date and closing their linked GitHub issues, reducing manual steps and ensuring consistency across sites.

Core Features & Use Cases

  • Site resolution and calendar integration: Determines the target site, reads the daily/weekly editorial calendar, and locates the entry by slug.
  • Content-type aware publishing: Enforces URL requirements for non-blog content and validates blog post existence for blog entries.
  • Workflow automation: Updates the calendar, assigns the publication date, and closes the associated GitHub issue if linked.
  • Use Case: A content editor publishes a scsi-protocol-deep-dive article, automatically updates the calendar to Published, and closes the corresponding issue.

Quick Start

Publish an entry by slug using /editorial-publish scsi-protocol-deep-dive.

Frequently Asked Questions about editorial-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate publishing editorial calendar entries and closing GitHub issues?▼

You can automate editorial calendar publishing by invoking the Skill with a content slug, which marks the entry Published on the current date and auto-closes linked GitHub issues.

What's the best way to publish a blog post from an editorial calendar?▼

Publishing a blog post from an editorial calendar requires passing the entry slug to the Skill, which validates blog post existence, updates the calendar state to Published, and closes the associated issue.

Does editorial publishing require URL validation for non-blog content?▼

Yes, editorial publishing enforces URL requirements for non-blog content types, ensuring proper URL validation before marking the editorial calendar entry as Published.

Can I close GitHub issues automatically when content is published?▼

Yes, you can close GitHub issues automatically during the publishing workflow if a GitHub issue is linked to the editorial calendar entry being marked Published.

How does site resolution work for editorial calendar publishing?▼

Site resolution determines the target site, reads the daily or weekly editorial calendar, and locates the entry by slug before applying the Published state and closing linked issues.

What are the limitations of automated editorial calendar publishing?▼

Automated editorial calendar publishing is limited to entries with valid slugs; non-blog content must pass URL validation, and GitHub issue closure only occurs when an issue is explicitly linked.

Related Skills

Explore More Content & Communication Skills→
oletizioletizi

editorial-status

Read editorial calendar files and group entries by workflow stage.

Community
Intermediate
ThalesGroupThalesGroup
19

docs-publish-github-pages

Inspect and patch GitHub Pages docs publishing workflows.

Official
Advanced
truchottruchot
2

content-management

Coordinates editorial content workflows across teams, tools, and multi-language sites.

Community
Advanced
Terry-MaoTerry-Mao
144

update-dedupe

Analyze GitHub issue closure patterns to propose deduplication guidance updates.

Community
Advanced