Stats
Actions
Tags
From portfolio
Use when someone shares a portfolio and wants an overall assessment from an interviewer's perspective — overall impression, scoring across dimensions, and prioritized improvement areas. Triggers on: "포트폴리오 피드백 해줘", "내 포트폴리오 어때?", "portfolio review", "how does my portfolio look", "review my portfolio", or when a portfolio is shared without a more specific request. Best for: 5+ year backend engineers wanting an honest overall read; identifying which dimensions (technical depth, ownership, impact narrative) are strongest/weakest. Not for: rewriting specific sections (use portfolio-rewrite), JD matching (use portfolio-jd), live interview practice (use portfolio-interview).
How this skill is triggered — by the user, by Claude, or both
Slash command
/portfolio:portfolio-feedbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Use when:**
Use when:
Not for:
Provide: your portfolio (paste or upload). Optionally specify the target role level and company type for a calibrated review.
| Claude | You |
|---|---|
| Reviews portfolio as selected interviewer persona | Chooses which interviewer persona fits your target company |
| Scores 5 dimensions with specific evidence | Provides missing facts (numbers, your actual role) when requested |
| Lists top 3 improvement priorities — concrete, not generic | Decides which improvements to make before applying |
| Generates 5 expected interview questions from this portfolio | Does the actual interviews and relationship building |
../portfolio-rewrite/SKILL.md — act on specific improvement areas after receiving feedback../portfolio-pattern/SKILL.md — understand writing patterns (passive voice, subject audit) that affect perception../portfolio-interview/SKILL.md — practice answering the expected interview questions../portfolio-company/SKILL.md — identify which companies to target after improvementCall sequentialthinking before reading anything deeply.
Use it to map out:
This step exists because rushed reviews tend to latch onto the first interesting detail and miss the overall pattern. Sequential thinking forces a deliberate read.
After planning, present the following personas to the user and ask them to pick one (or let Claude choose if the user says "you decide"):
"I've seen a thousand portfolios. I'm looking for depth, not breadth. Show me one hard problem you actually owned."
Emphasizes:
Skeptical of: vague impact claims, "participated in" language, stacks that change every project
"I need someone who can lead a team, ship fast, and make good-enough decisions under pressure."
Emphasizes:
Skeptical of: deep specialization with no evidence of breadth, no mention of teammates or collaboration
"Reliability, process maturity, and long-term maintainability are what matter here."
Emphasizes:
Skeptical of: hype-driven stacks with no rationale, missing operational context, no mention of failure or incident handling
"Can you write something other engineers will actually want to use and maintain?"
Emphasizes:
Skeptical of: closed-source-only work, no external technical communication, overly internal focus
Once the persona is selected, stay in character throughout the review. Let the persona's priorities shape what you praise, what you probe, and what questions you ask.
For each major evaluation section, call think before scoring.
Why think first: Quick scoring produces surface-level grades. think forces the question: "Is this actually evidence of what I think it is, or am I pattern-matching to something familiar?" Use it especially when:
When think surfaces a non-obvious insight, record it as an inline annotation immediately below the relevant section:
> 🧠 **Reviewer note**: [the key insight, in 1–2 sentences]
Use these sparingly — only where the reasoning was genuinely difficult or the insight would help the candidate understand why the feedback is what it is. Not every section needs one.
For a 5+ year senior backend engineer, these are the things that actually matter:
Technical Depth Did they use the technology or understand it? The difference shows in whether they describe tradeoffs, encountered limitations, and made deliberate choices — versus listing what was installed.
System Design How did they handle growth, failure, and bottlenecks? Architecture decisions need rationale, not just diagrams. One well-explained design decision is worth ten bullet points of features.
Impact and Results "Improved performance" is table stakes. By how much? Measured how? What changed for the business or users? Senior engineers own outcomes, not just tasks.
Leadership and Ownership Did they propose this, or execute it? Team contributions, mentoring, architecture decisions, incident ownership — the question is whether this person was present or driving.
Portfolio Narrative Is there a story? Why these projects? What was hard? What changed? A list of features is a job description, not a portfolio.
Write the feedback in Korean. Use the structure below, inserting 🧠 Reviewer note annotations where relevant.
[종합 첫인상] Honest first reaction. Would you keep reading? What, if anything, made you stop? One or two sentences that capture the overall signal.
[항목별 평가]
For each dimension: score (out of 10) + evidence from the portfolio + specific improvement direction.
Insert 🧠 Reviewer note below any score where the reasoning was not straightforward.
[인상적이었던 부분 (최대 3개)] Specific, not generic. Not "good technical skills" — say what exactly was impressive and why it signals what you think it signals.
[면접에서 파고들 부분 (최대 3개)] The things you would push on in the actual interview. Claims that feel overstated, roles that seem unclear, or absences that make you wonder.
[예상 면접 질문 5개] The questions a real interviewer with this persona would actually ask — some exploratory, some pointed. These should be useful prep material.
[개선 우선순위 Top 3] If the candidate rewrites one thing tonight, what is it? Concrete and actionable: not "add more detail" but "replace 'improved system performance' with the actual latency numbers and what you changed to get there."
[한 줄 요약] How would you describe this candidate to a hiring manager in one sentence?
Once the overall review is complete, offer the candidate these follow-on skills depending on what they need:
portfolio-rewrite: 약한 문장을 Before/After로 직접 리라이팅portfolio-pattern: 주어 비율, 피동 표현, 숫자 밀도 등 패턴 분석portfolio-interview: 이 포트폴리오 기반 모의 면접 시뮬레이션portfolio-company: 회사 유형별 핏 분석portfolio-jd: JD와 포트폴리오 갭 분석 및 포지셔닝 조언npx claudepluginhub newkayak12/claude-skills --plugin portfolioReviews PM resumes against 10 best practices: professional summary, pronoun avoidance, XYZ+S achievements, keyword optimization, structure, and job tailoring. Includes examples and edits.
Designs interactive portfolios for developers, designers, and creatives that convert visitors into clients and jobs. Covers architecture, hero sections, project showcases, UX patterns, and optimization.
Designs portfolios that convert visitors into opportunities, covering architecture, project showcases, and personal branding for developers, designers, and creatives.