ResumeSkills is a collection of AI-agent skills for improving resumes, preparing job applications, practicing interviews, and planning career moves. It is intended for job seekers, career changers, and professionals using Claude Code for tasks such as ATS checks, job-description matching, resume tailoring, and salary negotiation. The catalogue entry consists of the project's career-focused skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Paramchoudhary/ResumeSkills --skill portfolio-case-study-writergit clone --depth 1 https://github.com/Paramchoudhary/ResumeSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/paramchoudhary/resumeskills/portfolio-case-study-writer)<a href="https://agentmods.dev/skills/paramchoudhary/resumeskills/portfolio-case-study-writer"><img src="https://agentmods.dev/badge/skills/paramchoudhary/resumeskills/portfolio-case-study-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/paramchoudhary/resumeskills/portfolio-case-study-writer"><img src="https://agentmods.dev/badge/skills/paramchoudhary/resumeskills/portfolio-case-study-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.02028 |
| Opus 5 | $0.00007 | $0.01014 |
| Sonnet 5 | $0.00003 | $0.00406 |
| Haiku 4.5 | $0.00001 | $0.00203 |
Grade A, and why
portfolio-case-study-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- portfolio-case-study-writer — 100% identical, 0 lines differ
- portfolio-case-study-writer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Case Study Writer
When to Use This Skill
Use this skill when the user:
- Wants to create portfolio case studies
- Needs to expand resume bullets into detailed writeups
- Is building a portfolio website
- Wants to showcase project work in depth
- Mentions: "case study", "portfolio", "project writeup", "work samples", "portfolio piece"
Core Capabilities
- Transform resume bullets into detailed case studies
- Structure case studies for maximum impact
- Create compelling project narratives
- Balance technical detail with business context
- Format for portfolio websites
- Tailor depth to audience
Case Study Purpose
Why Case Studies Matter:
- Resumes show WHAT you did; case studies show HOW and WHY
- Demonstrate thinking process, not just outcomes
- Allow deeper showcase of skills
- Differentiate you from other candidates
- Required for many PM, UX, and creative roles
The Case Study Structure
Standard Structure
1. Overview (Project summary)
2. Problem (What needed to be solved)
3. Process (How you approached it)
4. Solution (What you created/delivered)
5. Results (The impact)
6. Learnings (What you'd do differently)
Time to Read
- Quick Read: 3-5 minutes (essential for portfolio)
- Deep Dive: 10-15 minutes (for interested readers)
Section-by-Section Guide
1. Overview Section
Purpose: Hook the reader, provide context
Include:
- Project name and company
- Your role
- Timeline
- Team size
- One-sentence summary of impact
Example:
# Redesigning the Checkout Flow
**Company:** E-Commerce Inc.
**Role:** Lead Product Designer
**Timeline:** 6 weeks
**Team:** 2 designers, 3 engineers, 1 PM
**Summary:** Reduced cart abandonment by 35% through a streamlined 3-step checkout process, generating $2M in recovered revenue.
2. Problem Section
Purpose: Set up why this work mattered
Include:
- Business context
- User pain points
- Key metrics or goals
- Constraints
Example:
## The Problem
E-Commerce Inc. was experiencing 68% cart abandonment—significantly higher than the industry average of 55%. Exit surveys and user research revealed several issues:
- **Too many steps:** Our checkout had 7 screens
- **Forced account creation:** Users had to register before purchasing
- **Hidden costs:** Shipping wasn't shown until step 5
- **Mobile friction:** Forms weren't optimized for mobile
**Goal:** Reduce cart abandonment to below 50% within 3 months.
**Constraints:**
- No changes to existing payment integrations
- Had to maintain PCI compliance
- 6-week timeline before holiday season
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 370 lines · 14 tokens per session scan A b6b17fe94dd8
portfolio-case-study-writer is a skill published in the GitHub repository Paramchoudhary/ResumeSkills (2,220 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 2,028 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…