paput-mcp 2.10.1 → 2.10.2

package/dist/cli/skills/paput-public-profile-summary/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: paput-public-profile-summary
-description: Use this to generate and save the user's PaPut public profile summary (headline, profile summary, strength labels) shown on the AI Summary tab to recruiters. Build it only from public materials such as the skill sheet, public memos and notes, and category and growth aggregates. Never use private dashboard analysis or goals.
+description: Use this to generate and save the user's PaPut public profile summary (headline, profile summary, strength labels, and representative project highlights) shown on the AI Summary tab to recruiters. Build it only from public materials such as the skill sheet, public memos and notes, and category and growth aggregates. Never use private dashboard analysis or goals.
 ---
 
 # PaPut Public Profile Summary
@@ -11,7 +11,7 @@ Generate the public profile shown on the AI Summary tab: headline, profile_summa
 
 1. Call `paput_get_public_profile_context`.
 2. Generate the summary from the returned `structuredContent`.
-3. Present the draft in the user's language and tone, and explain what each field will become.
+3. Present the draft in the user's language and tone, including `headline`, `profile_summary`, `strength_labels`, and `project_highlights`. Explain what each field will become.
 4. Do not save unless the user explicitly asks to save it.
 5. If the user asks to save, call `paput_update_skill_sheet_public_profile`.
 6. Verify the saved result with `paput_get_skill_sheet`.
@@ -21,7 +21,7 @@ Generate the public profile shown on the AI Summary tab: headline, profile_summa
 - headline: one-line catchphrase of what the person can do (~100 chars).
 - profile_summary: 3-4 sentence overall summary written for a recruiter. Convey strengths and continuity in prose.
 - strength_labels: top 3-5 strengths. Each has a label, an optional short description, and evidence via `category_names` and `project_ids`.
-- project_highlights: up to 2-3 public-profile project highlights. Each has `project_id`, `title`, `summary` (120-200 Japanese chars or similarly concise in the user's language), optional `strength_labels`, and up to 3 `achievement_bullets`.
+- project_highlights: required when the context contains at least one project with enough material. Include up to 2-3 representative public-profile project highlights. Each has `project_id`, `title`, `summary` (120-200 Japanese chars or similarly concise in the user's language), optional `strength_labels`, and up to 3 `achievement_bullets`.
 
 ## Materials
 
@@ -38,6 +38,10 @@ Use only public materials returned by the context tool:
 - Use public materials only. Never use dashboard analysis or goals; they are private and for the user only.
 - Do not present memo counts as skill proficiency. Activity volume is not mastery.
 - Tie strengths to concrete memos or projects, and do not exaggerate.
+- Generate the `headline`, `profile_summary`, and `strength_labels` first, then select `project_highlights` as evidence that supports that headline and those strengths.
+- If project material exists, always include `project_highlights` in the draft. Do not ask the user whether to add them.
+- Do not list every project. Choose only the 2-3 projects that most strongly justify the generated headline and `strength_labels`.
+- If no project has enough material, set `project_highlights` to an empty array and briefly explain why.
 - Rewrite project highlights for the public AI Summary tab. Do not copy detailed project AI summaries verbatim.
 - Treat project_highlights as evidence for the headline/profile strengths, not as a full skill sheet project history.
 - Keep the tone factual and suitable for a recruiter reading it in a short time.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paput-mcp",
-  "version": "2.10.1",
+  "version": "2.10.2",
   "description": "PaPut MCP Server",
   "main": "dist/index.js",
   "type": "module",