report

Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

Quality

83%

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

85%Weight 40%Scale 1-3

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

The body is a well-structured, actionable instruction set with a clear single-committing-action workflow and concrete embed/table formats. The main weakness is mild redundancy in restating the inspect-before-commit ordering.

Suggestions

Consolidate the repeated 'inspect first, then call write_report' guidance into one authoritative statement to save tokens.

Move the one redundant restatement in 'Write the report' to a brief cross-reference back to 'Emitting the report'.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'inspect first, then call write_report' ordering is restated three or more times, which could be tightened. Not 3 because of that redundancy; not 1 because there is no padded concept exposition.	2 / 3
Actionability	Concrete tool names, the exact embed syntax '![caption](chart://chart_id)' with a worked example, the exact 'report' argument, and a markdown table example give copy-paste-ready guidance rather than pseudocode.	3 / 3
Workflow Clarity	A clear sequence (inspect -> produce charts -> compose -> commit via write_report) with an unambiguous committing action and a pre-write verification step ('Read the charts behind the key findings…before you compose'); no validate-retry loop is needed since this is not a destructive or batch operation.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the self-contained guidance is organized into clear one-level (## / ###) sections with no nested file references, avoiding a monolithic wall of text.	3 / 3
	Total	11 / 12 Passed

Description

82%Weight 40%Scale 1-3

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

The description is specific and trigger-rich, clearly conveying what the skill produces across many report forms. Its only gap is the absence of an explicit 'when to use' trigger clause within the description field itself (the skill's separate when_to_use field covers that, but the rubric scores the description field).

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks to write up, summarize, or report on an exploration they've done.'

Consider folding a condensed version of the when_to_use trigger terms into the description so the 'when' is answered in-field.

Dimension	Reasoning	Score
Specificity	Enumerates concrete deliverables ('note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report') plus a concrete action ('with embedded charts'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is clearly answered, but the description field itself contains no explicit 'Use when…' trigger clause, so per the rubric guideline completeness is capped at 2. It is not 1 because the capability is unambiguous.	2 / 3
Trigger Term Quality	'report', 'note', 'blog post', 'executive summary', 'KPI dashboard', 'slide brief', and 'charts' are natural phrases a user would say, giving good coverage rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	'Turn an exploration (threads, findings, charts) into a single Markdown report' carves a clear niche unlikely to trigger for unrelated skills, rather than overlapping with generic writing skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: microsoft/data-formulator
Path: py-src/data_formulator/analyst/skills/report/SKILL.md
Commit: 5d4f7b3

Reviewed: 8 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.