CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-multi-sheet-threshold-analysis

统计多Sheet Excel总行数并根据规模选择处理策略,提取特定维度信息进行去重统计,并生成摘要与明细报表。

56

Quality

63%

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-data-cleaning/duplicate-removal/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 skill body is a concise, actionable four-step Python workflow with good organization, but it lacks validation/verification checkpoints for a batch file-writing operation, capping workflow clarity. Placeholder values in the code require substitution before execution.

Suggestions

Add validation/verification checkpoints — e.g., assert expected output files exist and re-read them to confirm row counts match the dedup results — before declaring the workflow complete.

Replace or clearly flag placeholder values (target_sheet, keywords, target_col_idx) so the code is closer to copy-paste ready, or add a brief note on how to obtain them from the input file.

DimensionReasoningScore

Conciseness

The body is mostly lean code with brief inline comments and no padding of concepts Claude already knows; only minor over-explanation (e.g., repeated pandas imports, "使用 set 进行高效去重") could be trimmed.

4 / 5

Actionability

Each step provides concrete, executable Python code that is mostly copy-paste ready, with only minor gaps from placeholder values ("关键词A", "关键词B", target_col_idx = 1) that the user must substitute.

4 / 5

Workflow Clarity

The four steps (Step1–Step4) are clearly sequenced, but this batch/file-writing workflow has no validation or verification checkpoints, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is well-organized into clearly labeled steps with a one-level-deep pointer to the parent workflow SKILL.md; no bundle files exist to reference, and the structure is appropriate for this single-purpose sub-skill.

4 / 5

Total

15

/

20

Passed

Description

58%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 clearly conveys what the skill does through several concrete actions, but lacks any explicit trigger/"Use when" guidance, capping completeness and trigger-term quality. It is written in third person with no first/second-person voice issues.

Suggestions

Add an explicit "Use when..." clause stating when Claude should invoke this skill (e.g., when the user mentions multi-sheet Excel deduplication, summary/detail reports, or .xlsx threshold analysis).

Include natural user-facing trigger terms and file extensions such as ".xlsx", "Excel 去重", or "多 Sheet 统计" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "统计多Sheet Excel总行数", "根据规模选择处理策略", "提取特定维度信息进行去重统计", "生成摘要与明细报表" — with only minor gaps in coverage (the strategy selection is not detailed).

4 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ("多Sheet Excel", "去重统计", "摘要与明细报表") but misses natural user phrasings and file extensions like ".xlsx" or synonyms a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The multi-sheet row-count + dedup-analysis + summary/detail-report niche is fairly specific and mostly distinct, with only minor overlap risk against general Excel skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.