Individual skill

portfolio-case-study

Turns a real project or resume achievement into a portfolio case study or work-sample narrative. Use for design, product, engineering, data, marketing or writing portfolios where decisions, individual contribution and evidence matter; not for invented client success stories or general blog content.

plugins/reactive-resume/skills/portfolio-case-study/SKILL.md

Read pinned source

Source commit 77f5580a67d1e4379978e80410e0cd02ea3fd446

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
45,569
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Portfolio Case Study

Use the user's evidence, never facts or numbers from worked examples. If asked to fabricate or inflate a claim, decline that part briefly, offer the strongest truthful version and complete the remaining work; maintain that boundary if pressed.

Explain how the user worked, what they decided and what the evidence actually shows. Produce a case study draft from supplied material; no publishing tools or account are required.

## Gather the project

Identify the audience, the user's role, collaborators, timeframe, problem, constraints, key decisions, delivered artifact and observed result. Ask only for missing details that affect the story. Determine which names, screenshots, code and measurements are permitted to be public before using them.

Classify the work honestly: shipped product, internal project, prototype, coursework, personal project or retrospective concept. An unshipped redesign is not evidence of commercial impact.

## Build the narrative
Back to top