sync-artifact-scale

Create and mirror Markdown artifacts with YAML frontmatter to the ai-blogs workbench.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/eugene-belkovich/ai-setup --skill sync-artifact-scale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-artifact-scale
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/claude/profiles/work/skills/workflow/sync-artifact-scale
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill sync-artifact-scale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Keeps Markdown deliverables from being orphaned by automatically generating the required frontmatter and mirroring them to the ai-blogs workbench so artifacts are visible and organized.

Core Features & Use Cases

  • Auto-derives metadata (author, source, repo, branch, session) from your Git context and a feature slug.
  • Writes a local copy under docs/plans and a mirrored copy under content/workbench (organized by repo/project/section).
  • Validates required fields and normalizes tags to ensure consistent searchability and discovery.
  • Use case: after finishing a plan in docs/plans, run the tool to publish a front-matted artifact and automatically mirror it into the workbench for collaboration.

Quick Start

Run the sync_artifact.py script with your artifact details to publish and mirror the Markdown deliverable to the workbench.

Frequently Asked Questions about sync-artifact-scale

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

FAQPage Schema
How do I automatically add YAML frontmatter to Markdown files and sync them to a workbench?

To automatically add YAML frontmatter and sync Markdown files, this tool validates required metadata fields and mirrors your deliverables to the ai-blogs workbench. It auto-derives provenance data from your Git context to ensure artifacts remain visible and organized.

Why do my Markdown deliverables in docs/plans get orphaned and lose their provenance metadata?

Markdown deliverables get orphaned without standardized frontmatter capturing author, source, and session data. This tool solves that by automatically generating required YAML fields from your Git context and mirroring the artifacts to the workbench.

What is the best way to keep Markdown artifacts organized by repository and section in a workbench?

The best way to keep Markdown artifacts organized is to mirror them into structured project and section paths. This tool automatically derives repository and session data from Git, writing mirrored copies to the workbench under organized directory structures.

Can I auto-derive author and repository metadata from Git for my Markdown frontmatter?

Yes, you can auto-derive author, source, repo, and branch metadata directly from your Git context. The tool extracts this provenance information automatically and writes it into the required YAML frontmatter fields of your Markdown artifacts.

Do I need to manually normalize tags and frontmatter fields before publishing Markdown artifacts?

No, you do not need to manually normalize tags or validate frontmatter fields. The tool enforces required fields and automatically normalizes tags to ensure consistent searchability and discovery across the mirrored workbench artifacts.

How do I sync a Markdown artifact to the workbench after finishing a plan in docs/plans?

To sync a Markdown artifact after finishing a plan, run the sync_artifact.py script with your artifact details. It will generate the required frontmatter, write a local copy under docs/plans, and publish a mirrored copy to the workbench.