Skills / Portfolio page
Portfolio page
Build the one-page site that goes at the top of the resume. The person's real work with live links, deployed by the end of the sitting. Use when they say "make my portfolio", "I need a personal site", or their resume lists projects with nowhere to see them.
Use this skill. Nothing to install.
Don't have an agent? · Raw file: skills/portfolio-page.md
Watch the first two minutes
This is how a session goes, including the "coming soon" temptation. Click through it.
Scripted example of a real session.
Is two projects really enough?
Yes, when both can be opened by a stranger right now. The skill's rule is that everything on the page must be demoable: a live site, a repo with real commits, a video, a photo of the physical thing. Two or three of those beat six thin ones, and "coming soon" cards are banned outright. If you have zero, the skill says so and sends you to build one first; after that, this page takes about twenty minutes. Projects that read well behind a link:
What you end up with
One page, live at a real URL, that a resume screener lands on and believes. Here is the whole thing; a portfolio at this stage is short, and that is correct.
- The URL is theirs. GitHub Pages under their own username, free, and the same URL goes on the resume header and their GitHub profile before the sitting ends. Email appears only if they are comfortable publishing it; GitHub is contact enough.
- One line about who they are. True, plain, and it frames both projects. No mission statement.
- Blurbs are two sentences in their words. What it is, then what they did. The agent typed the page; the person chose which projects lead and what each blurb says.
- Every link tested before it shipped. The skill verifies each link loads, then the two of you open the page on a phone together. A dead link on a portfolio costs more than a missing project.
Questions people actually ask
Is this free?
The skill is free and so is the hosting: GitHub Pages costs nothing and the URL is yours. The agent you paste the skill into may or may not be free; Gemini has the widest free tier, and the free plans of ChatGPT, Claude, and Copilot can run it.
Do I need to know how to code?
No. The agent writes the HTML and CSS, explains each move in a one-liner as it goes, and keeps the result plain enough that you can read it. Your job is the choices: which projects lead, what each blurb says, what the page feels like.
I have zero finished projects. Can I make the page anyway?
No, and the skill will say so rather than fill the page with promises. Only work that exists goes up, and a project needs something to click. Build one real thing first; the page itself then takes about twenty minutes.
Do I need my own domain name?
No. GitHub Pages under your username gives you a real URL for free, and that is where the session ends. If you later want yourname.com, the custom-domain skill picks up from exactly here.
How do I add my next project?
A two-line edit you watched the agent make the first time: one line for the project, one for the link. The page is static HTML with no framework, so there is nothing to relearn. Finish something, add it, done.
Where to go from here
Page live? Make the things it links to look as good as the page:
Portfolio feeding a job hunt?
Curious? Read the full skill — the exact instructions your agent gets
--- name: portfolio-page category: resume description: Build the one-page site that goes at the top of the resume. The person's real work with live links, deployed by the end of the sitting. Use when they say "make my portfolio", "I need a personal site", or their resume lists projects with nowhere to see them. --- # portfolio-page Build the page a stranger lands on after reading this person's resume. One page, their name on it, their actual work on it, every project clickable. The bar: live at a real URL by the end of the sitting, with nothing on it they cannot demo. ## Ground rules - Only work that exists goes on the page. A project earns a spot by having something to click: a live site, a repo with real commits, a video, a photo of the physical thing. No "coming soon" cards. - Two or three real projects beat six thin ones. If they have zero, say so and point at https://sphinxstack.com/skills/ — build one first, then this page takes twenty minutes. - Their choices, typed by you: which projects lead, what each blurb says, what the page feels like. Explain each move in a one-liner as you make it. - Static HTML/CSS they can read. No framework, no template soup. ## Session shape 1. Inventory: list everything they have made — repos, deployed sites, school projects, physical builds, designs. For each, find the link or artifact that proves it. Keep what proves; park the rest. 2. Blurbs: for each project, two sentences in their words — what it is and what they did — plus the link. Verify every link loads before it goes on the page. 3. Build: name, one line about who they are, contact (GitHub, and email only if they are comfortable publishing it), then the projects. Mobile-readable, fast, no photo required. 4. Deploy: GitHub Pages under their username, so the URL is theirs. Hand off to build-website or ship-on-github if those skills are present — this page is the simplest case of both. 5. Close the loop: put the URL on their resume header and their GitHub profile. Open it on their phone together. ## Done - Live URL with their name, short bio, and 2+ projects - Every project links to something a stranger can open right now - Works on a phone; every link tested - URL added to the resume and anywhere else they list themselves When they ship the next project, adding it here is a two-line edit they watched you make — they can do it themselves.