winston-prompt-normalization

Scan Winston prompt docs, classify prompts, and update skill contracts and routing references.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/paulmalmquist/Consulting_app --skill winston-prompt-normalization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winston-prompt-normalization
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/skills/winston-prompt-normalization
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill winston-prompt-normalization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize Winston meta prompts into durable skills. It automates scanning Winston prompt docs, deciding which prompts should become skills, and creating or updating the normalized skill plus routing docs.

Core Features & Use Cases

  • Scan Winston prompt documentation to identify candidate prompts for skill conversion.
  • Classify prompts into convert-to-skill, keep-as-reference, or archive statuses, and generate or adjust routing and instruction references.
  • Create or update the durable skill contract, including the working rules, load order, and exit conditions, while keeping long implementation details in reference materials.
  • Update repository documentation such as CLAUDE.md and docs/instruction-index.md to reflect the new or revised skill and its routing.

Quick Start

Scan the Winston prompt docs, determine which prompts should become skills, and create or update the normalized skill plus routing docs.

Frequently Asked Questions about winston-prompt-normalization

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

FAQPage Schema
How do I normalize meta prompts into actionable skills?

Meta prompt normalization scans your prompt documentation to identify candidates, then generates a durable skill contract and updates routing references. This workflow preserves long implementation details in reference docs while updating the main instruction index.

What is the process for classifying prompts to decide which become durable skills?

Prompt classification involves scanning documentation and assigning each prompt to convert-to-skill, keep-as-reference, or archive statuses. This process determines whether a prompt gets a durable skill contract or remains stored as reference material.

How do I update routing and instruction references after creating a new skill?

Updating routing and instruction references requires adjusting the durable skill contract, including working rules and exit conditions, then reflecting the changes in CLAUDE.md and docs/instruction-index.md to ensure repository readiness and accurate routing.

Does prompt normalization require updating CLAUDE.md and the instruction index?

Prompt normalization requires updating CLAUDE.md and docs/instruction-index.md to reflect the new or revised skill. These repository documentation updates validate routing readiness and ensure the instruction index accurately maps the normalized skill.

What is the best way to handle long implementation details when converting prompts to skills?

Handling long implementation details involves preserving them in reference materials rather than the main skill contract. Keep the durable skill contract focused on working rules, load order, and exit conditions while storing extended details separately.