agentsclimarketplace

Micro pipeline

Skill stevesolun/micro-skills/micro-skill-pipeline/skills/micro-pipeline

Stop writing 200-line skills that Claude skims. Convert any skill into a gated micro-pipeline with hard YES/NO quality checks.

Install
npx -y skills add stevesolun/micro-skills --skill micro-pipeline

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

  • 10 stars10 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

Gated micro-skill pipeline system. Auto-triggers when building, generating, or creating any multi-step output (documents, code, presentations, reports). Enforces a Scope-Plan-Build-Check-Deliver pipeline where each step has a pass/fail gate. Use this whenever the output quality matters and the task has more than one component.

SKILL.md

1.5 KB, as published. Nobody here has run it

Micro-Skill Pipeline

When this skill triggers, execute the following gated pipeline. One step at a time. Do NOT skip ahead.

Pipeline

  1. Scope -- Read references/01-scope.md. Extract constraints from the request.
  2. Plan -- Read references/02-plan.md. Design the approach. Map components.
  3. Build -- Read references/03-build.md. Execute with micro-checks per component.
  4. Check -- Read references/04-check.md. Answer every gate question YES or NO. Any NO = fix before proceeding.
  5. Deliver -- Read references/05-deliver.md. Finalize and present output.

Failure Log

Look for a failure-log.md in the current project root or skill directory. If it exists, read it before starting. Every listed pattern is a mandatory check constraint.

Rules

  • Read each reference file when you reach that step, not all at once.
  • Step 4 (Check) is the hard gate. "Mostly yes" counts as NO.
  • On Check failure: fix, re-run full checklist, then append a one-line pattern to failure-log.md.
  • For simple single-component tasks, collapse Scope+Plan into one step but never skip Check.

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.