CtrlK
BlogDocsLog inGet started
Tessl Logo

formatted-export-with-parquet

从多Sheet Excel文件中识别指定条件的记录,并将筛选结果以整行标红格式导出为Excel文件,适用于数据清洗、条件筛选与可视化标记场景。

60

Quality

71%

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/formatted-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.

A concise, actionable two-step skill with real code and a clean one-level reference to its parent workflow. Its main weakness is the absence of validation/verification checkpoints for a batch sheet-processing and file-writing operation, which caps workflow clarity.

Suggestions

Add validation checkpoints: confirm the matched target column before filtering, and verify the output file was written correctly (e.g., re-open with openpyxl to confirm the red fills) — the batch-over-sheets write currently lacks any feedback loop.

Show how all_sheets is loaded (e.g., pd.read_excel(path, sheet_name=None)) so Step1 is fully runnable, and replace the placeholder 'keyword1'…'keyword4' with a concrete example or a clearly marked <user_column_keyword> placeholder.

Add light error handling for the empty-result and no-target-column paths (beyond a single print) to make the workflow robust.

DimensionReasoningScore

Conciseness

Lean body that is mostly executable code with brief step descriptions and minimal prose; a few placeholder keywords and code comments could be trimmed.

4 / 5

Actionability

Provides real, mostly copy-paste-ready pandas/openpyxl code, but all_sheets is never shown being loaded and the column-matching uses placeholder 'keyword1'…'keyword4' that the user must replace.

4 / 5

Workflow Clarity

Step1 and Step2 are clearly sequenced, but this is a batch operation over all sheets writing an output file with no validation or verification checkpoints, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized into a header, a clearly signaled one-level reference to the parent workflow SKILL.md, and a Skill Steps section; no bundle files exist and the inline code is appropriate for a simple sub-skill.

4 / 5

Total

15

/

20

Passed

Description

75%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 specific, mostly complete description that names concrete actions and usage scenarios for a narrow Excel export niche. It would benefit from an explicit 'Use when…' trigger clause and file-extension synonyms to reach the top level.

Suggestions

Add an explicit 'Use when…' trigger clause naming concrete user phrases (e.g., 'Use when the user wants to highlight or filter specific rows across multiple Excel sheets') to lift completeness and trigger-term quality.

Include the .xlsx file extension and a synonym (e.g., 工作簿/Workbook) to broaden natural trigger coverage toward comprehensive.

DimensionReasoningScore

Specificity

Names the domain (multi-sheet Excel) and several specific concrete actions — condition-based record identification and whole-row red-highlight export — with only minor coverage gaps.

4 / 5

Completeness

Clearly states what the skill does and provides a scenario-based 'when' (适用于…场景), but the trigger guidance is not as explicit as a concrete 'Use when the user mentions X' clause.

4 / 5

Trigger Term Quality

Includes natural terms a user would say (Excel, Sheet, 数据清洗, 条件筛选, 可视化标记) but omits the .xlsx extension and common synonyms, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The whole-row red-highlight export niche is distinctive, with only minor overlap risk against sibling Excel-workflow sub-skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata' field is not a dictionary

Warning

metadata_field

'metadata' field is not a dictionary

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

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.