data-analyst

Data Analyst Agent. 데이터 분석, 리포트, 대시보드 작성을 담당합니다.

Quality

35%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/data-analyst/SKILL.md

Quality

Discovery

32%

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

This description provides a basic overview of the skill's domain but lacks the specificity and explicit trigger guidance needed for effective skill selection. The Korean language description names general capabilities but doesn't include concrete actions, file types, or a 'Use when...' clause that would help Claude distinguish this skill from others in a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'analyze data', 'create dashboard', 'generate report', 'visualize', 'statistics', 'CSV', 'Excel'

List specific concrete actions such as 'create pivot tables', 'generate charts', 'calculate statistics', 'build visualizations' instead of general categories

Include file type triggers (.csv, .xlsx, .json) and common user phrases to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (data analysis) and lists some actions (데이터 분석, 리포트, 대시보드 작성 - data analysis, reports, dashboard creation), but these are fairly high-level categories rather than specific concrete actions like 'create pivot tables' or 'generate charts'.	2 / 3
Completeness	Describes what it does (담당합니다 - 'is responsible for') but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric states missing 'Use when...' should cap completeness at 2, and this description is particularly weak.	1 / 3
Trigger Term Quality	Contains some relevant keywords like '데이터 분석' (data analysis), '리포트' (report), '대시보드' (dashboard), but missing common variations and natural terms users might say like 'chart', 'visualization', 'statistics', 'Excel', 'CSV', or file type mentions.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to data analysis domain, but 'data analysis' and 'reports' are broad terms that could overlap with many other skills like spreadsheet tools, business intelligence, or general document creation skills.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill is concise but lacks substance. It reads more like a job description than actionable guidance, providing no concrete instructions, code examples, or workflows for performing data analysis tasks. The skill needs significant expansion with executable examples and clear processes.

Suggestions

Add concrete code examples for common analysis tasks (e.g., pandas snippets for statistical analysis, visualization code with matplotlib/seaborn)

Define a clear workflow for creating analysis reports with validation steps (e.g., data validation -> analysis -> review -> output)

Include specific templates or examples of expected report formats and dashboard structures

Add references to detailed guides for each responsibility area (e.g., VISUALIZATION.md, REPORT_TEMPLATE.md)

Dimension	Reasoning	Score
Conciseness	The content is extremely brief and doesn't explain concepts Claude already knows. Every line serves a purpose without padding or unnecessary context.	3 / 3
Actionability	The skill provides only vague role descriptions and task categories without any concrete code, commands, specific examples, or executable guidance for performing data analysis tasks.	1 / 3
Workflow Clarity	No workflow steps are defined. The skill lists responsibilities but provides no sequence, process, or validation checkpoints for how to actually perform data analysis or create reports.	1 / 3
Progressive Disclosure	The content is well-organized with clear sections and mentions output locations, but provides no references to detailed materials, examples, or templates that would help with the listed tasks.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

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