portfolio-case-study-writer
Transform resume bullets into detailed portfolio case studies
37
33%
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/portfolio-case-study-writer/SKILL.mdQuality
Discovery
40%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 and distinctive niche—converting resume bullets into portfolio case studies—but is too terse. It lacks a 'Use when...' clause, misses common keyword variations, and doesn't enumerate the specific sub-tasks or outputs involved.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to expand resume bullet points into full portfolio case studies, project writeups, or detailed work samples.'
Include additional trigger terms and synonyms such as 'CV', 'work experience', 'project writeup', 'portfolio piece', and 'accomplishments'.
List more specific actions the skill performs, e.g., 'Expands brief resume accomplishments into structured case studies with context, approach, results, and impact sections.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (resume/portfolio) and a specific action (transform bullets into case studies), but only describes one action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also thin—so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes natural terms like 'resume bullets', 'portfolio', and 'case studies' that users might say, but misses common variations like 'CV', 'work experience', 'project writeups', or 'portfolio pieces'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific niche of transforming resume bullets into portfolio case studies is quite distinctive and unlikely to conflict with other skills; the combination of 'resume bullets' and 'portfolio case studies' creates a clear, unique trigger. | 3 / 3 |
Total | 8 / 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 like a comprehensive human-facing tutorial on writing case studies rather than a concise, actionable skill for Claude. Its main strengths are the concrete examples and clear output template, but it is severely bloated with explanatory content Claude doesn't need (e.g., why case studies matter, what each section's purpose is). The lack of an actual transformation workflow—how to go from resume bullet input to case study output, including what to ask the user—is a significant gap.
Suggestions
Cut the content by 60-70%: remove 'Why Case Studies Matter', section purpose explanations, and role-specific variations (or move them to a separate ROLES.md). Focus on the output template, one concise example, and the quality checklist.
Add an explicit transformation workflow: define steps like (1) receive resume bullet, (2) ask clarifying questions about context/metrics/process, (3) draft case study using template, (4) review against checklist, (5) iterate with user feedback.
Split role-specific guidance (PM, UX, Engineer, Marketing) and visual element tips into separate referenced files to improve progressive disclosure.
Add a concrete input→output example showing a single resume bullet being transformed into a mini case study, so Claude has a clear pattern to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts like why case studies matter, what each section's 'purpose' is, and includes lengthy examples for every section. Much of this is knowledge Claude already has—the skill reads more like a blog post or tutorial for humans than concise instructions for an AI agent. | 1 / 3 |
Actionability | Provides concrete examples and a clear output template, which is useful. However, the examples are illustrative rather than executable—there are no actual commands, scripts, or tool invocations. The guidance is specific enough to follow but is more of a reference document than step-by-step actionable instructions for transforming a given resume bullet. | 2 / 3 |
Workflow Clarity | The case study structure (Overview → Problem → Process → Solution → Results → Learnings) provides a clear sequence, and the output template and quality checklist are helpful. However, there's no explicit workflow for the transformation process itself—how to take a resume bullet as input, what questions to ask the user, how to handle missing information, or validation/feedback loops before producing the final output. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to supporting documents. The role-specific variations, visual element guidance, and detailed section-by-section examples could easily be split into separate files. The content is a wall of text that could benefit significantly from better organization across files. | 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.