CtrlK
BlogDocsLog inGet started
Tessl Logo

venue-templates

Venue-specific LaTeX templates, formatting requirements, and submission guidelines for journals, conferences, posters, and grants—use when a target venue imposes strict layout, page limits, anonymization, or agency compliance rules.

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, largely executable skill body with a clear end-to-end workflow and real bundle files backing the references. The main issues are a non-functional `--type "article"` flag in the flagship example, a missing `assets/examples/` directory, and the absence of an explicit validation feedback loop.

Suggestions

Fix the Example Usage command: replace `--type "article"` with a valid query_template.py choice (e.g. `--type journals`) so the flagship example runs as written.

Either create `assets/examples/` with the venue-typical writing samples described in the body, or remove the two references to it (lines 29 and 86) to avoid a dead pointer.

Add an explicit feedback loop after step 4 (e.g. "If validation reports violations, adjust the template/metadata and re-run validate_format.py until it passes") to lift workflow clarity to a 5.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's LaTeX competence, but the Key Features and Implementation Details sections restate the template/requirement inventory, and Implementation Details lightly over-explains what the scripts do rather than just pointing to them.

4 / 5

Actionability

Provides copy-paste bash commands for a full query → customize → compile → validate flow with real file paths, but the example uses `--type "article"` which the script rejects (valid choices are journals/posters/grants/all), so the literal command would fail.

4 / 5

Workflow Clarity

Clear numbered sequence with an explicit validation checkpoint (step 4, validate_format.py), but it lacks the explicit "if validation fails, fix and re-run" feedback loop that anchors a 5 for batch/destructive-style operations.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references into references/ and assets/ with organized sections, but `assets/examples/` is referenced twice in the body and does not exist, leaving a broken navigation pointer.

4 / 5

Total

16

/

20

Passed

Description

87%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, well-targeted description that pairs a concrete capability statement with an explicit "use when" trigger and venue-specific constraint language. Minor room to add file-extension synonyms and the query/customize/validate actions for maximal granularity.

DimensionReasoningScore

Specificity

Names the domain and several concrete deliverables — "Venue-specific LaTeX templates, formatting requirements, and submission guidelines" — but stops short of the granular action list (e.g. query/customize/validate) that would warrant a 5.

4 / 5

Completeness

Explicitly answers both what ("Venue-specific LaTeX templates, formatting requirements, and submission guidelines") and when ("use when a target venue imposes strict layout, page limits, anonymization, or agency compliance rules") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ("journals, conferences, posters, and grants", "page limits, anonymization, or agency compliance rules") that users would say, though it omits synonyms/extensions like ".tex", "LaTeX class", or "camera-ready".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (venue-imposed LaTeX submission compliance) with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
aipoch/medical-research-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.