trace-to-skill-converter

Convert workflow traces into reusable Skill definitions with deterministic extraction and LLM naming.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill trace-to-skill-converter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace-to-skill-converter
Source: https://github.com/WesleyMFrederick/cc-workflows-plugin/tree/main/src-claude/skills/trace-to-skill-converter
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill trace-to-skill-converter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts completed workflow traces into reusable, testable Skill definitions by extracting structured data deterministically and delegating semantic naming to an LLM, enabling repeatable skill generation from traces.

Core Features & Use Cases

  • Deterministic extraction: parse traces to structured JSON without any LLM involvement.
  • Semantic synthesis: an LLM derives the skill name, description, and instructions from the extracted data.
  • End-to-end workflow: phase 1 extraction, phase 2 synthesis, phase 3 assembly+eval with governance gates.
  • Use case: transform a project trace into a ready-to-publish Skill.md for reuse across teams.

Quick Start

Run the trace-to-skill converter on a trace markdown file to generate a draft SKILL.md that can be reviewed and finalized.

Frequently Asked Questions about trace-to-skill-converter

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

FAQPage Schema
How do I convert a workflow trace into a reusable skill definition?

To convert a workflow trace into a reusable skill definition, run the trace-to-skill converter on a markdown trace file. It deterministically extracts structured data and delegates semantic naming to an LLM to generate a draft SKILL.md.

How does deterministic extraction from process trees and artifacts work?

Deterministic extraction parses traces, including process trees and artifacts, into structured JSON without LLM involvement. This ensures repeatable, structured data generation before the LLM derives semantic names and instructions.

What is the best way to automate skill generation from completed project traces?

The best way to automate skill generation from project traces is using a phased workflow that separates deterministic extraction, LLM synthesis, and architecture evaluation with governance gates, ensuring repeatable and testable skill outputs.

Do I need a valid SKILL.md frontmatter to generate a draft skill from a trace?

Yes, a valid SKILL.md frontmatter is required to generate a draft skill from a trace. The converter uses this frontmatter to output a JSON contract for phase 2 synthesis and subsequent architecture evaluation.

Can I use workflow traces with phased sections to create testable skills?

Yes, you can use workflow traces with optional process trees, artifacts, and phased sections to create testable skills. The converter applies deterministic extraction to diverse trace structures to enable repeatable skill generation across projects.

Why does the trace-to-skill conversion process delegate architecture evaluation to a sub-agent?

The conversion process delegates architecture evaluation to a sub-agent during the assembly and evaluation phase. This ensures the generated skill meets governance gates and quality standards before finalizing the SKILL.md for team reuse.