linkedin-profile-optimizer
Optimize LinkedIn profile for searchability, recruiter visibility, and engagement
35
30%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/linkedin-profile-optimizer/SKILL.mdQuality
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 (LinkedIn profile optimization) but is too brief and lacks explicit trigger guidance. It reads more like a tagline than a functional skill description, missing concrete actions and a 'Use when...' clause that would help Claude reliably select it.
Suggestions
Add a 'Use when...' clause with trigger terms like 'LinkedIn profile', 'recruiter', 'job search', 'professional headline', 'LinkedIn SEO', or 'profile review'.
List specific concrete actions such as 'Rewrites headlines, crafts keyword-rich summaries, optimizes experience sections, and suggests skills for endorsement'.
Include common user phrasing variations like 'improve my LinkedIn', 'LinkedIn makeover', 'get noticed by recruiters', or 'professional branding'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (LinkedIn profile) and lists some actions (optimize for searchability, recruiter visibility, engagement), but doesn't specify concrete actions like rewriting headlines, crafting summaries, selecting keywords, or restructuring experience sections. | 2 / 3 |
Completeness | Describes what it does (optimize LinkedIn profile) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, 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 'LinkedIn profile', 'searchability', 'recruiter visibility', and 'engagement' which are relevant keywords, but misses common user phrases like 'LinkedIn SEO', 'headline', 'summary', 'about section', 'job search', or 'professional branding'. | 2 / 3 |
Distinctiveness Conflict Risk | The LinkedIn-specific focus provides some distinctiveness, but 'optimize for engagement' and 'searchability' could overlap with general SEO or social media optimization skills. The niche is somewhat clear but not sharply delineated. | 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 more like a comprehensive LinkedIn optimization blog post than a focused skill file for Claude. It is excessively verbose, explaining common knowledge (photo tips, banner sizes, posting frequency) that wastes token budget. The strongest elements are the concrete examples (headline formulas, about section template, experience format) and the structured output format, but these are buried in unnecessary advisory content.
Suggestions
Cut the content by 60-70%: remove photo/banner advice, content strategy, recruiter settings, and the LinkedIn vs Resume comparison table — these are general knowledge Claude already has. Focus on the headline formula, about section structure, experience template, keyword strategy, and output format.
Add progressive disclosure by splitting detailed examples (e.g., full about section examples, keyword lists by industry) into separate reference files, keeping SKILL.md as a concise overview.
Add a validation step to the workflow: after generating optimized sections, verify character limits (220 for headline, 2600 for about), check keyword density, and confirm All-Star checklist items are addressed.
Remove or drastically condense sections like 'Profile Photo', 'Background Banner', 'Content Strategy', and 'Recruiter Visibility Settings' which are user actions Claude cannot perform and are not part of profile text optimization.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains things Claude already knows (what a LinkedIn profile photo is, what a background banner is, basic advice like 'friendly expression, slight smile'). The LinkedIn vs Resume table, photo requirements, banner pixel sizes, and content strategy sections are general knowledge that don't need to be in a skill file. Much of this reads like a blog post rather than actionable instructions for Claude. | 1 / 3 |
Actionability | Provides concrete examples of headlines, about sections, and experience entries which are useful templates. However, much of the content is advisory rather than executable (e.g., 'post 3-5x per week', 'get endorsements'). The output format template is a good actionable element, but many sections describe what to do rather than showing Claude exactly how to do it. | 2 / 3 |
Workflow Clarity | The output format section provides a clear sequence of action items and a structured template for delivering results. However, there's no explicit validation or feedback loop — no step to verify keyword density, check character limits against the written content, or validate that the profile meets All-Star requirements before finalizing. The overall flow from assessment to optimization is implied but not explicitly sequenced as a workflow. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite many sections (photo guidelines, content strategy, recruiter settings) that could be separated or omitted entirely. No bundle files exist, and the skill doesn't organize content into layers — everything is presented at the same level of detail. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%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
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.