academic-cv-builder

Format CVs for academic positions with publications, grants, and teaching

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/academic-cv-builder/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (academic CV formatting) and mentions key components, but it lacks a 'Use when...' clause, which significantly hurts completeness. The trigger terms are reasonable but miss common synonyms, and the actions described are limited to just 'format' without elaborating on specific capabilities.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to create or format a curriculum vitae for academic, faculty, or research positions.'

Include common trigger term variations such as 'curriculum vitae', 'faculty CV', 'tenure-track', 'academic resume', and 'research CV'.

List more specific actions beyond 'format', such as 'organize publication lists, structure grant histories, arrange teaching portfolios, and order academic service sections'.

Dimension	Reasoning	Score
Specificity	Names the domain (academic CVs) and lists some specific elements (publications, grants, teaching), but doesn't describe concrete actions beyond 'format' — e.g., it doesn't mention organizing sections, generating citation lists, or converting between formats.	2 / 3
Completeness	Describes what the skill does (formats academic CVs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also only moderately detailed, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'CVs', 'academic', 'publications', 'grants', and 'teaching' which users might naturally say, but misses common variations like 'curriculum vitae', 'academic resume', 'tenure', 'faculty CV', or 'research experience'.	2 / 3
Distinctiveness Conflict Risk	The 'academic positions' qualifier and specific elements (publications, grants, teaching) help distinguish it from general resume/CV skills, but it could still overlap with general CV formatting or resume-building skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a comprehensive reference guide about academic CVs rather than a concise, actionable skill for Claude. It extensively explains concepts Claude already knows (what CV sections are, how academia works, resume vs CV differences) while lacking a clear decision-making workflow for actually building a CV from user input. The monolithic structure with no progressive disclosure compounds the token inefficiency.

Suggestions

Cut 70-80% of the content by removing explanations of what academic CV sections are and what academia values—Claude already knows this. Focus only on specific formatting templates and decision rules.

Add a clear workflow: 1) Gather user info (role type, field, career stage), 2) Select section order based on role, 3) Format each section using templates, 4) Review against checklist. Make this the primary structure.

Split discipline-specific conventions and role-specific emphasis into separate reference files to reduce the main skill's token footprint.

Replace the 'When to Use This Skill' section with a single line—Claude can infer when to use an academic CV skill from context.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Explains obvious concepts like the difference between a resume and CV, what each CV section means, and discipline-specific conventions—all knowledge Claude already possesses. The comparison table, length guidelines, and most section descriptions are padding that don't add actionable value beyond what Claude inherently knows about academic CVs.	1 / 3
Actionability	Provides concrete formatting examples for each section which are useful as templates, but these are static text templates rather than executable code/commands. The guidance is more of a reference document than actionable instructions—it tells Claude what sections exist rather than providing a clear decision procedure for generating a CV from user input.	2 / 3
Workflow Clarity	The output format section provides a basic structure and the checklist at the end is useful, but there's no clear workflow for gathering information from the user, making decisions about section ordering, or validating the output. The process of actually building a CV from user input is implicit rather than explicitly sequenced.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content—from basic section descriptions to discipline-specific conventions to role-specific emphasis—is inlined in a single massive document. Much of this content (e.g., discipline conventions, role-specific emphasis) could be split into separate reference files.	1 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: paramchoudhary/resumeskills
Commit: 24c6edc

Reviewed: 12 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.