[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D34A29K0VF2N2K03EJ3897":3,"skill-same:01M6D34A29K0VF2N2K03EJ3897":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M6D34A29K0VF2N2K03EJ3897","amp-level-up",null,"Discover unused Amp features based on your usage patterns","hemory\u002Famp-legacy-do-not-use","hemory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21179881?v=4","01M6D31HFJ391DN8N0JP8AQGFE","Hemory Phifer","01M6D31HKXVTEN27AT6R4PP2ZJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Famp-level-up\u002FSKILL.md",[],[19,20,21,22,23],"level up","up","amp level up","patterns","discover","2026-11-10 10:12:30",false,"---\nname: amp-level-up\ndescription: Discover unused Amp features based on your usage patterns\n---\n\n## Purpose\n\nDiscover Amp capabilities you haven't used yet. No FOMO — this is your concierge showing you what's available so you can get full value from the system without missing features.\n\n---\n\n## Step 1: Check Usage Log\n\nRead `System\u002Fusage_log.md` to understand what features the user has adopted.\n\n---\n\n## Step 2: Analyze Patterns\n\nLook for natural progressions and gaps:\n\n### Progression Patterns\n\n**Daily → Weekly → Quarterly:**\n- Using `\u002Fdaily-plan` but not `\u002Fweek-plan`? → Suggest weekly planning\n- Using `\u002Fweek-plan` but not `\u002Fquarter-plan`? → Suggest quarterly goals\n\n**Meeting Capture → Relationship Tracking:**\n- Processing meetings but no person pages? → Suggest person pages\n- Have person pages but not company pages? → Suggest processing meetings to auto-create company pages in 05-Areas\u002FCompanies\u002F\n\n**Tasks → Projects:**\n- Managing tasks but no project pages? → Suggest project tracking\n- Have projects but not using `\u002Fproject-health`? → Suggest health checks\n\n**Basic → Advanced:**\n- Comfortable with core workflows? → Suggest journaling, learning capture\n- Using all features consistently? → Suggest custom MCPs, system improvements\n\n### Role-Based Relevance\n\nPrioritize suggestions based on user's role (from `System\u002Fuser-profile.yaml`):\n\n**Product Managers:**\n- `\u002Fproduct-brief` for feature ideation\n- Project tracking for initiative management\n- Relationship tracking for stakeholder management\n\n**Engineering:**\n- Project tracking for sprint\u002Fmilestone management\n\n**Sales\u002FCustomer Success:**\n- Person pages for customer context\n- Relationship tracking for account management\n- Meeting prep for sales calls\n\n**Leadership:**\n- Quarterly planning for strategic thinking\n- Weekly reviews for team synthesis\n- Learning capture for pattern recognition\n\n---\n\n## Step 2.5: Check for Role-Specific Skills\n\nAfter analyzing universal feature usage, check for role-specific skills:\n\n### Identify User's Role Group\n\n1. Read `System\u002Fuser-profile.yaml` → `role` field\n2. Map role to role_group using this mapping:\n   - **product:** Product Manager, CPO, Product Ops, Fractional CPO\n   - **sales:** Sales, Account Executive, CRO, RevOps\n   - **marketing:** Marketing, CMO\n   - **finance:** Finance, CFO\n   - **engineering:** Engineering, CTO, Solutions Engineering\n   - **customer_success:** Customer Success, CCO\n   - **operations:** Product Ops, RevOps, BizOps, Data\u002FAnalytics\n   - **leadership:** CEO, Founder, C-Suite roles\n   - **design:** Design\n   - **support:** People (HR), Legal, IT Support, CHRO, CLO, CIO, CISO\n   - **advisory:** Consultant, Coach, Venture Capital\u002FPrivate Equity\n\n### Check Available Skills\n\n1. List files in `.claude\u002Fskills\u002F_available\u002F[role_group]\u002F`\n2. For each available skill directory, read its SKILL.md and extract:\n   - name (from frontmatter)\n   - description (from frontmatter)\n   - jtbd (from frontmatter)\n   - time_investment (from frontmatter)\n\n### Check Installed Skills\n\n1. List files in `.claude\u002Fskills\u002F`\n2. Cross-reference with available skills to determine which are not yet installed\n\n### Present Role Skills (if any uninstalled)\n\nIf there are uninstalled role-specific skills, include this section in the output:\n\n```markdown\n---\n\n## ? Role-Specific Skills for [Role Name]\n\nYou haven't installed role-specific skills yet. Here's what's available for [role_group] roles:\n\n### \u002F[skill-name]\n**Job to be done:** [JTBD from frontmatter]\n**Time investment:** [time_investment from frontmatter]\n\n[Repeat for each available uninstalled skill]\n\n---\n\n**Want to install these skills?** \n\nSay:\n- **\"install all\"** to add all [X] skills\n- **\"install [skill-name]\"** to add specific skills\n- **\"tell me more about [skill-name]\"** to learn more before installing\n```\n\n### Installation Workflow\n\nWhen user says \"install [skill]\" or \"install all\":\n\n1. **Verify skill exists** in `.claude\u002Fskills\u002F_available\u002F[role_group]\u002F[skill-name]\u002F`\n2. **Copy skill folder:**\n   ```bash\n   cp -r .claude\u002Fskills\u002F_available\u002F[role_group]\u002F[skill-name]\u002F .claude\u002Fskills\u002F[skill-name]\u002F\n   ```\n3. **Confirm to user:** \"✓ Installed `\u002F[skill-name]` - try it now!\"\n4. **Update usage log:** Add the skill to the \"Role-Specific Skills\" section in `System\u002Fusage_log.md` (see Step 5 for format)\n5. **If installing multiple:** Show progress for each skill\n\n**Important:** Only copy the skill folder itself (not the parent role_group folder). The skill should end up at `.claude\u002Fskills\u002F[skill-name]\u002FSKILL.md`, not `.claude\u002Fskills\u002F[role_group]\u002F[skill-name]\u002FSKILL.md`.\n\n---\n\n## Step 3: Integration Discovery\n\nCheck for connected integrations and surface opportunities the user may be missing.\n\n### Unused Capabilities (Already Connected)\n\nRead `System\u002Fintegrations\u002Fconfig.yaml` and check each enabled integration for underutilized features:\n\n**For each enabled integration, check if all capabilities are active:**\n\n- **Gmail connected** but `email_followup: false`?\n  → \"You have Gmail connected but haven't enabled follow-up detection. It flags emails waiting for replies — useful in `\u002Fdaily-plan`.\"\n\n- **Gmail connected** but `newsletter_digest: false`?\n  → \"Gmail is connected but newsletter digests aren't enabled. It summarizes your morning newsletters so you can skim instead of read.\"\n\n- **Todoist\u002FThings connected** but `\u002Fprocess-inbox` doesn't route to it?\n  → \"You have [Tool] connected but inbox processing doesn't route tasks to it yet. Want to enable two-way sync so tasks land in both places?\"\n\n- **Jira connected** but `sprint_tracking: false`?\n  → \"Jira is connected but sprint tracking isn't active. It would pull sprint items into your `\u002Fdaily-plan`.\"\n\n- **Zoom connected** but Granola also active?\n  → \"You have both Zoom and Granola — Granola already captures meetings. Zoom's main added value is scheduling. Working as expected?\"\n\nPresent any findings as a section:\n\n```markdown\n## Untapped Integration Features\n\nYou have [X] integrations connected. Here are features you haven't turned on yet:\n\n- **Gmail follow-up detection** — Surfaces emails waiting for replies in your daily plan.\n  → Enable: Edit `System\u002Fintegrations\u002Fconfig.yaml` → `google-workspace.email_followup: true`\n\n- **[Other unused feature]** — [Brief value prop].\n  → Enable: [Specific instruction]\n```\n\nIf all features of all connected integrations are active, skip this section.\n\n### Missing Integrations (Not Connected)\n\nCheck if the user's vault has mentions of tools they haven't connected:\n\n- Search vault files for references to Slack, Todoist, Google Calendar, Zoom, etc.\n- If significant mentions found that aren't already connected:\n\n```markdown\n## Tool Connections You Might Want\n\nI scanned your notes and found references to tools you haven't connected:\n\n- **[Name]** — [mentions] references across your notes ([example files])\n  → [value proposition]\n  → Connect with `[setup command]` ([setupTime] setup)\n\n[Repeat for each high_value item, max 3]\n```\n\nIf no high_value items found, skip this section entirely. Don't show moderate or available items here — keep `\u002Famp-level-up` focused on high-signal recommendations only.\n\n---\n\n## Step 4: Generate Recommendations\n\nShow **2-3 specific, actionable suggestions** ranked by:\n\n1. **Natural next step:** Builds on what they're already doing\n2. **High value:** Would significantly improve their workflow\n3. **Low friction:** Easy to try without disrupting flow\n\n### Recommendation Format\n\nFor each suggestion:\n\n```markdown\n### {{Feature Name}} - {{Why it matters}}\n\n**What you're missing:** {{Brief explanation}}\n\n**Why now:** {{Why this is relevant based on their usage}}\n\n**How to start:** {{Specific command or action}}\n\n**Time investment:** {{2 minutes \u002F 10 minutes \u002F ongoing}}\n```\n\n---\n\n## Step 5: Present Recommendations\n\nDisplay in this format:\n\n```markdown\n# ? Level Up Your Amp System\n\nBased on your usage, here are **{{X}} ways to get more value** from Amp:\n\n---\n\n## 1. {{Feature Name}}\n\n**What you're missing:** {{Explanation}}\n\n**Why it's relevant:** {{Context from their usage}}\n\n**How to start:** {{Command or action}}\n\n**Time:** {{Investment}}\n\n---\n\n## 2. {{Feature Name}}\n\n[Same format]\n\n---\n\n## 3. {{Feature Name}}\n\n[Same format]\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n\n---\n\n*Run `\u002Famp-level-up` anytime to see what else you might be missing.*\n```\n\n---\n\n## Step 6: Track Adoption (Silent)\n\nWhen user tries a recommended feature, silently update `System\u002Fusage_log.md` by checking the box for that feature.\n\n**Update triggers:**\n- User runs a command → Check command box\n- User creates person page → Check person page box\n- User creates project → Check project tracking box\n- Work MCP tools used → Check task boxes\n- **User installs role-specific skill** → Check \"Installed\" box in Role-Specific Skills section\n- **User runs role-specific skill** → Check \"Used\" box in Role-Specific Skills section\n\n**Update method:**\n- Simple find\u002Freplace: `- [ ] Feature` → `- [x] Feature`\n- No announcement needed\n\n**Role-Specific Skills Tracking:**\n\nWhen user installs a role-specific skill, add it to `System\u002Fusage_log.md` if the \"Role-Specific Skills\" section doesn't exist:\n\n```markdown\n## Role-Specific Skills\n\n**Installed:**\n- [x] \u002F[skill-name]\n\n**Used:**\n- [ ] \u002F[skill-name]\n```\n\nIf section exists, just check the appropriate boxes for the skill.\n\n---\n\n## Examples\n\n### Example 1: Daily User, No Weekly Planning\n\n```markdown\n# ? Level Up Your Amp System\n\nBased on your usage, here are **3 ways to get more value** from Amp:\n\n---\n\n## 1. Weekly Planning - Think Bigger Picture\n\n**What you're missing:** You've been crushing daily plans (42 days straight! ?), but you're planning day-to-day without a weekly view. Weekly planning helps you think bigger than today's tasks.\n\n**Why it's relevant:** Consistent daily planning shows you value structure. Weekly planning is the natural next step — it makes your daily plans even better because you're working toward clear weekly outcomes.\n\n**How to start:** Run `\u002Fweek-plan` on Monday morning (or Friday evening). Set your Top 3 priorities for the week. Then when you run `\u002Fdaily-plan`, I'll show how today's work connects to those weekly goals.\n\n**Time:** 5-10 minutes once per week\n\n---\n\n## 2. Person Pages - Never Walk Into Meetings Cold\n\n**What you're missing:** You mention people in your notes, but you don't have person pages yet. Person pages aggregate everything about someone — meeting history, open items, context — so you're never scrambling before calls.\n\n**Why it's relevant:** You have 12 meetings this week. Right now, you're probably trying to remember what you discussed last time. With person pages, I can show you that context automatically in `\u002Fdaily-plan` and `\u002Fmeeting-prep`.\n\n**How to start:** Just say \"Create a person page for [name]\" and I'll set it up. Or next time you mention someone in a meeting note, I'll offer to create their page automatically.\n\n**Time:** 2 minutes per person, one-time setup\n\n---\n\n## 3. Weekly Review - Spot Patterns You're Missing\n\n**What you're missing:** You're planning every week, but you're not reviewing what happened. Weekly reviews help you spot patterns (energy, challenges, wins) that aren't obvious day-to-day.\n\n**Why it's relevant:** After 6 weeks of weekly planning, you have data. A weekly review surfaces insights like \"I'm always blocked on Fridays\" or \"My best work happens Tuesday mornings.\" That knowledge helps you plan better.\n\n**How to start:** Run `\u002Fweek-review` on Friday afternoon or Sunday evening. I'll analyze your week, show patterns, and suggest adjustments.\n\n**Time:** 10-15 minutes once per week\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n```\n\n### Example 2: Power User, Advanced Features\n\n```markdown\n# ? Level Up Your Amp System\n\nYou're using Amp like a pro. Here are **2 advanced features** that could push your system even further:\n\n---\n\n## 1. Custom MCP Integration - Connect Your CRM\n\n**What you're missing:** You're tracking relationships manually, but your CRM already has this data. A custom MCP could sync deal status, contact info, and interaction history automatically.\n\n**Why it's relevant:** You've built 23 person pages and you're consistent with relationship tracking. Automating the data sync would save you 15-20 minutes per week and ensure your Amp system stays in sync with your CRM.\n\n**How to start:** Run `\u002Fcreate-mcp` and tell me which CRM you use (Salesforce, HubSpot, etc.). I'll guide you through creating a custom MCP server that pulls data automatically.\n\n**Time:** 30-45 minutes setup, saves 15-20 min\u002Fweek ongoing\n\n---\n\n## 2. Learning Synthesis - Turn Experience Into Knowledge\n\n**What you're missing:** You've captured 47 session learnings, but you haven't synthesized them into durable knowledge yet. Learning synthesis turns \"I made this mistake\" into \"Here's the principle I learned.\"\n\n**Why it's relevant:** You have a goldmine of captured experience. Running `\u002Fsave-insight` regularly would turn those raw learnings into a knowledge base you can reference and share.\n\n**How to start:** Run `\u002Fsave-insight` after finishing a complex project or at the end of each month. I'll help you extract patterns from your session learnings and write them into `06-Resources\u002FLearnings\u002F`.\n\n**Time:** 10 minutes per insight, quarterly or as-needed\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n```\n\n---\n\n## Special Cases\n\n### If Usage Log is Empty\n\n> \"Looks like you're just getting started! Let me show you the core workflows that most people find valuable first...\"\n\nThen show the essentials:\n1. Daily planning\n2. Task management\n3. Meeting capture\n\n### If Everything is Checked\n\n> \"You're using every feature in Amp! ?\n> \n> At this point, consider:\n> - Building custom MCPs for your specific workflow\n> - Running `\u002Famp-improve` to suggest system enhancements\n> - Sharing what you've learned — your setup could help others\"\n\n### If User Says \"Show Me Everything\"\n\n> \"I could, but that's overwhelming. Let me show you the next 2-3 features that make sense based on where you are.\n> \n> If you want to browse everything, check out:\n> - `CLAUDE.md` for the full system overview\n> - `.claude\u002Fcommands\u002F` folder for all available commands\n> - `06-Resources\u002FAmp_System\u002FAmp_System_Guide.md` for the complete guide\"\n\n---\n\n## Capturing Your Own Ideas\n\nAfter showing recommendations, also mention:\n\n> ---\n> \n> **? Have your own ideas for improving Amp?**\n> \n> Use the `capture_idea` MCP tool anytime you think \"I wish Amp did X\".\n> \n> Your ideas get ranked by:\n> - Impact on your daily workflow\n> - Fit with your usage patterns\n> - Implementation effort\n> - Synergy with existing features\n> \n> Run `\u002Famp-backlog` to see your ideas ranked, or `\u002Famp-improve` to workshop one.\n> \n> *The system helps you systematically improve your PKM over time.*\n\n---\n\n## Integration with Other Commands\n\n### In `\u002Fdaily-plan`:\n\nIf user hasn't run `\u002Famp-level-up` in 7+ days and has unused features, add a gentle nudge:\n\n```markdown\n---\n\n? **Tip:** You're using {{X}} of {{Y}} Amp features. Run `\u002Famp-level-up` to see what you might be missing.\n```\n\n### After Onboarding:\n\nAt the end of `\u002Fsetup`, mention:\n\n> \"One more thing: run `\u002Famp-level-up` anytime to discover features you haven't tried yet. No FOMO — just helpful guidance on what's available.\"\n\n---\n\n## Track Usage (Silent)\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `level_up_viewed` and properties:\n- `features_suggested`\n- `features_unknown_count`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Philosophy\n\nThis command exists to reduce **feature blindness** — when users don't know what they don't know.\n\n**Not pushy:** Only suggest 2-3 things at a time\n**Contextual:** Based on their actual usage patterns\n**Progressive:** Natural next steps, not overwhelming options\n**Helpful:** Genuine concierge service, not annoying nudges\n\nThe goal: Get users to full value as fast as possible without interrupting their flow.\n","## Purpose\n\nDiscover Amp capabilities you haven't used yet. No FOMO — this is your concierge showing you what's available so you can get full value from the system without missing features.\n\n---\n\n## Step 1: Check Usage Log\n\nRead `System\u002Fusage_log.md` to understand what features the user has adopted.\n\n---\n\n## Step 2: Analyze Patterns\n\nLook for natural progressions and gaps:\n\n### Progression Patterns\n\n**Daily → Weekly → Quarterly:**\n- Using `\u002Fdaily-plan` but not `\u002Fweek-plan`? → Suggest weekly planning\n- Using `\u002Fweek-plan` but not `\u002Fquarter-plan`? → Suggest quarterly goals\n\n**Meeting Capture → Relationship Tracking:**\n- Processing meetings but no person pages? → Suggest person pages\n- Have person pages but not company pages? → Suggest processing meetings to auto-create company pages in 05-Areas\u002FCompanies\u002F\n\n**Tasks → Projects:**\n- Managing tasks but no project pages? → Suggest project tracking\n- Have projects but not using `\u002Fproject-health`? → Suggest health checks\n\n**Basic → Advanced:**\n- Comfortable with core workflows? → Suggest journaling, learning capture\n- Using all features consistently? → Suggest custom MCPs, system improvements\n\n### Role-Based Relevance\n\nPrioritize suggestions based on user's role (from `System\u002Fuser-profile.yaml`):\n\n**Product Managers:**\n- `\u002Fproduct-brief` for feature ideation\n- Project tracking for initiative management\n- Relationship tracking for stakeholder management\n\n**Engineering:**\n- Project tracking for sprint\u002Fmilestone management\n\n**Sales\u002FCustomer Success:**\n- Person pages for customer context\n- Relationship tracking for account management\n- Meeting prep for sales calls\n\n**Leadership:**\n- Quarterly planning for strategic thinking\n- Weekly reviews for team synthesis\n- Learning capture for pattern recognition\n\n---\n\n## Step 2.5: Check for Role-Specific Skills\n\nAfter analyzing universal feature usage, check for role-specific skills:\n\n### Identify User's Role Group\n\n1. Read `System\u002Fuser-profile.yaml` → `role` field\n2. Map role to role_group using this mapping:\n   - **product:** Product Manager, CPO, Product Ops, Fractional CPO\n   - **sales:** Sales, Account Executive, CRO, RevOps\n   - **marketing:** Marketing, CMO\n   - **finance:** Finance, CFO\n   - **engineering:** Engineering, CTO, Solutions Engineering\n   - **customer_success:** Customer Success, CCO\n   - **operations:** Product Ops, RevOps, BizOps, Data\u002FAnalytics\n   - **leadership:** CEO, Founder, C-Suite roles\n   - **design:** Design\n   - **support:** People (HR), Legal, IT Support, CHRO, CLO, CIO, CISO\n   - **advisory:** Consultant, Coach, Venture Capital\u002FPrivate Equity\n\n### Check Available Skills\n\n1. List files in `.claude\u002Fskills\u002F_available\u002F[role_group]\u002F`\n2. For each available skill directory, read its SKILL.md and extract:\n   - name (from frontmatter)\n   - description (from frontmatter)\n   - jtbd (from frontmatter)\n   - time_investment (from frontmatter)\n\n### Check Installed Skills\n\n1. List files in `.claude\u002Fskills\u002F`\n2. Cross-reference with available skills to determine which are not yet installed\n\n### Present Role Skills (if any uninstalled)\n\nIf there are uninstalled role-specific skills, include this section in the output:\n\n```markdown\n---\n\n## ? Role-Specific Skills for [Role Name]\n\nYou haven't installed role-specific skills yet. Here's what's available for [role_group] roles:\n\n### \u002F[skill-name]\n**Job to be done:** [JTBD from frontmatter]\n**Time investment:** [time_investment from frontmatter]\n\n[Repeat for each available uninstalled skill]\n\n---\n\n**Want to install these skills?** \n\nSay:\n- **\"install all\"** to add all [X] skills\n- **\"install [skill-name]\"** to add specific skills\n- **\"tell me more about [skill-name]\"** to learn more before installing\n```\n\n### Installation Workflow\n\nWhen user says \"install [skill]\" or \"install all\":\n\n1. **Verify skill exists** in `.claude\u002Fskills\u002F_available\u002F[role_group]\u002F[skill-name]\u002F`\n2. **Copy skill folder:**\n   ```bash\n   cp -r .claude\u002Fskills\u002F_available\u002F[role_group]\u002F[skill-name]\u002F .claude\u002Fskills\u002F[skill-name]\u002F\n   ```\n3. **Confirm to user:** \"✓ Installed `\u002F[skill-name]` - try it now!\"\n4. **Update usage log:** Add the skill to the \"Role-Specific Skills\" section in `System\u002Fusage_log.md` (see Step 5 for format)\n5. **If installing multiple:** Show progress for each skill\n\n**Important:** Only copy the skill folder itself (not the parent role_group folder). The skill should end up at `.claude\u002Fskills\u002F[skill-name]\u002FSKILL.md`, not `.claude\u002Fskills\u002F[role_group]\u002F[skill-name]\u002FSKILL.md`.\n\n---\n\n## Step 3: Integration Discovery\n\nCheck for connected integrations and surface opportunities the user may be missing.\n\n### Unused Capabilities (Already Connected)\n\nRead `System\u002Fintegrations\u002Fconfig.yaml` and check each enabled integration for underutilized features:\n\n**For each enabled integration, check if all capabilities are active:**\n\n- **Gmail connected** but `email_followup: false`?\n  → \"You have Gmail connected but haven't enabled follow-up detection. It flags emails waiting for replies — useful in `\u002Fdaily-plan`.\"\n\n- **Gmail connected** but `newsletter_digest: false`?\n  → \"Gmail is connected but newsletter digests aren't enabled. It summarizes your morning newsletters so you can skim instead of read.\"\n\n- **Todoist\u002FThings connected** but `\u002Fprocess-inbox` doesn't route to it?\n  → \"You have [Tool] connected but inbox processing doesn't route tasks to it yet. Want to enable two-way sync so tasks land in both places?\"\n\n- **Jira connected** but `sprint_tracking: false`?\n  → \"Jira is connected but sprint tracking isn't active. It would pull sprint items into your `\u002Fdaily-plan`.\"\n\n- **Zoom connected** but Granola also active?\n  → \"You have both Zoom and Granola — Granola already captures meetings. Zoom's main added value is scheduling. Working as expected?\"\n\nPresent any findings as a section:\n\n```markdown\n## Untapped Integration Features\n\nYou have [X] integrations connected. Here are features you haven't turned on yet:\n\n- **Gmail follow-up detection** — Surfaces emails waiting for replies in your daily plan.\n  → Enable: Edit `System\u002Fintegrations\u002Fconfig.yaml` → `google-workspace.email_followup: true`\n\n- **[Other unused feature]** — [Brief value prop].\n  → Enable: [Specific instruction]\n```\n\nIf all features of all connected integrations are active, skip this section.\n\n### Missing Integrations (Not Connected)\n\nCheck if the user's vault has mentions of tools they haven't connected:\n\n- Search vault files for references to Slack, Todoist, Google Calendar, Zoom, etc.\n- If significant mentions found that aren't already connected:\n\n```markdown\n## Tool Connections You Might Want\n\nI scanned your notes and found references to tools you haven't connected:\n\n- **[Name]** — [mentions] references across your notes ([example files])\n  → [value proposition]\n  → Connect with `[setup command]` ([setupTime] setup)\n\n[Repeat for each high_value item, max 3]\n```\n\nIf no high_value items found, skip this section entirely. Don't show moderate or available items here — keep `\u002Famp-level-up` focused on high-signal recommendations only.\n\n---\n\n## Step 4: Generate Recommendations\n\nShow **2-3 specific, actionable suggestions** ranked by:\n\n1. **Natural next step:** Builds on what they're already doing\n2. **High value:** Would significantly improve their workflow\n3. **Low friction:** Easy to try without disrupting flow\n\n### Recommendation Format\n\nFor each suggestion:\n\n```markdown\n### {{Feature Name}} - {{Why it matters}}\n\n**What you're missing:** {{Brief explanation}}\n\n**Why now:** {{Why this is relevant based on their usage}}\n\n**How to start:** {{Specific command or action}}\n\n**Time investment:** {{2 minutes \u002F 10 minutes \u002F ongoing}}\n```\n\n---\n\n## Step 5: Present Recommendations\n\nDisplay in this format:\n\n```markdown\n# ? Level Up Your Amp System\n\nBased on your usage, here are **{{X}} ways to get more value** from Amp:\n\n---\n\n## 1. {{Feature Name}}\n\n**What you're missing:** {{Explanation}}\n\n**Why it's relevant:** {{Context from their usage}}\n\n**How to start:** {{Command or action}}\n\n**Time:** {{Investment}}\n\n---\n\n## 2. {{Feature Name}}\n\n[Same format]\n\n---\n\n## 3. {{Feature Name}}\n\n[Same format]\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n\n---\n\n*Run `\u002Famp-level-up` anytime to see what else you might be missing.*\n```\n\n---\n\n## Step 6: Track Adoption (Silent)\n\nWhen user tries a recommended feature, silently update `System\u002Fusage_log.md` by checking the box for that feature.\n\n**Update triggers:**\n- User runs a command → Check command box\n- User creates person page → Check person page box\n- User creates project → Check project tracking box\n- Work MCP tools used → Check task boxes\n- **User installs role-specific skill** → Check \"Installed\" box in Role-Specific Skills section\n- **User runs role-specific skill** → Check \"Used\" box in Role-Specific Skills section\n\n**Update method:**\n- Simple find\u002Freplace: `- [ ] Feature` → `- [x] Feature`\n- No announcement needed\n\n**Role-Specific Skills Tracking:**\n\nWhen user installs a role-specific skill, add it to `System\u002Fusage_log.md` if the \"Role-Specific Skills\" section doesn't exist:\n\n```markdown\n## Role-Specific Skills\n\n**Installed:**\n- [x] \u002F[skill-name]\n\n**Used:**\n- [ ] \u002F[skill-name]\n```\n\nIf section exists, just check the appropriate boxes for the skill.\n\n---\n\n## Examples\n\n### Example 1: Daily User, No Weekly Planning\n\n```markdown\n# ? Level Up Your Amp System\n\nBased on your usage, here are **3 ways to get more value** from Amp:\n\n---\n\n## 1. Weekly Planning - Think Bigger Picture\n\n**What you're missing:** You've been crushing daily plans (42 days straight! ?), but you're planning day-to-day without a weekly view. Weekly planning helps you think bigger than today's tasks.\n\n**Why it's relevant:** Consistent daily planning shows you value structure. Weekly planning is the natural next step — it makes your daily plans even better because you're working toward clear weekly outcomes.\n\n**How to start:** Run `\u002Fweek-plan` on Monday morning (or Friday evening). Set your Top 3 priorities for the week. Then when you run `\u002Fdaily-plan`, I'll show how today's work connects to those weekly goals.\n\n**Time:** 5-10 minutes once per week\n\n---\n\n## 2. Person Pages - Never Walk Into Meetings Cold\n\n**What you're missing:** You mention people in your notes, but you don't have person pages yet. Person pages aggregate everything about someone — meeting history, open items, context — so you're never scrambling before calls.\n\n**Why it's relevant:** You have 12 meetings this week. Right now, you're probably trying to remember what you discussed last time. With person pages, I can show you that context automatically in `\u002Fdaily-plan` and `\u002Fmeeting-prep`.\n\n**How to start:** Just say \"Create a person page for [name]\" and I'll set it up. Or next time you mention someone in a meeting note, I'll offer to create their page automatically.\n\n**Time:** 2 minutes per person, one-time setup\n\n---\n\n## 3. Weekly Review - Spot Patterns You're Missing\n\n**What you're missing:** You're planning every week, but you're not reviewing what happened. Weekly reviews help you spot patterns (energy, challenges, wins) that aren't obvious day-to-day.\n\n**Why it's relevant:** After 6 weeks of weekly planning, you have data. A weekly review surfaces insights like \"I'm always blocked on Fridays\" or \"My best work happens Tuesday mornings.\" That knowledge helps you plan better.\n\n**How to start:** Run `\u002Fweek-review` on Friday afternoon or Sunday evening. I'll analyze your week, show patterns, and suggest adjustments.\n\n**Time:** 10-15 minutes once per week\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n```\n\n### Example 2: Power User, Advanced Features\n\n```markdown\n# ? Level Up Your Amp System\n\nYou're using Amp like a pro. Here are **2 advanced features** that could push your system even further:\n\n---\n\n## 1. Custom MCP Integration - Connect Your CRM\n\n**What you're missing:** You're tracking relationships manually, but your CRM already has this data. A custom MCP could sync deal status, contact info, and interaction history automatically.\n\n**Why it's relevant:** You've built 23 person pages and you're consistent with relationship tracking. Automating the data sync would save you 15-20 minutes per week and ensure your Amp system stays in sync with your CRM.\n\n**How to start:** Run `\u002Fcreate-mcp` and tell me which CRM you use (Salesforce, HubSpot, etc.). I'll guide you through creating a custom MCP server that pulls data automatically.\n\n**Time:** 30-45 minutes setup, saves 15-20 min\u002Fweek ongoing\n\n---\n\n## 2. Learning Synthesis - Turn Experience Into Knowledge\n\n**What you're missing:** You've captured 47 session learnings, but you haven't synthesized them into durable knowledge yet. Learning synthesis turns \"I made this mistake\" into \"Here's the principle I learned.\"\n\n**Why it's relevant:** You have a goldmine of captured experience. Running `\u002Fsave-insight` regularly would turn those raw learnings into a knowledge base you can reference and share.\n\n**How to start:** Run `\u002Fsave-insight` after finishing a complex project or at the end of each month. I'll help you extract patterns from your session learnings and write them into `06-Resources\u002FLearnings\u002F`.\n\n**Time:** 10 minutes per insight, quarterly or as-needed\n\n---\n\n## Want to try one now?\n\nJust say the number or feature name, and I'll guide you through it.\n```\n\n---\n\n## Special Cases\n\n### If Usage Log is Empty\n\n> \"Looks like you're just getting started! Let me show you the core workflows that most people find valuable first...\"\n\nThen show the essentials:\n1. Daily planning\n2. Task management\n3. Meeting capture\n\n### If Everything is Checked\n\n> \"You're using every feature in Amp! ?\n> \n> At this point, consider:\n> - Building custom MCPs for your specific workflow\n> - Running `\u002Famp-improve` to suggest system enhancements\n> - Sharing what you've learned — your setup could help others\"\n\n### If User Says \"Show Me Everything\"\n\n> \"I could, but that's overwhelming. Let me show you the next 2-3 features that make sense based on where you are.\n> \n> If you want to browse everything, check out:\n> - `CLAUDE.md` for the full system overview\n> - `.claude\u002Fcommands\u002F` folder for all available commands\n> - `06-Resources\u002FAmp_System\u002FAmp_System_Guide.md` for the complete guide\"\n\n---\n\n## Capturing Your Own Ideas\n\nAfter showing recommendations, also mention:\n\n> ---\n> \n> **? Have your own ideas for improving Amp?**\n> \n> Use the `capture_idea` MCP tool anytime you think \"I wish Amp did X\".\n> \n> Your ideas get ranked by:\n> - Impact on your daily workflow\n> - Fit with your usage patterns\n> - Implementation effort\n> - Synergy with existing features\n> \n> Run `\u002Famp-backlog` to see your ideas ranked, or `\u002Famp-improve` to workshop one.\n> \n> *The system helps you systematically improve your PKM over time.*\n\n---\n\n## Integration with Other Commands\n\n### In `\u002Fdaily-plan`:\n\nIf user hasn't run `\u002Famp-level-up` in 7+ days and has unused features, add a gentle nudge:\n\n```markdown\n---\n\n? **Tip:** You're using {{X}} of {{Y}} Amp features. Run `\u002Famp-level-up` to see what you might be missing.\n```\n\n### After Onboarding:\n\nAt the end of `\u002Fsetup`, mention:\n\n> \"One more thing: run `\u002Famp-level-up` anytime to discover features you haven't tried yet. No FOMO — just helpful guidance on what's available.\"\n\n---\n\n## Track Usage (Silent)\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `level_up_viewed` and properties:\n- `features_suggested`\n- `features_unknown_count`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Philosophy\n\nThis command exists to reduce **feature blindness** — when users don't know what they don't know.\n\n**Not pushy:** Only suggest 2-3 things at a time\n**Contextual:** Based on their actual usage patterns\n**Progressive:** Natural next steps, not overwhelming options\n**Helpful:** Genuine concierge service, not annoying nudges\n\nThe goal: Get users to full value as fast as possible without interrupting their flow.\n",{"name":5,"description":7},"main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Famp-level-up",0,"https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use","https:\u002F\u002Fgithub.com\u002Fhemory","https:\u002F\u002Fwww.heminthehat.com\u002F","The People Developer | L&D Program Manager | Software Engineer","2026-06-04 23:46:30",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill amp-level-up",{"tool":44,"command":45},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill amp-level-up",{"tool":47,"command":48},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill amp-level-up","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Famp-level-up\u002FSKILL.md",true,[],[53,90,99,113,128,140],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":69,"publishedAt":24},"01M6D3DVEAHJTTK4W21B15ZZKK","zoom-setup","Connect Zoom to Amp for meeting recordings, scheduling, and transcript context","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzoom-setup\u002FSKILL.md",[59,64],{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"zoom setup","setup","schedule","MCP","review","connect","transcript","search","stats","oauth2","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":24},"01M6D3DRAK8VWESYDZDF8JJDSH","xray","Understand what just happened under the hood - learn AI by seeing it in action","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxray\u002FSKILL.md",[],[92,97,98],"learn","just",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":24},"01M6D3DN7BZQDY6143A2QSDP9A","week-review","Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-review\u002FSKILL.md",[105],{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},[107,74,108,109,110,111,112],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":24},"01M6D3DJ7F1TCFXBBSTQW82WE7","week-plan","Set weekly priorities and plan the week ahead with intelligent suggestions based on goals, calendar shape, and task effort.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-plan\u002FSKILL.md",[],[120,121,122,123,124,125,126,127],"week plan","plan","calendar","SET","shape","goals","task","priorities",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":24},"01M6D3DF90D7RC8ZJE4AW2P9VC","triage","Strategically route orphaned files and extract scattered tasks","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[130,135,136,137,138,139],"tasks","fast","extract","files","route",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":150,"publishedAt":24},"01M6D3DC9BBHK5TASE34SQYXSQ","trello-setup","Connect Trello to Amp for visual Kanban task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":62,"taxonomyTypeDesc":63},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},[151,152,71,153,75,73,154,126,155,156,157,158,159],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]