portfolio-presentation
Curate and present creative/technical work for maximum impact. Structure case studies, craft project narratives, optimize for different audiences (hiring managers, clients, collaborators). Supports portfolio websites, PDF decks, and presentation formats. Triggers on portfolio review, case study writing, project showcase, or work presentation requests.
Best use case
portfolio-presentation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Curate and present creative/technical work for maximum impact. Structure case studies, craft project narratives, optimize for different audiences (hiring managers, clients, collaborators). Supports portfolio websites, PDF decks, and presentation formats. Triggers on portfolio review, case study writing, project showcase, or work presentation requests.
Teams using portfolio-presentation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/portfolio-presentation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How portfolio-presentation Compares
| Feature / Agent | portfolio-presentation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Curate and present creative/technical work for maximum impact. Structure case studies, craft project narratives, optimize for different audiences (hiring managers, clients, collaborators). Supports portfolio websites, PDF decks, and presentation formats. Triggers on portfolio review, case study writing, project showcase, or work presentation requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Portfolio Presentation
Transform scattered work into compelling professional narrative.
## Core Principle
A portfolio isn't a list of projects—it's a story about who you are and what you can do for the person viewing it.
## Audience Analysis
Before curating, identify the viewer:
| Audience | Primary Interest | Time Available | Decision Criteria |
|----------|------------------|----------------|-------------------|
| Hiring Manager | Can you do the job? | 30-90 seconds initial | Relevant skills, growth |
| Technical Lead | How do you think? | 2-5 minutes deep dive | Problem-solving, code quality |
| Client | Can you solve my problem? | 1-2 minutes | Similar work, results |
| Collaborator | Would I enjoy working with you? | Variable | Process, communication |
| Academic | What's your contribution? | Thorough review | Rigor, originality |
## Portfolio Structure
### Homepage/Landing
```
[Hero: Your positioning statement]
[Featured Work: 3-4 best pieces]
[Brief About]
[Contact/CTA]
```
**Positioning Statement Formula**:
```
I'm a [role] who [unique approach/specialty].
I help [audience] achieve [outcome] through [method].
```
### Project Selection
**The 3-5-7 Rule**:
- 3 projects minimum (shows range)
- 5 projects optimal (depth + breadth)
- 7 projects maximum (avoid overwhelm)
**Selection Criteria**:
| Criterion | Weight | Question |
|-----------|--------|----------|
| Relevance | 30% | Does it match target opportunity? |
| Impact | 25% | Can I quantify results? |
| Craft | 20% | Does it showcase my best work? |
| Recency | 15% | Is it current enough? |
| Story | 10% | Is there a compelling narrative? |
### Project Order
1. **Lead with best fit** (not necessarily best work)
2. **Second strongest** (captures attention)
3. **Show range** (different type/scale)
4. **Personal/passion project** (shows personality)
5. **Stretch piece** (aspirational direction)
---
## Case Study Framework
### Quick Format (Portfolio Card)
```markdown
## [Project Name]
**Role**: [Your specific role]
**Timeline**: [Duration]
**Team**: [Size/composition]
[One compelling image]
[2-3 sentence summary: Problem → Solution → Result]
**Key Outcome**: [Single quantified result]
```
### Standard Format (Project Page)
```markdown
# [Project Name]
## Overview
[Elevator pitch: What is it? Who's it for? Why does it matter?]
## The Challenge
[Problem statement with context and stakes]
## My Role
[Specific responsibilities and contributions]
## Process
[Key phases with visuals]
1. Discovery/Research
2. Ideation/Strategy
3. Execution/Implementation
4. Iteration/Refinement
## Solution
[What was built/created with visuals]
## Results
[Quantified outcomes]
- [Metric]: [Before] → [After]
- [Metric]: [Improvement]
## Reflection
[What I learned, what I'd do differently]
```
### Deep Dive Format (Full Case Study)
See `references/case-study-template.md`
---
## Narrative Patterns
### The Transformation Arc
```
Status Quo → Disruption → Struggle → Insight → Resolution → New Normal
```
### The Problem-Solution-Impact
```
[User] was struggling with [problem]
We discovered [insight]
So we built [solution]
Which resulted in [impact]
```
### The Process Story
```
We started by [research/discovery]
Which revealed [key insight]
Leading us to [design decision]
Through [iteration], we arrived at [solution]
```
### The Constraint Story
```
Given [constraints: time/budget/tech]
We had to [creative approach]
Which taught us [lesson]
And delivered [outcome despite constraints]
```
---
## Visual Presentation
### Image Requirements
| Type | Purpose | Specs |
|------|---------|-------|
| Hero | First impression | 16:9 or 4:3, high-res |
| Process | Show thinking | Annotated, clear |
| Detail | Craft quality | Cropped, focused |
| Before/After | Show impact | Side-by-side |
| Context | Real-world use | In-situ photos |
### Screenshot Best Practices
- Show real data (anonymized if needed)
- Browser chrome optional (clean vs. context)
- Highlight key interactions
- Include mobile views if responsive
- Show states: empty, loading, populated, error
### Video/Animation
When to use:
- Complex interactions
- Time-based experiences
- Before/after transformations
- Process documentation
Keep under 60 seconds for portfolio context.
---
## Writing Guidelines
### Headlines
❌ "E-commerce Website Redesign"
✅ "Increasing Conversion 40% Through Checkout Simplification"
### Descriptions
❌ "I designed the UI and implemented the frontend"
✅ "Led design and development of checkout flow that reduced cart abandonment from 68% to 41%"
### Quantification
| Weak | Strong |
|------|--------|
| Improved performance | Reduced load time from 4.2s to 0.8s |
| Increased engagement | Grew DAU 3x over 6 months |
| Better user experience | NPS improved from 32 to 67 |
### Voice
- First person for personal sites ("I designed...")
- First person plural for team work ("We discovered...")
- Active voice always
- Present tense for live work, past for completed
---
## Format-Specific Guidance
### Portfolio Website
See `references/website-structure.md`
### PDF Portfolio
See `references/pdf-portfolio.md`
### Presentation Deck
See `references/deck-structure.md`
---
## Review Checklist
### Content
- [ ] Positioning statement is clear
- [ ] Projects match target audience
- [ ] Each project has quantified results
- [ ] Story arc is compelling
- [ ] Role/contribution is explicit
### Visual
- [ ] Images are high quality
- [ ] Consistent visual style
- [ ] Mobile-friendly (if web)
- [ ] Load time acceptable
### Technical
- [ ] All links work
- [ ] Contact info current
- [ ] SEO basics covered (if web)
- [ ] Analytics installed (if web)
### Polish
- [ ] Proofread for errors
- [ ] Consistent formatting
- [ ] Fresh eyes review
---
---
## Related Skills
### Complementary Skills (Use Together)
- **[cv-resume-builder](../cv-resume-builder/)** - Build a resume to accompany your portfolio
- **[interview-preparation](../interview-preparation/)** - Prepare to discuss portfolio projects in interviews
- **[brand-guidelines](../brand-guidelines/)** - Create consistent visual identity across portfolio
### Alternative Skills (Similar Purpose)
- None - this is the primary portfolio presentation skill
### Prerequisite Skills (Learn First)
- None required - this is a standalone professional skill
---
## References
- `references/case-study-template.md` - Full case study format
- `references/website-structure.md` - Portfolio website architecture
- `references/pdf-portfolio.md` - PDF portfolio best practices
- `references/deck-structure.md` - Presentation deck formatRelated Skills
workshop-presentation-design
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
webhook-integration-patterns
Designs reliable webhook systems with proper delivery guarantees, retry logic, signature verification, and idempotent processing for event-driven integrations.