portfolio-page
GitHub用于构建以结果为导向的作品集或案例研究页面。通过结构化的上下文、角色、行动与成果展示工作价值，适用于求职或展示专业能力，强调深度而非广度，避免仅罗列素材。
Trigger Scenarios
Install
npx skills add mohitagw15856/pm-claude-skills --skill portfolio-page -g -y
SKILL.md
Frontmatter
{
"name": "portfolio-page",
"homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/portfolio-page.html",
"metadata": {
"openclaw": {
"emoji": "👤"
}
},
"description": "Structure a portfolio or case-study page that shows your work, not just lists it. Use when asked to write a portfolio page, a project case study, a work showcase, or an 'is this person good?' proof page. Produces a portfolio structure — a positioning header, and per-project case studies (context → your role → what you did → outcome) that demonstrate impact, ready to export as a designed page\/PDF."
}
Portfolio Page Skill
A portfolio fails when it's a gallery of artifacts with no story — the viewer can't tell what you did or whether it worked. This skill structures it as evidence: a clear positioning header, then per-project case studies that walk context → your specific role → what you did → the outcome. It works for PMs, designers, engineers, marketers, founders — any "show me you're good" page.
Required Inputs
Ask for these only if they aren't already provided:
- Who you are & what you want — your positioning and the audience (hiring manager, client, investor).
- The projects — 2–4 of your best, with: the problem, your role, what you did, and the result.
- Proof — metrics, links, visuals, testimonials (whatever's available).
- Constraints — anything confidential/NDA that needs anonymising.
Output Format
[Name] — [positioning headline]
One line on who you are and the value you create; who the page is for; contact/links.
Selected work — 2–4 case studies, strongest first. Each:
[Project name] — [one-line outcome]
- Context: the situation and the problem (brief — set the stage).
- My role: your specific contribution vs. the team's (be honest and clear).
- What I did: the key decisions/actions, not every task — show judgement.
- Outcome: the measurable result (or qualitative if that's all there is), and what you learned.
- Proof: link / visual / metric / quote.
About / how I work (optional) — a short note on approach or values, for fit.
Note (for the user): pick depth over breadth — 3 strong case studies beat 8 thin ones. Anonymise confidential numbers as ranges ("~30% lift") rather than dropping them.
Quality Checks
- Each project is a case study (context → role → action → outcome), not just a title + screenshot
- Your specific role is distinguished from the team's on every project
- Outcomes are stated (quantified where possible), not left implied
- The page leads with positioning so the viewer knows who it's for and what you do
- 2–4 strong projects, newest/most-relevant first — depth over breadth
Anti-Patterns
- Do not list artifacts without the story — a screenshot with no context proves nothing
- Do not blur your contribution into the team's — "we shipped" leaves the viewer unsure what you did
- Do not omit outcomes — "redesigned the flow" without a result is a task, not a case study
- Do not pad with weak projects — each extra mediocre one dilutes the strong ones
- Do not leak confidential data — anonymise to ranges instead of dropping the impact entirely
Based On
Case-study portfolio practice (context · role · action · outcome) used across product, design, and engineering.
Version History
- 54fad50 Current 2026-07-19 12:27
