---
id: "framework-skill-methodology"
type: "framework"
source_timestamps: ["10:42:00", "11:55:00"]
tags: ["prompt-engineering", "best-practices"]
related: ["concept-methodology-body", "claim-linear-skills-brittle", "action-document-edge-cases"]
steps: ["\"Reasoning: Provide frameworks", "quality criteria", "and principles", "not just linear steps.\"", "\"Output Format: Explicitly specify the exact format (Markdown", "PDF", "specific fields) the skill must return.\"", "Edge Cases: Document the exceptions and nuances that humans handle via common sense.", "Examples: Provide pattern-matching references so the LLM knows what a successful output looks like.", "Lean Constraints: Keep the skill file concise (under 150 lines) to avoid context bloat and instruction confusion."]
sources: ["s43-file-format-agreement"]
sourceVaultSlug: "s43-file-format-agreement"
originDay: 43
---
# The 5-Part Skill Methodology Framework

## Purpose

A structural framework for writing the methodology section of a `skill.md` file. By moving beyond simple step-by-step instructions and including reasoning, strict output contracts, documented edge cases, and examples — while keeping the overall file lean — creators can build robust skills that agents can execute reliably without human intervention.

## The 5 Steps

### 1. Reasoning

Provide **frameworks, quality criteria, and principles**, not just linear steps. The LLM should understand *why* something is good, not just *how* to do it. Counters [[claim-linear-skills-brittle]].

### 2. Output Format

Explicitly specify the exact format (Markdown, PDF, specific fields, JSON schema) the skill must return. This is the [[concept-skills-as-contracts]] principle in action.

### 3. Edge Cases

Document the exceptions and nuances that humans handle via common sense. The LLM will not guess them. See [[action-document-edge-cases]].

### 4. Examples

Provide **pattern-matching references** so the LLM knows what a successful output looks like. Few-shot examples beat abstract description.

### 5. Lean Constraints

Keep the skill file concise — ideally **under 150 lines**. Bloat degrades performance by 10–20% in some agent evals due to context dilution and instruction conflict.

## Related

- [[concept-methodology-body]]
- [[concept-skill-anatomy]]
- [[contrarian-linear-steps-fail]]