skill-authoring-workflow

Convert workshop notes into compliant SKILL.md assets with metadata validation.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill skill-authoring-workflow-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring-workflow
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/skill-authoring-workflow
Command: npx skills add https://github.com/ch-m-n/dotfile --skill skill-authoring-workflow-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow clears the chaos of turning rough workshop notes or half-baked prompts into compliant SKILL.md assets by enforcing repo standards, metadata limits, and catalog updates before a skill is published.

Core Features & Use Cases

  • Dogfood First toolkit: Leverage the repo scripts for finding, adding, building, testing, and checking skills so every step follows the same trusted automation.
  • Definition of Done guardrails: Follow a fixed order of sections, validate frontmatter (name, description, intent, type), respect metadata limits, resolve cross-references, and keep README counts accurate.
  • Use Case: When a PM has workshop notes for a new interactive advisor, run the guided workflow to decide on a component type, tighten prose, run metadata checks, and integrate the new skill into the catalog without breaking standards.

Quick Start

Ask the skill to convert your draft notes into a compliant skill authoring checklist that follows the repo workflow.

Frequently Asked Questions about skill-authoring-workflow

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

FAQPage Schema
How do I convert workshop notes into compliant skill metadata for publishing?

To convert workshop notes into compliant skill metadata, run a guided workflow that transforms raw prompts into publish-ready assets by enforcing repo standards, validating frontmatter, and tightening prose before committing.

What is the process for validating skill metadata limits before a repo commit?

Validating skill metadata limits involves running repo scripts to check frontmatter fields like name, description, intent, and type, ensuring cross-references resolve correctly and README counts stay accurate before committing changes.

How do I choose the right component type when creating a new repo skill?

Choosing the right component type when creating a repo skill requires following a guided workflow that evaluates your draft notes, applies definition of done guardrails, and maps the content to the correct build path for catalog integration.

Can I use repo scripts to build and test skill authoring workflows?

Yes, you can use repo scripts to find, add, build, test, and check skills, ensuring every authoring step follows trusted automation to package workflows for Claude uploads without breaking standards.

Why does my skill authoring workflow fail repo standards validation?

Skill authoring workflows fail repo standards validation when the fixed order of sections is ignored, frontmatter metadata limits are exceeded, or cross-references and README counts are not resolved and updated correctly before publishing.

Do I need partial prompts to generate a compliant skill authoring checklist?

You need raw workshop notes or partial prompts to generate a compliant skill authoring checklist, which the workflow transforms into a step-by-step guide that enforces metadata limits and repo standards for Claude uploads.