Portfolio Skills GitHub Install

Two skills for your AI agent

Your Portfolio Gets 30 Seconds

By Owi. After 15 years in digital product, I can tell you that is about what the first look lasts. One skill reads your portfolio like the person hiring; the other builds it to pass.

$npx skills@latest add adrituyo/portfolio-skills
30 sThe first look
17Rules checked
3Grids to build with
The 30-second theory

Nobody spends more than 30 seconds on a portfolio the first time.

Whoever is hiring has forty tabs open. The first look decides which ones get a real read, and it goes the same way every time: five seconds on the first screen, ten scanning, fifteen on one project. Both skills are built around those three moments.

The skills 2

Ordered the way you would reach for them: look at what you have, then build what is missing.

02

Build it

One content file in, a finished site out. The structure is fixed; the look stays yours.

/portfolio-audit

Portfolio Audit

Find out what a stranger takes from your portfolio in 30 seconds, and what to fix first, before the person hiring finds out for you.

  • Use it whenYou are about to apply and want to see it with fresh eyes.
  • Or whenYou keep sending it and nobody writes back.
  • Or whenYou just redesigned it and can no longer tell if it works.
You say

Audit my portfolio: yourname.com. I'm applying for senior product roles.

It does
  1. 1Looks at your first screen, on desktop and on a phone.
  2. 2Walks the page the way a reviewer does: first screen, scan, one project.
  3. 3Marks the 17 rules against what it actually saw.
You get

Passes on the first screen, loses it on the scroll: the headline says lead, the work says art director.

9 of 17 pass · 4 weak · 4 fail

  1. 1Put the work you led first.
  2. 2One line per project: role, year, for whom.
  3. 3Move the proof from About to the top.

Each fix comes with the copy rewritten. Then what already works, what it could not check, and all 17 rules with the evidence from your page.

It never invents a fact about you. When a better headline needs a number it does not have, it leaves a slot: [N] years, [team size].

What the audit checks

The 17 rules

Grouped by the moment a reviewer meets them, each under the question they are asking at that point. None is about taste: a plain portfolio can pass all seventeen and a beautiful one can fail half.

First screen

0–5 s

Who is this, and at what level?

  1. 01Say what you do, in one sentenceA line that could not sit on anyone else's site.
  2. 02Show work on the first screenThe claim needs evidence before the first scroll.
  3. 03Signal level and proofYears, names, numbers. Specific and checkable.

The scan

5–15 s

Is the work real, and is the best of it first?

  1. 04Strongest, most relevant work firstMost visitors see one project. Choose which.
  2. 05Few projects, each one editedYou are judged by the weakest piece you show.
  3. 06Readable at a glanceTitle and one line, always visible. No hover.

One project

15–30 s

What did this person actually do?

  1. 07Say what your part wasRole, team, and client or personal concept.
  2. 08Show one decisionWhat you chose and why, not the process you followed.
  3. 09Show the changeBefore and after, a result, or what shipped.

The exit

After 30 s

How do I reach them, and for what?

  1. 10One clear ask, one way to reach youA visible email and a reason to write.
  2. 11Aimed at somethingAfter 30 seconds, hired for what?

Everything around it

At any moment

Does anything get in the way?

  1. 12Works on a phoneLinks are opened from chats and feeds.
  2. 13Loads fastA slow first screen spends the 30 seconds on nothing.
  3. 14Shares wellThe preview card is seen before the page.
  4. 15Readable by machinesRecruiters search, and ask AI assistants for names.
  5. 16No frictionNo passwords, loaders, dead links or cursor tricks.
  6. 17Always within reachYour name and your email stay on screen at every scroll.
/portfolio-build

Portfolio Build

Turn a folder of work and a few facts about you into a finished portfolio that already passes the 30 seconds.

  • Use it whenYou have the work and no site to show it.
  • Or whenThe audit says the problem is the structure, not the copy.
  • Or whenYou want to see your work in another grid without starting over.
You say

Build my portfolio from this folder. I'm a product designer, aiming at senior fintech roles.

It does
  1. 1Asks only for what it cannot find in what you gave it.
  2. 2Shows you the three grids, says which it would pick and why, and builds the one you choose.
  3. 3Writes the headline, proof and one line per project from your facts.
  4. 4Sets the look from your brand: typeface, colour, corners, spacing.
You get

A finished site in a folder. Nothing to install: change one content file and build again.

The first screen of a portfolio built with the case grid: a large statement, then the first project.

Case grid · 3 projects · 18 pictures

  1. 9"Admin dashboard" does not say what changed or what shipped.
  2. 14No share image for link previews.

It ends by listing, by rule number, what an audit would still flag, so you know what is left.

The grid decides where things go. The look is one small block you own, so two portfolios built this way read the same and look nothing alike.

Three structures that pass the test

Pick a grid

The same example portfolio, built three ways. Each one answers the same question for a different kind of work: in 30 seconds, what does the reviewer need to see?

The index grid: a profile card fixed on the left, the first project large on the right.

Index

Your name, headline and email stay fixed on the left while the work scrolls large on the right.

Best for
Art direction, brand, 3D, illustration.
Seen in the first 5 seconds
Who you are and your first piece, side by side.
The columns grid: a short header with the headline, then two pictures side by side.

Columns

A short header, then every piece at one size, two across. It reads as a body of work.

Best for
Film, motion, photography.
Seen in the first 5 seconds
Your line, then two pieces at once.
The case grid: a large statement, then the first project card.

Case

A large statement, one card per project with its result, and a page each for role, decision and outcome.

Best for
Product, UX, design leadership.
Seen in the first 5 seconds
Your statement at full size, then the first project.