analyze

Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

Quality

84%

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

81%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-structured orchestration skill with a clear, validated workflow and good delegation to specialized skills. Its main weakness is that the core 'Analyze' step is abstract and lacks executable code, though that is partly expected for an instruction-style skill.

Suggestions

Tighten the 'Analyze' step with concrete heuristics (e.g., specific decomposition patterns or example sub-question breakdowns) to lift actionability past 4.

Trim or merge the 'Tips' section, which reiterates guidance already covered in the workflow, to improve conciseness.

Make the CONNECTORS.md reference more prominent than a blockquote aside, or move it into the relevant 'Gather Data' step where connected tools are first needed.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no over-explanation of concepts Claude already knows (no primers on SQL or data warehouses); the 'Tips' section partially reiterates the workflow, a minor trim opportunity that fits anchor 4.	4 / 5
Actionability	Provides concrete guidance via a named validation checklist (row count, null, magnitude, trend continuity, aggregation logic), explicit fallback paths, and per-complexity output formats; the 'Analyze' step stays abstract ('Identify patterns, trends, outliers') and no executable code is given, placing it just above the midpoint rather than at 5.	4 / 5
Workflow Clarity	A clearly sequenced 6-step process with an explicit validation checkpoint (Step 4) and feedback loops (query fails -> debug/retry; unexpected results -> sanity checks; concern -> investigate), matching anchor 5; the workflow is read-only analysis so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Well-organized into clear sections and appropriately delegates detail to one-level-deep references (sql-queries and data-visualization skills, CONNECTORS.md) rather than inlining them; no bundle files exist, and signaling is clear with only minor organization gaps, fitting anchor 4.	4 / 5
	Total	17 / 20 Passed

Description

83%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 clearly states both capability and explicit trigger conditions with natural phrasing. It is comprehensive on the 'when' side and concrete on actions, with only minor gaps in keyword synonyms and a slight overlap risk with adjacent analysis skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report') but frames them at a scenario level rather than as a comprehensive enumeration, fitting anchor 4.	4 / 5
Completeness	Explicitly answers both 'what' ('Answer data questions -- from quick lookups to full analyses') and 'when' ('Use when...') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('looking up a single metric', 'what's driving a trend or drop', 'comparing segments over time', 'data report'); good coverage but missing common synonyms like 'query' or 'dashboard', so not a 5.	4 / 5
Distinctiveness Conflict Risk	A clear data-analysis niche with distinct triggers (trend/drop investigation, segment comparison, formal report); minor overlap risk with general BI/analysis skills keeps it at 4 rather than 5.	4 / 5
	Total	17 / 20 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: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: anthropics/knowledge-work-plugins
Path: data/skills/analyze/SKILL.md
Commit: 8444efc

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