portfolio
Skill1 starsChanged 4 months agoMITView on GitHub
Plan, build, critique, update, or ship a professional design portfolio as one evidence-backed system. Use when the user invokes /portfolio; needs portfolio positioning, project inventory and selection, personal brand, case studies, homepage/about/contact copy, information architecture, visual direction, website implementation, accessibility, review, or publishing; or wants to turn scattered work into a coherent portfolio for a specific role, client, or audience.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- markbaindesign/bain-studiotheir own version, first seen Nov 8, 2026
- fainir/agent-harnesstheir own version, first seen Nov 1, 2026
- ahmetenesdur/starkfitheir own version, first seen Oct 25, 2026
- Seth090502/osanwe-publictheir own version, first seen Oct 20, 2026
Used with
Projects with it also use risk, ask and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OlayeeeyoSkillrisk
评估当前整体持仓的风险敞口。当用户输入 /risk 时触发。适用场景:"我的持仓有什么风险?" "期权 assignment 风险大吗?" "持仓集中度怎样?
Also in 3 projects that use this
dubwoahSkillask
Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- anthropics/claude-for-legal★ 9.5ksame name
- gauss314/skills★ 242same name
- thesun4sky/jobstack★ 216same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Kanevry/session-orchestrator★ 53same name
- RaoHai/ClaudeQuant★ 8same name
- davidromeo/tradeblocks-skills★ 4same name
- ExarLabs/paros-advisor★ 4same name
- tradeblocks-org/tradeblocks-skills★ 4same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
No mode means build. If a portfolio or project already exists, inspect it before asking for information that can be recovered from the …
- Distinctive: line 47
Treat these as delegated capabilities, not separate reports.
- Distinctive: line 51
Use these sequences as required routes, not suggestions:
- Very specific: line 67
Do not append ship to build.
- Very specific: line 82
Use assets/portfolio-workbook.md when the user needs a persistent artifact across sessions.
- Distinctive: line 93
never invent research, metrics, testimonials, awards, employers, responsibilities, or impact.
- Very specific: line 95
Use [evidence needed: …] for material gaps.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Portfolio Dispatcher
Build a portfolio around what the intended audience must understand and believe. Do not begin with a visual theme or force every project into the same story.
Resolve the mode
Interpret the first argument as a mode when present:
| Call | Outcome |
/portfolio build | Run the full workflow from evidence inventory to validated portfolio |
/portfolio position | Define target audience, promise, differentiators, and proof requirements |
/portfolio inventory | Find and classify usable projects, artifacts, metrics, and testimonials |
/portfolio select | Score projects and choose the smallest credible set |
/portfolio architecture | Create the sitemap, page hierarchy, labels, and content model |
/portfolio case-study | Route one project through /case-study |
/portfolio write | Draft or edit homepage, work-index, about, resume, and contact copy |
/portfolio design | Define or implement the portfolio’s visual and interaction system |
/portfolio audit | Test positioning, evidence, findability, writing, accessibility, and execution |
/portfolio ship | Validate, commit, push, and deploy only with explicit publishing authority |
/portfolio update | Re-run inventory and replace stale or weak evidence without rebuilding everything |
No mode means build. If a portfolio or project already exists, inspect it before asking for information that can be recovered from the files.
Route the installed library
Load only the routes required for the active mode. If the use dispatcher is installed, run its inventory sweep against the active phase so new relevant skills can join later.
| Need | Route |
| Career/studio positioning, niche, expertise signals | designbiz |
| Personal brand, identity, positioning, touchpoints | brand |
| Product, system, or AI project story | case-study |
| Brand-identity project story or precedent | brand-case-studies with case-study |
| Sitemap, labels, project taxonomy, findability | information-architecture-and-navigation |
| Interface direction, design system, layout, polish | design |
| Section-level image direction or generated visuals | imagegen-frontend-web |
| Voice and removal of AI writing patterns | humanizer, after evidence and structure are stable |
| Accessibility and inclusive implementation | accessibility-and-inclusive-design |
| GitHub publication | github:yeet, only after an explicit ship request |
Treat these as delegated capabilities, not separate reports. The portfolio owns the audience, project set, cross-page hierarchy, and proof system; companion skills own their specialized decisions.
Mode plans
Use these sequences as required routes, not suggestions:
| Mode | Ordered plan |
build | position → inventory → select → architecture → case-study for each selected project → write → design → audit → local handoff |
position | designbiz for audience/expertise strategy → brand for personal-brand expression → proof requirements |
inventory | Inspect authorized files and sources → evidence/permission ledger → gap list |
select | Permission gate → PROOF scoring → coverage/redundancy/depth check |
architecture | information-architecture-and-navigation → content model → sitemap → page briefs |
case-study | case-study; add brand-case-studies for identity work |
write | Portfolio page copy → evidence check → humanizer voice pass |
design | design; add imagegen-frontend-web only when meaningful new imagery is needed |
audit | Positioning/evidence gate → rendered findability test → accessibility-and-inclusive-design → execution checks |
ship | audit must pass → github:yeet → configured deployment path |
update | Inventory delta → replace or repair weak proof → rerun affected case-study/page/audit stages |
Do not append ship to build. Run ship only when the user explicitly requests publishing.
Full workflow
- Target and position — name the role, client, or audience; their decision; desired next action; constraints; and proof requirements.
- Inventory — inspect projects, artifacts, metrics, research, screenshots, source files, testimonials, and permissions.
- Select — apply
references/project-selection.md; choose the smallest set that proves the positioning without repetition. - Architect — apply
references/page-system.md; design the content model and sitemap before visual styling. - Build stories — route each selected project through
case-study; do not duplicate its internal framework here. - Write connective copy — draft the homepage, work index, about page, project cards, resume bridge, and contact path.
- Design and implement — route the interface through
design; generate new imagery only when it carries meaning. - Validate — apply
references/portfolio-quality-gate.mdagainst the actual rendered portfolio. - Hand off — leave a verified local artifact and one re-entry step.
- Ship only on request — publish only when the user explicitly invokes or requests the ship phase.
Use assets/portfolio-workbook.md when the user needs a persistent artifact across sessions.
Evidence contract
For every project and portfolio-level claim:
- name the user, organization, or system affected;
- state the designer’s actual ownership and collaborators;
- connect artifacts to decisions, not decoration;
- distinguish shipped outcomes from observations, reports, and proposals;
- mark confidential, redacted, reconstructed, or unavailable evidence;
- never invent research, metrics, testimonials, awards, employers, responsibilities, or impact.
Use [evidence needed: …] for material gaps. A visually strong page does not compensate for unsupported claims.
Output by default
Return or create:
- target-audience and positioning statement;
- evidence inventory;
- scored project shortlist;
- portfolio sitemap and page briefs;
- case-study production queue;
- portfolio-level copy;
- design/build direction;
- validation results and unresolved gaps;
- one next action when work remains.
Example
/portfolio build Inspect my project folders and build a portfolio for senior
AI product design roles. Prioritize systems thinking, agent control, and shipped work.Expected outcome: the skill inventories evidence, selects non-redundant projects, defines positioning and sitemap, routes each selected project through /case-study, builds or directs the site through /design, and reports the executed validation path before calling it ready.
Done
The portfolio is ready only when the actual rendered artifact lets the target audience answer:
- Who is this person, what kind of work do they do, and for whom?
- Which projects best prove that claim?
- What did they own, decide, and change?
- What evidence supports the result?
- Can I find the right depth quickly on desktop, mobile, keyboard, and assistive technology?
- What should I do next, and does that action work?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

