Communitygithub.com

HaroonArshad-53/skills-for-everyone

Turn rough notes about a finished project into a portfolio case study and a short LinkedIn or social post that proves skill with the problem, process, and result, without inventing metrics. Use when a user finishes a project and asks to add it to their portfolio, write a case study, a Behance or Dribbble description, or a LinkedIn post about their work.

What is skills-for-everyone?

skills-for-everyone is a Claude Code agent skill that turn rough notes about a finished project into a portfolio case study and a short LinkedIn or social post that proves skill with the problem, process, and result, without inventing metrics. Use when a user finishes a project and asks to add it to their portfolio, write a case study, a Behance or Dribbble description, or a LinkedIn post about their work.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/HaroonArshad-53/skills-for-everyone/tree/HEAD/skills/portfolio-case-study

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Portfolio Case Study Builder

When to use this skill

  • A project is finished and needs to become portfolio proof
  • Updating a portfolio, Behance, Dribbble, or personal website
  • Writing a LinkedIn post about completed work without sounding boastful

Workflow

  1. Collect the raw material: client type (not name unless the user has permission), the problem, what was delivered, tools used, timeline, and any result the user can honestly state.
  2. Structure the case study: The Problem (client situation in 2 lines), My Role, The Process (3-5 steps, decisions and why), The Deliverable, The Result, What I Learned.
  3. For results: use only what the user provided. If there is no number, describe the visible outcome (the new logo stays readable at Instagram profile size) instead of inventing percentages.
  4. Write the short version too: a 100-150 word LinkedIn post - hook line about the problem, 3 lines of process, the result, one lesson, and a soft call to action.
  5. Suggest the visuals to attach: before and after, process sketch, final deliverable - in the order a scroller should see them.

Rules - never break these

  • Never invent client names, revenue numbers, percentages, or testimonials. A true small result beats a fake big one, and clients check.
  • Do not reveal a client confidential details, unreleased work, or internal data. Describe the client by type if unsure.
  • Process is the proof for beginners: clear thinking is what hires juniors, not claimed years of experience.

Output format

  • Case study - full version in the structure above, ready for portfolio or Behance
  • LinkedIn post - short version, ready to paste
  • Visuals to attach - ordered list
  • Missing proof - 1 line: what result or permission to ask the client for, if any

Example

User: Make a case study: I redesigned a bakery logo and menu cards, small local bakery, took 1 week, Illustrator, owner said customers compliment the new menu. No sales numbers.

Good output (excerpt): Result line written honestly: The owner reports customers now compliment the menu cards in-store - the previous design was text-only and hard to read at the counter. No percentage invented. The process section shows the readability decision that actually did the work.

Related Skills