structured-output
Format final review deliverables with consistent structure for comparable findings across reviews
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-imbue-structured-outputNight Market Skill — ported from claude-night-market/imbue. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Table of Contents
- When to Use
- Activation Patterns
- Required TodoWrite Items
- Step 1: Select Template (
structured-output:template-selected) - Step 2: Format Findings (
structured-output:findings-formatted) - Step 3: Assign Actions (
structured-output:actions-assigned) - Step 4: Attach Appendix (
structured-output:appendix-attached) - Output Quality Checklist
- Exit Criteria
Structured Output
When To Use
- When finalizing any review or analysis.
- To format findings in a consistent and actionable way.
- Before presenting results to stakeholders or committing them to documentation.
When NOT To Use
- Capturing evidence during analysis - use proof-of-work
- Reviewing changes - use diff-analysis or review-core first
Activation Patterns
Trigger Keywords: format, structure, deliverable, report, organize, present, consistent Contextual Cues:
- "format this as a report" or "structure the output"
- "create a deliverable" or "present these findings"
- "organize this consistently" or "standardize the format"
- "make this actionable" or "prepare for stakeholders"
Auto-Load When: Finalizing any analysis deliverable or when consistent formatting is requested.
Required TodoWrite Items
structured-output:template-selectedstructured-output:findings-formattedstructured-output:actions-assignedstructured-output:appendix-attached
Mark each item complete as you finish the corresponding step.
Step 1: Select Template (structured-output:template-selected)
- Choose output format based on deliverable type:
- Review Report: Summary, Findings, Recommendations, Evidence.
- PR Description: Summary, Changes, Test Plan, Notes.
- Release Notes: Highlights, Breaking Changes, Fixes, Credits.
- Incident Report: Timeline, Impact, Root Cause, Remediation.
- Confirm audience and required detail level.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-imbue-structured-output": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
synthesize
>- Merge, deduplicate, rank, and format research findings from multiple channels into a coherent report. Use after research agents return their results
workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure