structured-outputs

Use this skill when you need Claude to return structured JSON — data extraction, classification, form parsing, or any task needing machine-readable output.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, code-first skill that gives fully executable examples for each technique and a clear selection table. It is lean and assumes Claude's competence; the main room for improvement is trimming the docstrings/schema block and adding an explicit validation note for parsing robustness.

Suggestions

Tighten the one-line docstrings and consider moving the INVOICE_SCHEMA example to a collapsible/secondary position to push conciseness toward the lean anchor.

Add a brief note that prefill/system-prompt output may need `json.loads` error handling (a validate-then-retry loop) to strengthen workflow clarity for the less reliable methods.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence with the anthropic SDK and Python, with no padding about basic concepts; the per-method docstrings and the 'Common Extraction Schemas' block add minor over-explanation that could be trimmed, keeping it just below the fully-lean anchor.	4 / 5
Actionability	Every method is given as complete, copy-paste-ready executable Python with real function signatures and worked example calls showing expected return values, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The three methods are presented as a clear choose-one decision with 'Choose based on complexity' and a Quick Reference table ranking reliability and best-fit use; the selection logic is explicit, though there is no explicit validation/checkpoint feedback loop, so it sits below the top anchor rather than at it.	4 / 5
Progressive Disclosure	This is a single-purpose skill needing no external bundle files (references/scripts/assets absent) and is organized into clean labeled sections (Overview, Method 1-3, Common Schemas, Quick Reference), so per the simple-skills note it reaches the well-organized anchor without separate file references.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that explicitly covers both what the skill does and when to use it, with multiple concrete actions and natural trigger terms. Its only weakness is slightly less than comprehensive keyword/synonym coverage.

Suggestions

Add a few common synonyms to the trigger list (e.g., 'JSON schema', 'tool use', 'API responses') to broaden keyword coverage toward the comprehensive anchor.

Consider naming the recommended technique inline (e.g., 'via tool use, prefilling, or system-prompt instruction') so the description previews the skill's distinct approach.

Dimension	Reasoning	Score
Specificity	Names the domain (structured JSON) and lists several concrete actions — 'data extraction, classification, form parsing, or any task needing machine-readable output' — with only minor coverage gaps, matching the 'several specific actions' anchor and falling short of the comprehensive anchor above.	4 / 5
Completeness	Explicitly answers both what ('return structured JSON — data extraction, classification, form parsing, or any task needing machine-readable output') and when ('Use this skill when you need Claude to return structured JSON... or any task needing machine-readable output') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('structured JSON', 'data extraction', 'classification', 'form parsing', 'machine-readable output') with a 'Use when' trigger, but misses some common synonyms like 'JSON schema' or 'tool use' that would reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (machine-readable JSON output) with distinct, specific triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ProwlrBot/prowlr-marketplace
Path: external/anthropic-official/structured-outputs/SKILL.md
Commit: 32f0050

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.