Agent skill

Structured Output

Formats review deliverables with consistent structure for comparable findings.

MITAuto-check passedAI & LLM Engineering

Install Structured Output

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/imbue/skills/structured-output .claude/skills/structured-output && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .claude/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/imbue/skills/structured-output .agents/skills/structured-output && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .agents/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/imbue/skills/structured-output .cursor/skills/structured-output && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .cursor/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/athola/claude-night-market.git --path plugins/imbue/skills/structured-output

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/imbue/skills/structured-output .gemini/skills/structured-output && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .gemini/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/imbue/skills/structured-output .github/skills/structured-output && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .github/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add athola/claude-night-market --skill structured-output -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install athola/claude-night-market structured-output --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/imbue/skills/structured-output .opencode/skills/structured-output && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "structured-output" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/imbue/skills/structured-output into .opencode/skills/structured-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-output", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: structured-output
GitHub stars: 342
Token cost: ~1.2k tokens
SKILL.md length: 407 words
Files: 1
Skills in repo: 159
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Formats review deliverables with consistent structure for comparable findings.

Works in 4 steps: Select Template… → Format Findings… → Assign Actions… → …
Finalizing any review
SKILL.md covers When To Use, When NOT To Use, Activation Patterns and Required TodoWrite Items, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Structured Output is an agent skill from athola/claude-night-market. Formats review deliverables with consistent structure for comparable findings. Use when finalizing any review or analysis that must be shared or compared.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Structured output and tool calling. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.

When your agent uses it

Finalizing any review
Analysis that must be shared

Example prompts

“Use the structured-output skill to format review deliverables with consistent structure for comparable findings”
“/structured-output”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Select Template (structured-output:template-selected)
Format Findings (structured-output:findings-formatted)
Assign Actions (structured-output:actions-assigned)
Attach Appendix (structured-output:appendix-attached)

What it can do on your machine

Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Structured Output loads about 1.2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 407 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 407 words, ~1,191 tokens.

