CtrlK
BlogDocsLog inGet started
Tessl Logo

venue-templates

Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.

65

Quality

79%

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/venue-templates/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, verification-first guide with concrete executable helper commands and clear reference routing, supported by a complete, real bundle. Its main weaknesses are verbosity from redundant currency warnings and inlined workflows, plus an implicit rather than explicit validation retry loop.

Suggestions

Consolidate the repeated currency/verification mandates into the single 'Mandatory Currency Rule' section and have later sections reference it, to reduce token redundancy.

Make the validate-fix-retry feedback loop explicit in the validation step (e.g., 'If validation fails, fix and re-run until it passes before proceeding').

Move the detailed Common Workflows into the relevant reference files, leaving the SKILL.md as a concise overview that links out, to sharpen the overview/detail separation.

DimensionReasoningScore

Conciseness

The body is well-organized but lengthy for a skill overview, repeating the currency/verification mandate across the Mandatory Currency Rule, workflow, and Final Compliance Checklist, and inlining several full multi-step procedures that assume knowledge Claude already has. It is mostly efficient yet has several padded/redundant sections that could be tightened.

3 / 5

Actionability

It provides concrete, executable bash commands for all three helper scripts (query_template.py, customize_template.py, validate_format.py) with real flags and example values, plus a copy-paste compliance-note block. Minor gaps: some commands depend on external downloads not shown, keeping it just below fully copy-paste-ready.

4 / 5

Workflow Clarity

The Verification-First Workflow is a clearly numbered five-step process with explicit checkpoints (record source URL + date, distinguish stages) and a validation step, and the four Common Workflows are well-sequenced with checklists. It does not reach 5 because the validation feedback loop (fail -> fix -> re-verify) is implied rather than an explicit retry cycle.

4 / 5

Progressive Disclosure

Structure is strong: an overview table maps each need to a specific one-level-deep reference file, and bundled assets are listed by status in clearly signaled tables; all referenced files (references/*.md, scripts/*.py, assets/**) exist. It falls short of 5 because the SKILL.md itself still inlines several full workflow sections that could live in references, slightly blurring the overview/detail split.

4 / 5

Total

15

/

20

Passed

Description

91%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 is clear, concise, third-person, and explicitly answers both what the skill does and when to use it, with strong natural trigger phrases. Its only weakness is modest breadth of distinctiveness given the PDF-inspection overlap.

DimensionReasoningScore

Specificity

Lists four concrete document types (journal manuscripts, conference papers, research posters, grant documents) and specific actions (selecting template, checking page/anonymity rules, inspecting PDF), with minor gaps in coverage. It does not reach 5 because the actions are framed at a moderate granularity rather than a comprehensive enumerated action list.

4 / 5

Completeness

It explicitly answers both 'what' (prepare manuscripts/papers/posters/grants with venue-specific formatting and LaTeX scaffolds) and 'when' (an explicit 'Use when...' clause with concrete triggers). Matches the 5-anchor example structure directly.

5 / 5

Trigger Term Quality

The 'Use when' clause covers natural phrases users would say — 'selecting an official template', 'checking current page or anonymity rules', 'adapting academic writing', 'inspecting a submission PDF' — including synonyms and domain variants. This is comprehensive coverage of natural trigger terms.

5 / 5

Distinctiveness Conflict Risk

The venue/publication niche is fairly distinct and unlikely to trigger for unrelated skills, but 'inspecting a submission PDF' and 'adapting academic writing' have minor overlap with general PDF or writing skills. It sits above 3 (mostly distinct) but the PDF-inspection angle keeps it just short of a clear-niche 5.

4 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 9 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
K-Dense-AI/scientific-agent-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.