publish_skill

Overview

This skill publishes completed blog drafts by updating metadata, renaming files, and moving them into the Archives folder. It streamlines turning a draft in Projects/ into a published post under Archives/ with proper status and date fields.

How this skill works

The skill inspects draft files in Projects/development-blog/ and Projects/hobby-blog/, verifies content readiness, and updates front matter to set status: published and add the published date. It removes any draft prefix from filenames, prepends a YYYY-MM identifier, creates target Archives folders if missing, and moves the file into the appropriate Archives subfolder.

When to use it

• When a blog draft in Projects/ is complete and ready to go live
• When you need to standardize metadata and filenames before publishing
• When archiving published posts by month and category
• When automating repetitive publish-and-move steps for many posts

Best practices

• Confirm the draft content is final before running the publish action
• Ensure front matter contains created date so published metadata remains accurate
• Use a clear draft prefix like "draft-" to enable safe renaming
• Verify tags and categories are set before publishing to avoid post-editing
• Keep consistent folder names: development-blog and hobby-blog under both Projects and Archives

Example use cases

• Batch publishing multiple completed drafts at month end into Archives with YYYY-MM prefixes
• Automated pipeline hooking: on manual approval, update front matter to published and move file to Archives
• Cleaning up a hobby blog: rename and archive finished hobby drafts into Archives/hobby-blog/