CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-data-analysis-and-report-generation

从Excel提取多类型数据,并生成包含可视化图表与下载链接的综合分析报告。

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sn-da-excel-workflow/capability/excel-result-export/report-generation-export/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The content delivers executable, code-first guidance across a clear three-step sequence and stays concise, but lacks validation/verification checkpoints for its batch and file-writing operations and leans on a few undefined variables and placeholders.

Suggestions

Add validation checkpoints between steps, e.g. verify category_counts is non-empty before plotting and confirm output files exist after savefig/to_excel.

Define or note the assumed context variables (combined_df, output_dir) and import os so the code blocks are copy-paste runnable.

Add a brief error-recovery note for Step2 (e.g., what to do when '限值' parsing fails or target_val cannot be coerced).

DimensionReasoningScore

Conciseness

The body is code-forward and assumes Claude knows pandas/matplotlib, with only brief functional comments; minor placeholder comments ('占位示例', '替换为实际列名') keep it just shy of fully lean.

4 / 5

Actionability

Three concrete, mostly-executable Python blocks cover the common cases, but they rely on assumed context (combined_df, output_dir, unimported os) and placeholders that the user must replace, leaving minor gaps.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Step1/Step2/Step3), but there are no validation checkpoints for batch row-iteration and file writing, which per the batch-operation cap limits workflow clarity to 3.

3 / 5

Progressive Disclosure

The skill is self-contained in one file with a clearly signaled one-level reference to the parent workflow SKILL.md and three organized step sections; no bundle files exist to require deeper splitting.

4 / 5

Total

15

/

20

Passed

Description

53%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.

The description is third-person and states concrete capabilities with a clear 'what', but omits any 'when to use' trigger guidance and has thin keyword coverage beyond 'Excel'. It is reasonably distinct within the Excel domain.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when analyzing Excel files, generating charts from spreadsheet data, or producing downloadable analysis reports').

Expand trigger terms with natural synonyms and the file extension, e.g. 'Excel, .xlsx, 表格, 报表'.

Replace the vague '多类型数据' with the concrete data types handled to lift specificity.

DimensionReasoningScore

Specificity

Names the domain (Excel) and 1-2 concrete actions ('提取多类型数据', '生成...综合分析报告' with charts and download links), but '多类型数据' is vague and the action set is not comprehensive.

3 / 5

Completeness

Provides a clear 'what' (extract data and generate analysis reports with charts/download links) but no 'Use when...' trigger clause, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Contains one strong natural keyword ('Excel') but lacks common variations/synonyms users might say (.xlsx, 表格, 报表, spreadsheets).

3 / 5

Distinctiveness Conflict Risk

The niche (Excel multi-type data extraction + charted analysis reports + download links) is mostly distinct, with only minor overlap risk against sibling Excel sub-skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
OpenSenseNova/SenseNova-Skills
Reviewed

Table of Contents

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.