CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ds-figure-polish

Use when a quest needs a polished milestone chart, paper-facing figure, appendix figure, or a mandatory render-inspect-revise pass before treating a figure as final.

60

Quality

76%

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/ds-figure-polish/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-organized, appropriately terse instruction skill: the mandatory render-inspect-revise workflow with its gated self-review checklist is exemplary, and the bundled mplstyle asset is genuinely used rather than duplicated. The main gaps are minor: no copy-paste-ready code snippet, some duplicated export guidance, and a trailing section of external policy pointers that are not part of the bundle.

DimensionReasoningScore

Conciseness

The body is a lean, well-sectioned list of rules with almost no explanation of concepts Claude already knows; minor trimmable spots remain, such as the motivational prose in 'Core principle' ("The goal is not to make a plot 'fancy'."), the vague "Do not rely entirely on defaults", and the duplicated export-format guidance across 'Surface classes', 'Style contract', and 'Export discipline'. This fits level 4 ('efficient; minor instances that could be trimmed') rather than level 5, and is clearly above level 3 since padding is the exception, not the rule.

4 / 5

Actionability

Guidance is concrete and specific for an instruction-only skill: a real bundled style path (assets/deepscientist-academic.mplstyle, verified to exist), exact figure sizes in inches, per-class export formats, an explicit inspection workflow, and a verbatim caption sentence to include. It falls short of level 5 because the only code-shaped guidance is a placeholder pattern (`plt.style.use(<path-to-assets/deepscientist-academic.mplstyle>)`) rather than a copy-paste-ready snippet, and some rules (e.g. 'legend minimal') leave the how to Claude. It is above level 3 because the guidance is direct and executable in substance, not pseudocode.

4 / 5

Workflow Clarity

The mandatory workflow is a clearly numbered 5-step sequence with an explicit validation step ("open the rendered figure yourself... inspect the actual result, not just the plotting code"), a feedback loop ("revise the figure if readability or composition is weak" then "re-export"), and a 10-item self-review checklist gated by "If any answer is negative, revise before calling the figure complete." This matches level 5 exactly: clear sequence, explicit validation, feedback loop, and a checklist; the operation is not destructive/batch so no capping applies.

5 / 5

Progressive Disclosure

The body is well-sectioned and the single bundle asset is real, appropriately referenced by path, and correctly kept out of the main file (the .mplstyle carries the concrete style values rather than duplicating them inline). It stays below level 5 because the skill is ~180 lines with no references/ split — the chart-selection heuristics, color rules, and size tables are candidates for a reference file — and the 'References to internal policy' section points to six paths that are not part of this bundle and are not clearly signaled as to whether they must be read.

4 / 5

Total

17

/

20

Passed

Description

61%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 has strong, explicit trigger guidance with natural domain phrasing, but it is entirely 'when' with no explicit statement of what the skill does. Adding a concise capability clause (e.g. applying an academic figure style and enforcing a render-inspect-revise-export loop) would raise both completeness and specificity.

Suggestions

Add an explicit 'what' clause before the 'Use when' clause, e.g. "Polishes research figures by applying an academic style contract and enforcing a render-inspect-revise loop before export."

Include common synonyms and file extensions in the trigger list, such as 'plot', 'publication figure', '.pdf', '.png', or '.svg' exports.

Clarify the domain word 'quest' (e.g. 'research task or experiment quest') so the trigger reads naturally outside the DeepScientist context.

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete artifacts ("polished milestone chart", "paper-facing figure", "appendix figure", "render-inspect-revise pass"), but it never states what the skill actually does — the actions (apply academic style, render, inspect, revise, export) are only implied by the trigger nouns. This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; it is above level 2 because the artifacts named are specific rather than generic, but below level 4 because no explicit capability list is present.

3 / 5

Completeness

The 'when' is explicit and strong ("Use when a quest needs..."), but the 'what' is only weakly implied: the reader must infer that the skill polishes and re-exports figures through an inspection loop. Per the anchors, this mirrors level 3 ('when' present, 'what' weakly implied) — it is not level 4 because the 'what' is never explicitly stated, and not level 2 because the trigger clause is explicit and specific.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present: "polished", "milestone chart", "paper-facing figure", "appendix figure", "figure as final". It is below level 5 because common synonyms and variations are missing — e.g. "plot", "publication figure", "matplotlib", and file extensions like .pdf/.png/.svg — while remaining above level 3 since several distinct, naturally-spoken trigger phrases are covered.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — "paper-facing figure", "appendix figure", "render-inspect-revise pass" are unlikely to fire for unrelated skills. Minor overlap risk remains with generic chart/dataviz styling skills triggered by "polished chart", keeping it below the clear-niche level 5 but above level 3.

4 / 5

Total

14

/

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

OpenLAIR/dr-claw

Path

skills/ds-figure-polish/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.