agntcms-publish-draft

Publish draft web pages via a specified endpoint with versioning and git commits.

Updated May 29, 2026

Search Tags:#content management #draft management #web publishing #git operations #endpoint integration

Ready to run

npx skills add https://github.com/AlexHramovich/fr-preview-migration --skill agntcms-publish-draft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agntcms-publish-draft
Source: https://github.com/AlexHramovich/fr-preview-migration/tree/main/.claude/skills/publish-draft
Command: npx skills add https://github.com/AlexHramovich/fr-preview-migration --skill agntcms-publish-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of publishing draft pages, reducing manual steps and ensuring consistency in the workflow.

Core Features & Use Cases

Automated Publishing: Publishes draft pages with a single command, ensuring the draft is moved to the live site correctly.
Endpoint Utilization: Calls the publish endpoint to handle file movement, versioning, and git commits.
Error Handling: Reports errors clearly and does not retry without user instruction, maintaining the integrity of the content history.

Quick Start

Use the agntcms-publish-draft skill to publish a draft page with the command: publish-draft <slug>

Frequently Asked Questions about agntcms-publish-draft

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

FAQPage Schema

How do I automate publishing draft web pages with a single command?▼

Automating draft web page publishing involves interfacing with a publish endpoint to handle file transfer, versioning, and git commits. This Skill triggers that process using a valid slug to identify the draft for automated live deployment.

What is the best way to move a draft page to a live site while maintaining git versioning?▼

Publishing draft pages through a dedicated endpoint ensures the draft is moved to the live site correctly while automatically handling file movement, versioning, and commits to the repository for content history integrity.

Do I need a specific identifier to publish a draft page through an endpoint?▼

Publishing a draft page requires a valid slug to identify the specific draft. The Skill utilizes this slug when calling the native HTTP tool to interact with the publish endpoint and execute the file transfer.

How does error handling work if the draft publishing process fails?▼

Error handling for draft publishing reports errors clearly and does not retry without explicit user instruction. This approach maintains the integrity of the content history by avoiding unintended duplicate git commits or file movements.

Can I use this to manage content versioning and web publishing simultaneously?▼

Managing content versioning and web publishing simultaneously is supported by interfacing with a publish endpoint. The endpoint handles both the file transfer to the live site and the corresponding git commits for version control.

What happens to my repository commits when I publish a draft?▼

When publishing a draft, the publish endpoint automatically handles commits to the repository. This ensures that the versioning and file movement are executed correctly, maintaining a consistent content history without manual git operations.