career-changer-translator

Translate skills from one industry to another, identify transferable skills

Quality

30%

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/career-changer-translator/SKILL.md

Quality

Content

27%

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

This skill is extremely verbose, containing extensive lists and examples that pad the context window without proportional value—Claude already understands transferable skills and career change concepts. The translation examples and output format template provide some actionable structure, but the content would be far more effective if condensed to ~25% of its current length with detailed industry-specific tables moved to separate reference files.

Suggestions

Reduce the content by 70-80%: remove the 'Universal Transferable Skills' list, the 'Career Change Challenge' section, and the 'Addressing the Why Question' section—Claude already knows these concepts. Keep only the output format, a single translation example, and the key reminders.

Move industry-specific translation tables (Teacher→Corporate, Military→Corporate, etc.) into separate reference files like TRANSLATIONS.md and link to them from the main skill.

Add an explicit workflow sequence: 1) Identify user's current field/role, 2) Identify target field/role, 3) Map transferable skills, 4) Translate experience bullets, 5) Identify gaps, 6) Generate output—with validation checkpoints.

Consolidate the 'Industry-Specific Career Change Paths' section into a brief reference table or separate file rather than listing entry points and bridge activities for each industry inline.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Extensively lists universal transferable skills Claude already knows, explains obvious concepts like why career changes are hard, and includes lengthy translation tables for 5+ industry pairs. Much of this is general knowledge that doesn't need to be spelled out.	1 / 3
Actionability	Provides concrete translation examples and a clear output format template, which is useful. However, much of the content is descriptive lists rather than executable guidance—there are no code commands or tool-based steps, and the 'how' of actually performing translations is mostly shown by example rather than a systematic method.	2 / 3
Workflow Clarity	The output format section provides a clear template for structuring the response, and the resume strategy has numbered steps. However, the overall workflow for how to approach a career change translation request is not explicitly sequenced—there's no clear 'first do X, then Y, validate Z' process to follow when a user asks for help.	2 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to external files. The extensive translation tables, industry-specific paths, and detailed examples could easily be split into separate reference files. The document is a wall of text that would benefit greatly from being broken into focused sub-documents.	1 / 3
	Total	6 / 12 Passed

Description

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—cross-industry skill translation—but is too brief and lacks explicit trigger guidance ('Use when...'), concrete output descriptions, and natural keyword variations that users would employ. It would benefit significantly from specifying when Claude should select it and listing more user-facing trigger terms like 'career change' or 'career pivot'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions career change, career pivot, switching industries, or mapping experience to a new field.'

Include more natural trigger terms users would say: 'career change', 'career transition', 'career pivot', 'switching fields', 'cross-industry experience', 'resume for new industry'.

Expand the 'what' portion with concrete outputs, e.g., 'Produces a transferable skills mapping, reframes past experience for target industries, and suggests how to position qualifications for a new career path.'

Dimension	Reasoning	Score
Specificity	Names the domain (skill translation between industries) and two actions (translate skills, identify transferable skills), but lacks detail on concrete outputs or methods—e.g., does it produce a resume, a mapping document, a list?	2 / 3
Completeness	Describes what it does (translate skills, identify transferable skills) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'transferable skills' and 'industry' which users might say, but misses common variations such as 'career change', 'career pivot', 'career transition', 'resume', 'job switch', or 'cross-industry'.	2 / 3
Distinctiveness Conflict Risk	The concept of translating skills between industries is a recognizable niche, but the vague phrasing could overlap with general career coaching, resume writing, or job search skills.	2 / 3
	Total	7 / 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
Path: skills/career-changer-translator/SKILL.md
Commit: 74ae19e

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