Prompt Master + Prompting 101 — Afilador de Prompts

Transform vague requests into structured prompts with explicit output contracts.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/laboratoriolegalcontable-png/stack-ia-creador --skill prompt-master-prompting-101-afilador-de-prompts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Prompt Master + Prompting 101 — Afilador de Prompts
Source: https://github.com/laboratoriolegalcontable-png/stack-ia-creador/tree/main/.claude/skills/prompt-master
Command: npx skills add https://github.com/laboratoriolegalcontable-png/stack-ia-creador --skill prompt-master-prompting-101-afilador-de-prompts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague or under-specified requests into high-precision prompts with explicit structure, constraints, and output contracts, reducing failed outputs and iteration cycles.

Core Features & Use Cases

  • 9-dimensión intent extraction: identifica silenciosamente tarea, tool target, formato de salida, restricciones, inputs, contexto, audiencia, criterios de éxito y ejemplos.
  • 10-pilar Anthropic prompting: construye prompts por capas (system cacheables + user-specific instructions) para mejorar consistencia y parseabilidad.
  • Prompt audit y anti-patrones: detecta fallas típicas (output sin formato, tool incorrecto, criterios de éxito ausentes, agent scope abierto) y guía la corrección.
  • Flujo v1→v5: evoluciona prompts desde mínima tarea hasta versión lista para producción con reglas, ejemplos y formato.

Quick Start

Ask the AI to audit your prompt for missing target tool, output format, constraints, and success criteria, then rewrite it using the Prompt Master v1→v5 structure.

Frequently Asked Questions about Prompt Master + Prompting 101 — Afilador de Prompts

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

FAQPage Schema
How do I write better LLM prompts that produce consistent and parseable outputs?

To write better LLM prompts, you must transform vague requests into structured instructions with explicit output formats, constraints, and success criteria. This approach reduces failed generations and iteration cycles by ensuring the model understands exact requirements.

Why does my LLM workflow return inconsistent outputs without a defined format?

Your LLM workflow returns inconsistent outputs because the prompt lacks an explicit output contract and defined constraints. Applying a layered structure with target-tool mapping and anti-pattern detection enforces parseable, predictable results across multi-step tasks.

How do I audit an existing prompt for missing constraints and anti-patterns?

To audit an existing prompt, check for missing target tool specifications, absent output formats, undefined constraints, and missing success criteria. Detecting these anti-patterns and applying layered prompting pillars guides the necessary structural corrections.

What is the best way to structure prompts for multi-step text and agent workflows?

The best way to structure prompts for multi-step workflows is using a layered approach with cacheable system instructions and user-specific tasks. Extracting intent dimensions like audience, context, and success criteria ensures the agent scope remains controlled and effective.

Can I evolve a basic prompt into a production-ready instruction set?

Yes, you can evolve a basic prompt into a production-ready instruction set using a v1 to v5 flow. This iterative construction process progressively adds explicit rules, examples, and strict formatting constraints to achieve high-precision results.

When do I need to specify a target tool in my prompt engineering process?

You need to specify a target tool in your prompt engineering process whenever your workflow involves multi-step tasks or agent integrations. Mapping the target tool prevents open agent scope failures and ensures the output matches the required technical format.