Download SKILL.mdSave it as .claude/skills/structured-output/SKILL.md (or your agent's skills folder).

name: structured-output
description: Formats review deliverables with consistent structure for comparable findings. Use when finalizing any review or analysis that must be shared or compared.
alwaysApply: false
category: output-patterns
tags: formatting, deliverables, consistency, reporting, structure
dependencies: imbue:proof-of-work
usage_patterns: deliverable-formatting, report-structure, consistent-output
complexity: beginner
model_hint: fast
estimated_tokens: 1000

Structured Output

When To Use

When finalizing any review or analysis.
To format findings in a consistent way that names specific next steps.
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-selected
structured-output:findings-formatted
structured-output:actions-assigned
structured-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.

Step 2: Format Findings (`structured-output:findings-formatted`)

Use consistent finding structure:

markdown

### [SEVERITY] Finding Title
**Location**: file.rs:123
**Anchor**: `verbatim source text copied from line 123`
**Category**: Security | Performance | Correctness | Style
**Description**: Brief explanation of the issue.
**Evidence**: [E1, E2] - Reference to evidence log.
**Recommendation**: Specific remediation steps.

Verification: Run the command with --help flag to verify availability.

Severity levels: CRITICAL, HIGH, MEDIUM, LOW, INFO.
Order findings by severity, then by file location.
Anchor is mandatory and grounds the finding. Copy the exact source text at Location (not a paraphrase). It is what a second pass re-reads to confirm the finding is real. A finding whose anchor does not appear at its cited line is treated as a hallucination and dropped. The check is mechanical: imbue:review-core Step 5 runs plugins/imbue/scripts/citation_verifier.py over the findings.

Show full SKILL.md (195 more words)Show less

Step 3: Assign Actions (`structured-output:actions-assigned`)

Convert findings to action items with assignee and priority:

markdown

## Action Items
- [ ] [HIGH] Fix SQL injection in auth.py:45 (@security-team, P1)
- [ ] [MEDIUM] Add input validation to API endpoint (@backend, P2)
- [ ] [LOW] Update deprecated dependency (@devops, P3)

Verification: Run the command with --help flag to verify availability.

Include owner assignment where known.
Add priority indicators (P1/P2/P3) for triage.
Note dependencies between actions.

Step 4: Attach Appendix (`structured-output:appendix-attached`)

Compile supporting materials:

markdown

## Appendix
### A. Commands Run
[Full evidence log from imbue:proof-of-work]

### B. External References
[Citations and documentation links]

### C. Raw Data
[Large outputs, full diffs, or data exports]

Verification: Run the command with --help flag to verify availability.

Keep main report concise; details in appendix.
validate appendix is navigable with clear section headers.

Output Quality Checklist

Before finalizing:

Every finding carries a verbatim Anchor the citation verifier resolved (no unverified findings ship).
All findings have evidence references.
Severity levels are justified.
Recommendations are specific and name the next step.
No orphaned sections or placeholder text.
Format renders correctly in target medium (GitHub, Confluence, etc.).

Exit Criteria

Todos completed with formatted deliverable.
Output follows selected template structure.
Stakeholders can act on findings without clarification.

Files

Just SKILL.md in plugins/imbue/skills/structured-output of athola/claude-night-market.

Open the folder on GitHubat commit 9f3eb00

Compare with similar skills

Structured Output next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Structured Output compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Structured Output this skillathola/claude-night-market	342	—	~1.2k	Automated safety check: Pass	MIT	2 days ago
Planning With Filesjarrodwatts/claude-code-config	1.1k	5 repos	~967	Automated safety check: Pass	None	8 mo ago
Tool Use Data Synthesissunny-glow/Auto-BenchMax	1.3k	—	~3.3k	Automated safety check: Pass	None	2 mo ago
Agent Harness ConstructionKartikLabhshetwar/mind-mentor	147	7 repos	~500	Automated safety check: Pass	Apache-2.0	4 mo ago
Prompt Engineering Patternswshobson/agents	40k	—	~1.3k	Automated safety check: Pass	MIT	3 days ago
Model Benchmarkstheopenco/llmgateway	1.7k	—	~1.1k	Automated safety check: Notes	Custom licence	today

Similar skills

Planning With Files
jarrodwatts/claude-code-config
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.
1.1k GitHub starsUsed in 5 repos~967 tokens
AI & LLM EngineeringAuto-check passed
Tool Use Data Synthesis
sunny-glow/Auto-BenchMax
Synthesize training data for ANY tool-use / agentic benchmark, in ANY repo.
1.3k GitHub stars~3.3k tokensUpdated 2 mo ago
AI & LLM EngineeringAuto-check passed
Agent Harness Construction
KartikLabhshetwar/mind-mentor
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
147 GitHub starsUsed in 7 repos~500 tokens
AI & LLM EngineeringAuto-check passed
Prompt Engineering Patterns
wshobson/agents
Reference for designing and tuning production LLM prompts: few-shot examples, chain-of-thought, structured outputs, templates and system prompts.
40k GitHub stars~1.3k tokensUpdated 3 days ago
AI & LLM EngineeringAuto-check passed
Model Benchmarks
theopenco/llmgateway
Run and report repository model or provider-mapping benchmarks.
1.7k GitHub stars~1.1k tokensUpdated today
AI & LLM EngineeringAuto-check: notes
Agent Prompt Quality Bar
mastra-ai/mastra
Universal quality bar and final audit rubric for any agent system prompt.
29k GitHub stars~2k tokensUpdated today
AI & LLM EngineeringAuto-check passed

Questions about Structured Output

What does Structured Output do?

Formats review deliverables with consistent structure for comparable findings. Structured Output is an agent skill from athola/claude-night-market. Formats review deliverables with consistent structure for comparable findings.

When should I use Structured Output?

Structured Output fits situations like: finalizing any review; analysis that must be shared.

How do I install Structured Output in Claude Code?

Run `npx skills add athola/claude-night-market --skill structured-output -a claude-code`. Or copy the skill folder (plugins/imbue/skills/structured-output in athola/claude-night-market) into .claude/skills/structured-output in your project. Claude Code loads it when a task matches its description.

How do I install Structured Output in Codex?

Run `npx skills add athola/claude-night-market --skill structured-output -a codex`. Or copy the skill folder (plugins/imbue/skills/structured-output in athola/claude-night-market) into .agents/skills/structured-output in your project. Codex loads it when a task matches its description.

Can I use Structured Output in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill structured-output -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/structured-output, .gemini/skills/structured-output, .github/skills/structured-output and .opencode/skills/structured-output in your project.

What does Structured Output need to run?

SKILL.md names no scripts, command-line tools or credentials: Structured Output is instructions for the agent only.

Does Structured Output access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Structured Output safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Structured Output use?

Structured Output is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Structured Output use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Structured Output?

Skills that share tags, products or a category with Structured Output: Planning With Files (jarrodwatts/claude-code-config, 1.1k stars), Tool Use Data Synthesis (sunny-glow/Auto-BenchMax, 1.3k stars), Agent Harness Construction (KartikLabhshetwar/mind-mentor, 147 stars) and Prompt Engineering Patterns (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Structured Output?

athola (a GitHub user) maintains it in athola/claude-night-market, which has 342 GitHub stars. The repository holds 159 skills in this directory. The repository was last updated on October 6, 2026.

Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Structured Output

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Structured Output

When To Use

When NOT 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

Files

Compare with similar skills

Similar skills

More from athola/claude-night-market

Related

Questions about Structured Output

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`)