CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chart-style-unifier

Batch-unify typography (font family, size, italics) for Word table cells and embedded charts; use when you need consistent formatting across theses/reports without changing body text.

Quality

70%

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 ./scientific-skills/Other/chart-style-unifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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's second half is a strong, concrete, executable guide (real scripts, accurate config example, complete VBA, sound linked-chart guidance), but the entire first half is generated template boilerplate that duplicates it with grammar errors and filler. Duplicated sections, a dangling tests reference, and no explicit validation step for a document-modifying batch operation hold it back.

Suggestions

Delete the first block of template sections (When to Use / Key Features / Dependencies / Example Usage / Implementation Details before the numbered ones); they duplicate sections 1–5 with filler like "Use this skill when a others task needs a packaged method instead of ad-hoc freeform output".

Add an explicit validation checkpoint to the run plan: after `change_table_font.py` executes, verify results against `references/style-apply-checklist.md` before returning the file, with an error-recovery step (e.g. what to do when the font is missing or the document is locked).

Remove the dangling `tests/test_table_font.py` reference (no tests directory exists in the bundle), and make the Excel macro in 4.3 self-contained by including the `ApplyChartTypography` definition it calls — or note explicitly that both snippets must be pasted into the same module.

DimensionReasoningScore

Conciseness

The first ~47 lines are template boilerplate that duplicate sections 1–5 almost entirely, including filler like "Use this skill when a others task needs a packaged method instead of ad-hoc freeform output" (broken grammar, no information), "Scope-focused workflow aligned to: [restates the description]", and "Parameters to clarify first: input path, output path, scope filters, thresholds..." — several padded sections, matching anchor 2. Not 1: the second half is genuinely lean with no explanation of concepts Claude already knows; not 3: wholesale section duplication is more than 'some unnecessary explanation'.

2 / 5

Actionability

Concrete executable guidance throughout the second half: pinned dependency table, `pip install python-docx pywin32`, `python scripts/init_run.py --table`, a config.json example that matches the actual generated config (verified against scripts/init_run.py), and a complete Word VBA macro. Minor gaps keep it at anchor 4 rather than 5: the Excel macro in 4.3 calls `ApplyChartTypography`, which is only defined in 4.2's snippet, so it is not self-contained despite being labeled "runnable", and 5.2 is conceptual ("implementation-dependent").

4 / 5

Workflow Clarity

Sequences are clear (init run dir → edit config.json → execute; and for linked charts: normalize Excel sources first → refresh in Word), matching anchor 3's 'steps listed but checkpoints missing or implicit' — the only validation is a vague "Review the generated output". Since this batch-modifies user documents, the rubric's guideline capping batch operations without validation at 3 applies; anchor 4 would require an explicit verify/error-recovery checkpoint (e.g. check items against references/style-apply-checklist.md before delivering).

3 / 5

Progressive Disclosure

The bundle matches the body's claims (scripts/init_run.py, generate_style_pack.py, change_table_font.py and references/style-apply-checklist.md, style-spec-template.md all exist and behave as described, verified), and 5.6 signals references one level deep. But 5.6 references `tests/test_table_font.py` which does not exist in the bundle, the body has two parallel sets of identically-named top-level sections (numbered and unnumbered), and ~170 lines of VBA that could live in references/ are inlined — 'some structure but could be better organized' (anchor 3), short of anchor 4's 'minor organization gaps'.

3 / 5

Total

12

/

20

Passed

Description

78%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 states what the skill does and when to use it, with concrete parameters and targets. Its main weaknesses are second-person phrasing ("use when you need") and missing a few natural trigger terms like ".docx" or "Word document".

Suggestions

Rewrite in third person, e.g. "Batch-unifies typography... Use when consistent formatting across theses/reports is needed" to avoid the second-person specificity penalty.

Add natural trigger terms users would say: ".docx", "Word document", "unify fonts", "chart labels/axes/legends".

DimensionReasoningScore

Specificity

"Batch-unify typography (font family, size, italics) for Word table cells and embedded charts" specifies the operation, parameters, and two targets, which sits between anchor 3 (one well-specified action) and anchor 4 (several distinct actions) — it is a single action richly parameterized, not multiple actions like extract/fill/merge. Base 4, but the second-person clause "use when you need consistent formatting" triggers the rubric's 1-point specificity penalty, landing on 3.

3 / 5

Completeness

Explicitly answers both: what ("Batch-unify typography (font family, size, italics) for Word table cells and embedded charts") and when ("use when you need consistent formatting across theses/reports without changing body text") with a concrete trigger scenario, matching anchor 5's structure. Not 4, because the 'when' clause is concrete and specific rather than generic.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "typography", "font family", "size", "italics", "Word table cells", "embedded charts", "consistent formatting", "theses/reports", "body text". A few natural terms a user would say are missing (".docx", "Word document", "fonts", "chart labels"), which matches anchor 4 rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (typography normalization for Word table cells and embedded charts) is clearly distinguishable with minor overlap risk against generic Word/docx formatting or chart-styling skills — anchor 4. Not 5: "consistent formatting" and "typography" could still collide with broader document-styling skills.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/chart-style-unifier/SKILL.md

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.