菜单
Use when someone wants to rewrite specific portfolio sections into stronger, senior-level statements — showing Before/After with explanations. Triggers on: "이 문장 고쳐줘", "이 부분 어떻게 쓰면 좋아", "더 잘 쓰는 법", "임팩트 있게 바꿔줘", "rewrite this portfolio section",
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/newkayak12/claude-skills --skill portfolio-rewrite命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a substantial request needs verified, non-repetitive output. Triggers on: "이거 제대로 해줘", "검증까지 해서", "하네스 돌려줘", "run the harness", "do this properly with verification", "6단계로 처리해줘", "메타스크립트로". Not for trivial edits or Q&A.
Use when turning code, docs, notes, or mixed sources into a small-to-moderate, query-efficient Markdown knowledge base with predictable folders, an AI lookup catalog, source-grounded summaries, and RAG-ready metadata.
Use when building knowledge graphs by extracting source-grounded entities, relationships, properties, evidence, schema, and graph-ready data from code, documents, notes, tickets, or mixed corpora.
基于 SOC 职业分类
正在显示 SKILL.md
| name | portfolio-rewrite |
| description | Use when someone wants to rewrite specific portfolio sections into stronger, senior-level statements — showing Before/After with explanations. Triggers on: "이 문장 고쳐줘", "이 부분 어떻게 쓰면 좋아", "더 잘 쓰는 법", "임팩트 있게 바꿔줘", "rewrite this portfolio section", |
| scenarios | ["Rewrite this portfolio bullet point to sound more senior","Make this section show more ownership and impact","I have vague impact claims — help me rewrite them with stronger language","이 문장 더 임팩트 있게 고쳐줘","이 포트폴리오 섹션 시니어 수준으로 리라이팅 해줘"] |
| compatibility | {"recommended":[],"optional":["think-tool"],"remote_mcp_note":"think-tool이 있으면 리라이팅 전 원본 문장의 실제 약점을 진단하는 품질이 높아집니다. Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요."} |
Use when:
Not for:
Paste the specific portfolio passage(s) you want rewritten. If numbers or role context are missing, Claude will ask before rewriting.
| Claude | You |
|---|---|
| Diagnoses what is actually weak in the original (not just "it's vague") | Provides missing facts: actual numbers, your specific role, what changed |
| Produces Before/After with explanation of what changed and why | Validates the rewrite is factually accurate |
| Applies techniques: specificity, ownership language, decision visibility, outcome framing | Decides which version to use |
| Flags when a rewrite needs facts you haven't provided yet | Supplies those facts so rewrites are honest, not fabricated |
../portfolio-pattern/SKILL.md — diagnose patterns before targeted rewriting../portfolio-feedback/SKILL.md — understand which sections to prioritize for rewritingBefore rewriting anything, call think to assess:
If key facts are missing (numbers, your specific role, what changed after), ask for them before rewriting. A well-phrased version of a vague claim is still a vague claim.
🧠 Rewriter note: Record the diagnosis here if it's non-obvious — what was actually wrong with the original, beyond "it's weak."
For each passage, produce:
Before:
[original text, verbatim]
After:
[rewritten version]
왜 더 강해졌는가: Explain in 2–4 sentences: what changed and why it matters to an interviewer. Be specific about the technique used (added metric, changed subject from "we" to "I", surfaced the decision not just the outcome, added failure-and-recovery arc, etc.)
🧠 Rewriter note: [only if the reasoning behind the rewrite was non-obvious or required a real judgment call]
Specificity over generality
Ownership language
Decision, not just action
Outcomes, not activities
Conflict and resolution Senior portfolios that read perfectly smooth feel rehearsed. A sentence that includes what went wrong and how it was resolved is more credible than one that only describes success.