agentsclimarketplace

Workflow to skill converter

Skill alexzhu0/agent-skill-radar/starters/workflow-to-skill-converter

Evidence-backed topic radar for choosing what Agent Skill to build next.

Install
npx -y skills add alexzhu0/agent-skill-radar --skill workflow-to-skill-converter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this when a stable workflow exists and should become a triggerable `SKILL.md`.

SKILL.md

1.2 KB, 244 tokens by cl100k_base, as published. Nobody here has run it

Workflow To Skill Converter

Purpose

Convert one clear workflow into a compact, reusable SKILL.md with trigger, inputs, and output shape.

Fit

  • Use when a workflow happens repeatedly and is currently only in chat notes or docs.
  • Do not use when the request is one-off advice with no repeat value.

Inputs

  • A stable workflow or playbook.
  • Trigger phrase, scope boundaries, and expected outcome.
  • Examples of failure cases or missing details.

Workflow

  1. Capture the core objective in one sentence.
  2. List required inputs and optional inputs.
  3. Define trigger phrase and anti-trigger conditions.
  4. Write required output sections from this repo's card style.
  5. Add a short missing-data and validation section.

Output

Produce:

  • SKILL.md with frontmatter fields: name, description.
  • Purpose, Fit, Inputs, Workflow, Output, and Validation.
  • Clear do-not-use boundaries.

Validation

  • Output is short enough to paste into an agent instruction file.
  • Scope is one workflow, not a full platform migration.
  • At least one concrete missing-data item is included.

Gives 0 of the 12 instructions most automation workflows skills give in 244 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

  • write conventional commit messagesin 36 of 745, across 35 files
  • delete branches after mergein 30 of 745, across 21 files
  • make atomic commitsin 25 of 745, across 15 files
  • write minimal code to pass testsin 22 of 745, across 10 files
  • run tests before committingin 21 of 745, across 13 files
  • re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • use try-catch for error handlingin 20 of 745, across 6 files
  • write tests before implementationin 20 of 745, across 8 files
  • configure branch protection rulesin 19 of 745, across 5 files
  • explain the why in commit messagesin 19 of 745, across 9 files
  • refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • capture the core objective in one sentence
  • list required inputs and optional inputs
  • define trigger phrase and anti-trigger conditions
  • write required output sections from the card style
  • add a short missing-data and validation section
  • include frontmatter fields name and description

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.