Format Output
This skill allows the agent to transform any raw content, analysis result, or synthesis into a polished, audience-appropriate deliverable. It handles format conversion, tone calibration, and structure selection based on the consumer of the output.
Steps
- Identify the target audience. Who receives this output?
Agent→ machine-readable YAML/JSON, strict schemaDeveloper→ markdown with code blocks, technical precisionBusiness stakeholder→ executive summary, plain language, key metrics firstSystem file→ format dictated by the file's schema contract
- Select the output format. Based on audience:
- Structured data: YAML, JSON
- Prose document: markdown with proper heading hierarchy
- Tabular: markdown table or CSV
- Briefing: numbered list of key points + recommendation
- Calibrate tone.
Technical→ precise, minimal prose, examples preferredExecutive→ high-level, outcome-focused, no jargonInstructional→ step-by-step, imperative voice, clear prerequisites
- Apply format standards.
- Single H1 per document
- Code blocks for all commands/code
- Alerts/callouts for warnings
- Tables for comparative data
- Write the formatted output.
- Self-check. Is the format correct for the audience? Is the tone consistent? Is all content accurate?
- Output the final formatted artifact.
Format Reference
| Audience | Preferred Format | Tone |
|---|---|---|
| Agent/System | YAML or JSON | Strict schema |
| Developer | Markdown + code blocks | Technical |
| Business/Exec | Prose + bullet summary | Plain, outcome-first |
| End User | Step-by-step tutorial | Instructional |
| Archive/Log | Markdown with metadata | Neutral, precise |
Notes
- Never guess the audience — derive it from context or ask if unclear.
- Format conversion does not change content — if something is wrong in the raw input, fix it before formatting, not during.
- Pair with
validationtoolbox to verify structured output conforms to schema before delivery.