publication-chart-skill

This skill should be used when the user asks for a publication-quality scientific figure or table, wants help choosing the right chart for results, needs a paper-ready pubfig or pubtab workflow, wants a figure + companion table for a results section, wants an Excel sheet turned into publication-ready LaTeX, or wants an existing scientific figure/table reviewed and upgraded.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/publication-chart-skill/SKILL.md

Quality

Content

73%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-architected workflow skill with a clear sequenced process, explicit validation and recovery loops, and a QA checklist, supported by a properly disclosed reference bundle. It loses points for repeated install guidance and a dangling reference to a nonexistent examples/ directory.

Suggestions

Consolidate the duplicated install/probe commands: keep the canonical set in workflow step 0 and have the "Missing dependency behavior" section reference it rather than restating the same commands.

Inline one minimal copy-paste pubfig and one pubtab example in the body so the common case is fully executable without first opening a recipe file.

Remove or fix the "see examples/" pointer at the end of Resources, since no examples/ directory exists in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is directive and assumes Claude's competence without explaining concepts, but the install/probe guidance is repeated across "0. Probe the environment" and the "Missing dependency behavior" section (same helper commands restated), which is more than minor padding and could be consolidated.	3 / 5
Actionability	Provides concrete executable commands ("python3 scripts/ensure_publication_tooling.py --require pubfig --json", "pubtab xlsx2tex ...") and concrete good defaults ("one pubfig call + one save_figure(...)", "batch_export(...)"), but the main figure-generation Python patterns are delegated to recipe references rather than given as inline copy-paste code, leaving minor gaps.	4 / 5
Workflow Clarity	A clear numbered 0–7 workflow with explicit validation checkpoints (probe → report available/missing → auto-install → re-run probe), an error-recovery feedback loop (install fails → degrade gracefully), and a concrete publication QA checklist, matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	SKILL.md is a well-structured overview with a Resources section giving one-line descriptions of one-level-deep references, all verified to exist except the referenced "examples/" directory which is absent, a navigation gap that keeps it below the clean-navigation anchor.	4 / 5
	Total	16 / 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.

A strong, trigger-rich description that clearly signals when to use the skill and carves out a distinctive publication-figure/table niche. Its main weakness is that capabilities are expressed as user intents rather than as direct, comprehensive statements of what the skill does.

Suggestions

Lead with one declarative "what" statement (e.g., "Turns research results into publication-grade figures via pubfig and tables via pubtab") before the trigger list, so "what" is explicit rather than inferred.

Add common synonyms and file extensions users say (e.g., ".xlsx", ".tex", "LaTeX table", "paper figure") to round out trigger-term coverage.

Rephrase a few "wants..." clauses as skill actions ("chooses the right chart", "converts Excel to publication-ready LaTeX") to lift specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete actions ("choosing the right chart for results", "figure + companion table for a results section", "Excel sheet turned into publication-ready LaTeX", "figure/table reviewed and upgraded"), but they are framed as user intents rather than crisp skill actions, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	An explicit "This skill should be used when the user asks for... or wants..." clause answers "when" with concrete trigger phrases, and the enumerated intents convey "what", but the "what" is distributed across scenarios rather than stated as a single declarative capability, keeping it below the anchor that crisply answers both.	4 / 5
Trigger Term Quality	Strong natural phrasing ("publication-quality scientific figure or table", "choosing the right chart for results", "Excel sheet turned into publication-ready LaTeX") but omits synonyms and file extensions like .xlsx and .tex, so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The publication-quality scientific figure/table niche with named tooling ("pubfig or pubtab", "Excel to publication-ready LaTeX") is a clear, distinct trigger space with minimal overlap risk against general plotting skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 6 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/publication-chart-skill/SKILL.md
Commit: 6ed46da

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.