[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3DF90D7RC8ZJE4AW2P9VC":3,"skill-same:01M6D3DF90D7RC8ZJE4AW2P9VC":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},"01M6D3DF90D7RC8ZJE4AW2P9VC","triage",null,"Strategically route orphaned files and extract scattered tasks","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\u002Ftriage\u002FSKILL.md",[],[5,19,20,21,22,23],"tasks","fast","extract","files","route","2026-11-10 10:12:30",false,"---\nname: triage\ndescription: Strategically route orphaned files and extract scattered tasks\nmodel_hint: fast\n---\n\nCleanup and routing tool that finds standalone files and scattered tasks, then suggests where they belong using your current strategic context (Week Priorities + Quarterly Goals).\n\n## Execution Style\n\nThis skill handles quick decisions. Be concise. Don't over-analyze. Make a routing decision and move on. Target: \u003C2 seconds of thinking per item.\n\n## What It Does\n\n- **Files**: Routes standalone files in `00-Inbox\u002F` to projects, person pages, or resource folders\n- **Tasks**: Finds unchecked `- [ ]` tasks scattered across notes and routes them appropriately\n- **Strategic**: Uses your Week Priorities and Quarterly Goals to inform routing confidence\n\n## Usage\n\n- `\u002Ftriage` - Process everything (files + tasks)\n- `\u002Ftriage files` - Organize standalone files only\n- `\u002Ftriage tasks` - Extract and route tasks only\n\n## Arguments\n\n$MODE: Optional. \"files\" | \"tasks\" | \"all\". Default: \"all\"\n\n---\n\n---\n\n## Demo Mode Check\n\nBefore executing, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml` and check `demo_mode`\n2. **If `demo_mode: true`:**\n   - Display: \"Demo Mode Active — Using sample data\"\n   - Use `System\u002FDemo\u002F` paths instead of root paths\n   - Write any output to `System\u002FDemo\u002F` subdirectories\n3. **If `demo_mode: false`:** Use normal vault paths\n\n\n## Step 0: Drop Zone Check\n\nBefore starting triage, check if today's drop zone has unprocessed items:\n\n1. Look for today's drop zone file. Check the new format first, then fall back to legacy:\n   - **New format:** `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD - Drop Zone.md`\n   - **Legacy format:** `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD-Drop-Zone.md`\n   Use whichever exists (prefer new format if both exist).\n2. If the file exists, read it and count entries that do NOT have `✅ Processed`\n3. **If unprocessed items exist:**\n   > \"? You have [X] unprocessed items in your drop zone. Want me to process them first?\"\n   - If user says yes: Run the `\u002Fcapture` workflow, then continue with triage\n   - If user says no or skips: Continue with triage\n4. **If no unprocessed items or file doesn't exist:** Continue silently\n\n---\n\n## Step 1: Load Strategic Context & Structure Discovery\n\nBefore processing inbox items, load strategic context and build an index of existing entities. This makes triage strategically aware and enables intelligent routing.\n\n### 0. Load Strategic Context\n\nRead these files to understand current priorities:\n\n1. **Week Priorities**: `00-Inbox\u002FWeek_Priorities.md`\n   - Extract this week's Top 3 focus items\n   - Note any specific projects\u002Fpeople mentioned\n   - Capture keywords and themes\n\n2. **Quarterly Goals**: `03-Tasks\u002FQuarterly_Goals.md`\n   - Extract current quarter's goals\n   - Note associated projects and outcomes\n   - Capture keywords and themes\n\nThis context will inform routing decisions - entries matching current priorities get higher confidence scoring and are surfaced first.\n\n### 1. Scan Projects\n\nList all files in `04-Projects\u002F`:\n- Extract project name from filename (convert underscores to spaces)\n- Read frontmatter if present for description, status, pillar\n- Build index: `{ name, path, description, status, pillar }`\n\n### 2. Scan People\n\nList all files in `05-Areas\u002FPeople\u002FExternal\u002F` and `05-Areas\u002FPeople\u002FInternal\u002F`:\n- Extract name from filename\n- Read frontmatter\u002Fmetadata table for role, company\n- Build index: `{ name, path, company, role, type: internal|external }`\n\n### 3. Scan Role-Specific Areas\n\nList any additional folders under `05-Areas\u002F` that aren't People or Career:\n- These may be role-specific areas created during setup (e.g., Accounts\u002F, Team\u002F, Content\u002F)\n- Extract relevant names from filenames\n- Build index: `{ name, path, type: area_type }`\n\n### 4. Read Pillars\n\nParse `System\u002Fpillars.yaml`:\n- Extract pillar names, descriptions, and keywords\n- These inform categorization when no entity match is found\n\n---\n\n## Step 0.5: Semantic Matching Enhancement (if QMD available)\n\n**This step activates automatically when QMD is installed.** It dramatically improves routing accuracy by matching inbox items to goals, projects, and people by **meaning**, not just keywords.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\nAfter loading strategic context (Step 0), enhance matching with semantic search:\n\n1. **For each inbox item**, run:\n   ```\n   qmd_search(query=\"[item title + first 100 words of content]\", limit=5)\n   ```\n   This finds vault content related by meaning. \"Email about onboarding flow\" matches \"Q1 goal: improve activation rate\" even though they share no keywords.\n\n2. **For task deduplication**, use semantic similarity instead of keyword overlap:\n   ```\n   qmd_search(query=\"[task description]\", limit=3)\n   ```\n   Catches semantic duplicates: \"Review Q1 metrics\" detected as duplicate of \"Check quarterly pipeline numbers\".\n\n3. **For goal alignment scoring**, run:\n   ```\n   qmd_search(query=\"[item content]\", limit=3)\n   ```\n   against quarterly goals and weekly priorities. Items semantically related to active goals get a +25 confidence boost.\n\n**How this changes matching:**\n\n| Aspect | Without QMD (keyword) | With QMD (semantic) |\n|--------|----------------------|---------------------|\n| Goal matching | Exact keyword overlap only | Meaning-based: \"churn analysis\" matches \"retention goal\" |\n| Duplicate detection | >60% string similarity | Semantic similarity: different words, same intent |\n| Person matching | Name must appear in text | Role\u002Ftitle references found: \"the sales VP\" → Sarah Chen |\n| Project matching | Project name in filename | Thematic connection: \"pricing update\" → \"Acme Deal\" project |\n\n**Merge semantic scores with entity scores** from Step 0. The combined confidence determines routing priority.\n\n**If QMD is not available:** Skip silently. The standard keyword-based matching in the steps below handles routing with existing patterns.\n\n---\n\n## Mode: Files\n\nOrganize standalone files in the `00-Inbox\u002F` folder by suggesting where they belong.\n\n### Process\n\n1. **Scan 00-Inbox\u002F**\n   - List all files (exclude Week Priorities.md, README.md)\n   - Read each file's content\n\n2. **Match Against Strategic Context & Entities**\n\n   For each inbox file, check in this order:\n\n   | Check | Match Criteria | Action | Confidence Boost |\n   |-------|---------------|--------|------------------|\n   | **Week Priority match** | Content relates to this week's Top 3 priorities | Route to associated project\u002Fperson, flag as HIGH priority | +30 points |\n   | **Quarterly Goal match** | Content relates to current quarter's goals | Route to associated project, flag as strategic | +20 points |\n   | **Project match** | File mentions project name, or filename contains project reference | Route to specific project file | +10 points if also matches priority |\n   | **Person match** | File is about a specific person, contains their name prominently | Route to person page OR suggest linking | +10 points if person mentioned in priorities |\n   | **Company match** | File mentions company name, or attendees from known domain | Route to company page in 05-Areas\u002FCompanies\u002F | Base confidence |\n   | **Pillar keyword match** | Content matches pillar keywords | Tag with pillar, suggest relevant category | Base confidence |\n   | **No entity match** | None of the above | Fall back to category routing | Low confidence |\n\n3. **Category Fallback Rules**\n\n   When no specific entity matches, use these rules:\n\n   | Destination | Criteria |\n   |-------------|----------|\n   | `04-Projects\u002F` | Has deadline, specific outcome, time-bound |\n   | `05-Areas\u002F[specific area]\u002F` | Belongs to a role-specific area (Accounts\u002F, Team\u002F, Content\u002F) |\n   | `05-Areas\u002FPeople\u002F` | Person-specific information |\n   | `06-Resources\u002F` | Reference material, knowledge, learnings |\n   | `07-Archives\u002F` | Old\u002Fcompleted, no longer active |\n   | Delete | No value, redundant, or temporary |\n\n4. **Present Suggestions with Strategic & Entity Context**\n\n   Show what was matched, prioritizing items that align with current priorities:\n\n   ```\n   File: [filename]\n   Strategic Context: [Week Priority\u002FQ Goal if matched]\n   Match: [entity type] → [specific entity name]\n   Destination: [exact path]\n   Confidence: [high\u002Fmedium\u002Flow] ([score]\u002F100)\n   Action: [suggested action]\n   ```\n\n   **Sort order:**\n   1. Items matching Week Priorities (highest confidence first)\n   2. Items matching Quarterly Goals\n   3. Items matching known entities (projects, people, companies)\n   4. Generic category routing\n   \n   **Flag misalignments:**\n   - If multiple entries relate to something NOT in priorities\u002Fgoals, surface it: \"You've captured 5 items about [topic]. Consider adding to priorities?\"\n\n5. **Execute with Confirmation**\n   - Show full plan\n   - Wait for user approval\n   - Move files using `mv` (not copy)\n   - For merges, append content to existing file\n\n---\n\n## Mode: Tasks\n\nExtract uncompleted tasks from notes and route them appropriately.\n\n### Process\n\n1. **Scan Sources**\n   - `00-Inbox\u002FMeetings\u002F*.md` - Meeting action items\n   - `00-Inbox\u002F*.md` - Captured tasks\n   - Any file with unchecked tasks `- [ ]`\n\n2. **Extract Tasks**\n   - Find all `- [ ]` items\n   - Note the source file for each\n   - Extract any mentioned names, projects, companies\n\n3. **Match Tasks to Entities**\n\n   For each task:\n   - Check if it mentions a known project → suggest adding to that project\n   - Check if it mentions a known person → suggest linking to person page\n   - Check if it mentions a known company → suggest linking to company\n\n4. **Deduplication Check**\n\n   For each task, check against:\n   - `00-Inbox\u002FWeekly_Plans.md`\n   - `03-Tasks\u002FTasks.md`\n\n   Flag items with >60% similarity to existing tasks.\n\n5. **Ambiguity Detection**\n\n   Flag tasks that are:\n   - Less than 3 words\n   - Match vague patterns (e.g., \"fix bug\", \"follow up\", \"research X\")\n\n   Generate clarification questions for ambiguous items.\n\n6. **Present Results**\n\n   **Ready to Route** (clear, non-duplicate items):\n   - Show suggested destination with entity context\n   - Show pillar if detectable\n   - Show any linked entities\n\n   **Potential Duplicates** (>60% similarity):\n   - Show the existing task it matches\n   - Ask: Skip \u002F Merge \u002F Keep Both\n\n   **Needs Clarification** (ambiguous):\n   - Show the issue\n   - Ask clarifying questions\n   - Wait for user input\n\n7. **Route with Confirmation**\n   - To Week Priorities: Add to `00-Inbox\u002FWeekly_Plans.md`\n   - To Project: Add to relevant project file\n   - To Person: Add to person page's action items\n   - Skip: Don't process\n   - Defer: Leave for later\n\n---\n\n## Mode: All (Default)\n\nProcess all orphaned items:\n1. Load strategic context (Week Priorities + Quarterly Goals)\n2. Run structure discovery (projects, people, companies)\n3. Organize standalone files in `00-Inbox\u002F`\n4. Extract and route scattered unchecked tasks from all notes\n\n---\n\n## Example Output\n\n```\n? Triage Report\n\n=== STRATEGIC CONTEXT ===\nWeek Priorities:\n• Mobile App Launch (beta by Friday)\n• Q2 Planning finalization\n• Sarah's team onboarding\n\nQuarterly Goals:\n• Launch mobile app beta (Q1)\n• Expand into EMEA market (Q2)\n• Build product marketing team (Q1)\n\n=== STRUCTURE DISCOVERED ===\n• 4 projects found in 04-Projects\u002F\n• 12 people found in 05-Areas\u002FPeople\u002F\n• 3 companies found in 05-Areas\u002FCompanies\u002F\n• 3 pillars configured\n\n=== FILES (2) ===\n\n1. \"Screenshot 2026-01-28.png\"\n   Found in: 00-Inbox\u002F\n   Strategic Context: (no automatic match - image file)\n   Suggested: Review manually or describe context\n   \n2. \"Q1_Planning_Notes.md\"\n   Strategic Context: ✓ Week Priority \"Q2 Planning\" (related)\n   Match: PROJECT → \"Q2 Planning\"\n   Destination: 04-Projects\u002FQ2_Planning.md\n   Confidence: MEDIUM (70\u002F100)\n   Action: Merge into Q2 Planning project?\n\n=== TASKS (4) ===\n\n? HIGH PRIORITY - MATCHES WEEK PRIORITIES (1):\n\n1. \"- [ ] Finalize mobile app pricing model\"\n   Found in: 04-Projects\u002FMobile_App_Launch.md\n   Strategic Context: ✓ Week Priority \"Mobile App Launch\" + Q1 Goal\n   Match: Already in correct project\n   Confidence: HIGH (95\u002F100)\n   Action: Extract to Week Priorities for visibility?\n\n? NEEDS ROUTING (2):\n\n2. \"- [ ] Follow up with Sarah about timeline concerns\"\n   Found in: random meeting note\n   Strategic Context: ✓ Week Priority \"Sarah's team onboarding\"\n   Match: PERSON → \"Sarah Chen\"\n   Destination: Add to Sarah's person page action items\n   Confidence: HIGH (85\u002F100)\n\n3. \"- [ ] Review competitor pricing\"\n   Found in: scattered note\n   Strategic Context: (no direct priority match)\n   Match: PILLAR → \"Product Strategy\"\n   Destination: Week Priorities or Tasks.md?\n   Confidence: MEDIUM (60\u002F100)\n\n⚠️ DUPLICATE (1):\n\n4. \"- [ ] Reach out to Sarah\"\n   Found in: old meeting note\n   78% match with existing task in Week Priorities\n   Action: Skip \u002F Merge \u002F Keep both?\n\n=== TASKS (5 items) ===\n\n✅ READY TO ROUTE (3):\n1. \"Follow up with Sarah about Q1 budget\"\n   → Week Priorities\n   Links: People\u002FExternal\u002FSarah_Chen.md\n\n2. \"Prep slides for conference\"\n   → Week Priorities\n   Pillar: Thought Leadership\n\n3. \"Review competitor analysis for Acme deal\"\n   → 04-Projects\u002FAcme_Deal.md (project match)\n   Links: 05-Areas\u002FCompanies\u002FAcme_Corp.md\n\n⚠️ POTENTIAL DUPLICATE (1):\n4. \"Contact Tom about implementation\"\n   → 78% match with \"Reach out to Tom\" in Week Priorities\n   [s]kip \u002F [m]erge \u002F [k]eep both?\n\n❓ NEEDS CLARIFICATION (1):\n5. \"Fix the bug\"\n   - Too vague. Which bug? What system?\n\n---\nProceed with ready items? [y\u002Fn]\n```\n\n---\n\n## How Structure Discovery Evolves\n\nBecause discovery happens at runtime:\n- **New projects** are automatically recognized in the next triage\n- **New people pages** become available for matching\n- **New companies** get detected\n- **Custom folders** you add are included as destinations\n\nNo configuration needed - triage adapts as your structure grows.\n\n---\n\n## Notes\n\n- Never auto-route without confirmation\n- Duplicates require explicit decision\n- Ambiguous items block until clarified\n- Use `mv` not `cp` when moving files\n- Entity matches show confidence level (high\u002Fmedium\u002Flow)\n- Multiple entity matches are shown for user to choose\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark inbox triage as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `triage_completed` and properties:\n- items_processed\n- tasks_extracted\n- files_routed\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n","Cleanup and routing tool that finds standalone files and scattered tasks, then suggests where they belong using your current strategic context (Week Priorities + Quarterly Goals).\n\n## Execution Style\n\nThis skill handles quick decisions. Be concise. Don't over-analyze. Make a routing decision and move on. Target: \u003C2 seconds of thinking per item.\n\n## What It Does\n\n- **Files**: Routes standalone files in `00-Inbox\u002F` to projects, person pages, or resource folders\n- **Tasks**: Finds unchecked `- [ ]` tasks scattered across notes and routes them appropriately\n- **Strategic**: Uses your Week Priorities and Quarterly Goals to inform routing confidence\n\n## Usage\n\n- `\u002Ftriage` - Process everything (files + tasks)\n- `\u002Ftriage files` - Organize standalone files only\n- `\u002Ftriage tasks` - Extract and route tasks only\n\n## Arguments\n\n$MODE: Optional. \"files\" | \"tasks\" | \"all\". Default: \"all\"\n\n---\n\n---\n\n## Demo Mode Check\n\nBefore executing, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml` and check `demo_mode`\n2. **If `demo_mode: true`:**\n   - Display: \"Demo Mode Active — Using sample data\"\n   - Use `System\u002FDemo\u002F` paths instead of root paths\n   - Write any output to `System\u002FDemo\u002F` subdirectories\n3. **If `demo_mode: false`:** Use normal vault paths\n\n\n## Step 0: Drop Zone Check\n\nBefore starting triage, check if today's drop zone has unprocessed items:\n\n1. Look for today's drop zone file. Check the new format first, then fall back to legacy:\n   - **New format:** `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD - Drop Zone.md`\n   - **Legacy format:** `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD-Drop-Zone.md`\n   Use whichever exists (prefer new format if both exist).\n2. If the file exists, read it and count entries that do NOT have `✅ Processed`\n3. **If unprocessed items exist:**\n   > \"? You have [X] unprocessed items in your drop zone. Want me to process them first?\"\n   - If user says yes: Run the `\u002Fcapture` workflow, then continue with triage\n   - If user says no or skips: Continue with triage\n4. **If no unprocessed items or file doesn't exist:** Continue silently\n\n---\n\n## Step 1: Load Strategic Context & Structure Discovery\n\nBefore processing inbox items, load strategic context and build an index of existing entities. This makes triage strategically aware and enables intelligent routing.\n\n### 0. Load Strategic Context\n\nRead these files to understand current priorities:\n\n1. **Week Priorities**: `00-Inbox\u002FWeek_Priorities.md`\n   - Extract this week's Top 3 focus items\n   - Note any specific projects\u002Fpeople mentioned\n   - Capture keywords and themes\n\n2. **Quarterly Goals**: `03-Tasks\u002FQuarterly_Goals.md`\n   - Extract current quarter's goals\n   - Note associated projects and outcomes\n   - Capture keywords and themes\n\nThis context will inform routing decisions - entries matching current priorities get higher confidence scoring and are surfaced first.\n\n### 1. Scan Projects\n\nList all files in `04-Projects\u002F`:\n- Extract project name from filename (convert underscores to spaces)\n- Read frontmatter if present for description, status, pillar\n- Build index: `{ name, path, description, status, pillar }`\n\n### 2. Scan People\n\nList all files in `05-Areas\u002FPeople\u002FExternal\u002F` and `05-Areas\u002FPeople\u002FInternal\u002F`:\n- Extract name from filename\n- Read frontmatter\u002Fmetadata table for role, company\n- Build index: `{ name, path, company, role, type: internal|external }`\n\n### 3. Scan Role-Specific Areas\n\nList any additional folders under `05-Areas\u002F` that aren't People or Career:\n- These may be role-specific areas created during setup (e.g., Accounts\u002F, Team\u002F, Content\u002F)\n- Extract relevant names from filenames\n- Build index: `{ name, path, type: area_type }`\n\n### 4. Read Pillars\n\nParse `System\u002Fpillars.yaml`:\n- Extract pillar names, descriptions, and keywords\n- These inform categorization when no entity match is found\n\n---\n\n## Step 0.5: Semantic Matching Enhancement (if QMD available)\n\n**This step activates automatically when QMD is installed.** It dramatically improves routing accuracy by matching inbox items to goals, projects, and people by **meaning**, not just keywords.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\nAfter loading strategic context (Step 0), enhance matching with semantic search:\n\n1. **For each inbox item**, run:\n   ```\n   qmd_search(query=\"[item title + first 100 words of content]\", limit=5)\n   ```\n   This finds vault content related by meaning. \"Email about onboarding flow\" matches \"Q1 goal: improve activation rate\" even though they share no keywords.\n\n2. **For task deduplication**, use semantic similarity instead of keyword overlap:\n   ```\n   qmd_search(query=\"[task description]\", limit=3)\n   ```\n   Catches semantic duplicates: \"Review Q1 metrics\" detected as duplicate of \"Check quarterly pipeline numbers\".\n\n3. **For goal alignment scoring**, run:\n   ```\n   qmd_search(query=\"[item content]\", limit=3)\n   ```\n   against quarterly goals and weekly priorities. Items semantically related to active goals get a +25 confidence boost.\n\n**How this changes matching:**\n\n| Aspect | Without QMD (keyword) | With QMD (semantic) |\n|--------|----------------------|---------------------|\n| Goal matching | Exact keyword overlap only | Meaning-based: \"churn analysis\" matches \"retention goal\" |\n| Duplicate detection | >60% string similarity | Semantic similarity: different words, same intent |\n| Person matching | Name must appear in text | Role\u002Ftitle references found: \"the sales VP\" → Sarah Chen |\n| Project matching | Project name in filename | Thematic connection: \"pricing update\" → \"Acme Deal\" project |\n\n**Merge semantic scores with entity scores** from Step 0. The combined confidence determines routing priority.\n\n**If QMD is not available:** Skip silently. The standard keyword-based matching in the steps below handles routing with existing patterns.\n\n---\n\n## Mode: Files\n\nOrganize standalone files in the `00-Inbox\u002F` folder by suggesting where they belong.\n\n### Process\n\n1. **Scan 00-Inbox\u002F**\n   - List all files (exclude Week Priorities.md, README.md)\n   - Read each file's content\n\n2. **Match Against Strategic Context & Entities**\n\n   For each inbox file, check in this order:\n\n   | Check | Match Criteria | Action | Confidence Boost |\n   |-------|---------------|--------|------------------|\n   | **Week Priority match** | Content relates to this week's Top 3 priorities | Route to associated project\u002Fperson, flag as HIGH priority | +30 points |\n   | **Quarterly Goal match** | Content relates to current quarter's goals | Route to associated project, flag as strategic | +20 points |\n   | **Project match** | File mentions project name, or filename contains project reference | Route to specific project file | +10 points if also matches priority |\n   | **Person match** | File is about a specific person, contains their name prominently | Route to person page OR suggest linking | +10 points if person mentioned in priorities |\n   | **Company match** | File mentions company name, or attendees from known domain | Route to company page in 05-Areas\u002FCompanies\u002F | Base confidence |\n   | **Pillar keyword match** | Content matches pillar keywords | Tag with pillar, suggest relevant category | Base confidence |\n   | **No entity match** | None of the above | Fall back to category routing | Low confidence |\n\n3. **Category Fallback Rules**\n\n   When no specific entity matches, use these rules:\n\n   | Destination | Criteria |\n   |-------------|----------|\n   | `04-Projects\u002F` | Has deadline, specific outcome, time-bound |\n   | `05-Areas\u002F[specific area]\u002F` | Belongs to a role-specific area (Accounts\u002F, Team\u002F, Content\u002F) |\n   | `05-Areas\u002FPeople\u002F` | Person-specific information |\n   | `06-Resources\u002F` | Reference material, knowledge, learnings |\n   | `07-Archives\u002F` | Old\u002Fcompleted, no longer active |\n   | Delete | No value, redundant, or temporary |\n\n4. **Present Suggestions with Strategic & Entity Context**\n\n   Show what was matched, prioritizing items that align with current priorities:\n\n   ```\n   File: [filename]\n   Strategic Context: [Week Priority\u002FQ Goal if matched]\n   Match: [entity type] → [specific entity name]\n   Destination: [exact path]\n   Confidence: [high\u002Fmedium\u002Flow] ([score]\u002F100)\n   Action: [suggested action]\n   ```\n\n   **Sort order:**\n   1. Items matching Week Priorities (highest confidence first)\n   2. Items matching Quarterly Goals\n   3. Items matching known entities (projects, people, companies)\n   4. Generic category routing\n   \n   **Flag misalignments:**\n   - If multiple entries relate to something NOT in priorities\u002Fgoals, surface it: \"You've captured 5 items about [topic]. Consider adding to priorities?\"\n\n5. **Execute with Confirmation**\n   - Show full plan\n   - Wait for user approval\n   - Move files using `mv` (not copy)\n   - For merges, append content to existing file\n\n---\n\n## Mode: Tasks\n\nExtract uncompleted tasks from notes and route them appropriately.\n\n### Process\n\n1. **Scan Sources**\n   - `00-Inbox\u002FMeetings\u002F*.md` - Meeting action items\n   - `00-Inbox\u002F*.md` - Captured tasks\n   - Any file with unchecked tasks `- [ ]`\n\n2. **Extract Tasks**\n   - Find all `- [ ]` items\n   - Note the source file for each\n   - Extract any mentioned names, projects, companies\n\n3. **Match Tasks to Entities**\n\n   For each task:\n   - Check if it mentions a known project → suggest adding to that project\n   - Check if it mentions a known person → suggest linking to person page\n   - Check if it mentions a known company → suggest linking to company\n\n4. **Deduplication Check**\n\n   For each task, check against:\n   - `00-Inbox\u002FWeekly_Plans.md`\n   - `03-Tasks\u002FTasks.md`\n\n   Flag items with >60% similarity to existing tasks.\n\n5. **Ambiguity Detection**\n\n   Flag tasks that are:\n   - Less than 3 words\n   - Match vague patterns (e.g., \"fix bug\", \"follow up\", \"research X\")\n\n   Generate clarification questions for ambiguous items.\n\n6. **Present Results**\n\n   **Ready to Route** (clear, non-duplicate items):\n   - Show suggested destination with entity context\n   - Show pillar if detectable\n   - Show any linked entities\n\n   **Potential Duplicates** (>60% similarity):\n   - Show the existing task it matches\n   - Ask: Skip \u002F Merge \u002F Keep Both\n\n   **Needs Clarification** (ambiguous):\n   - Show the issue\n   - Ask clarifying questions\n   - Wait for user input\n\n7. **Route with Confirmation**\n   - To Week Priorities: Add to `00-Inbox\u002FWeekly_Plans.md`\n   - To Project: Add to relevant project file\n   - To Person: Add to person page's action items\n   - Skip: Don't process\n   - Defer: Leave for later\n\n---\n\n## Mode: All (Default)\n\nProcess all orphaned items:\n1. Load strategic context (Week Priorities + Quarterly Goals)\n2. Run structure discovery (projects, people, companies)\n3. Organize standalone files in `00-Inbox\u002F`\n4. Extract and route scattered unchecked tasks from all notes\n\n---\n\n## Example Output\n\n```\n? Triage Report\n\n=== STRATEGIC CONTEXT ===\nWeek Priorities:\n• Mobile App Launch (beta by Friday)\n• Q2 Planning finalization\n• Sarah's team onboarding\n\nQuarterly Goals:\n• Launch mobile app beta (Q1)\n• Expand into EMEA market (Q2)\n• Build product marketing team (Q1)\n\n=== STRUCTURE DISCOVERED ===\n• 4 projects found in 04-Projects\u002F\n• 12 people found in 05-Areas\u002FPeople\u002F\n• 3 companies found in 05-Areas\u002FCompanies\u002F\n• 3 pillars configured\n\n=== FILES (2) ===\n\n1. \"Screenshot 2026-01-28.png\"\n   Found in: 00-Inbox\u002F\n   Strategic Context: (no automatic match - image file)\n   Suggested: Review manually or describe context\n   \n2. \"Q1_Planning_Notes.md\"\n   Strategic Context: ✓ Week Priority \"Q2 Planning\" (related)\n   Match: PROJECT → \"Q2 Planning\"\n   Destination: 04-Projects\u002FQ2_Planning.md\n   Confidence: MEDIUM (70\u002F100)\n   Action: Merge into Q2 Planning project?\n\n=== TASKS (4) ===\n\n? HIGH PRIORITY - MATCHES WEEK PRIORITIES (1):\n\n1. \"- [ ] Finalize mobile app pricing model\"\n   Found in: 04-Projects\u002FMobile_App_Launch.md\n   Strategic Context: ✓ Week Priority \"Mobile App Launch\" + Q1 Goal\n   Match: Already in correct project\n   Confidence: HIGH (95\u002F100)\n   Action: Extract to Week Priorities for visibility?\n\n? NEEDS ROUTING (2):\n\n2. \"- [ ] Follow up with Sarah about timeline concerns\"\n   Found in: random meeting note\n   Strategic Context: ✓ Week Priority \"Sarah's team onboarding\"\n   Match: PERSON → \"Sarah Chen\"\n   Destination: Add to Sarah's person page action items\n   Confidence: HIGH (85\u002F100)\n\n3. \"- [ ] Review competitor pricing\"\n   Found in: scattered note\n   Strategic Context: (no direct priority match)\n   Match: PILLAR → \"Product Strategy\"\n   Destination: Week Priorities or Tasks.md?\n   Confidence: MEDIUM (60\u002F100)\n\n⚠️ DUPLICATE (1):\n\n4. \"- [ ] Reach out to Sarah\"\n   Found in: old meeting note\n   78% match with existing task in Week Priorities\n   Action: Skip \u002F Merge \u002F Keep both?\n\n=== TASKS (5 items) ===\n\n✅ READY TO ROUTE (3):\n1. \"Follow up with Sarah about Q1 budget\"\n   → Week Priorities\n   Links: People\u002FExternal\u002FSarah_Chen.md\n\n2. \"Prep slides for conference\"\n   → Week Priorities\n   Pillar: Thought Leadership\n\n3. \"Review competitor analysis for Acme deal\"\n   → 04-Projects\u002FAcme_Deal.md (project match)\n   Links: 05-Areas\u002FCompanies\u002FAcme_Corp.md\n\n⚠️ POTENTIAL DUPLICATE (1):\n4. \"Contact Tom about implementation\"\n   → 78% match with \"Reach out to Tom\" in Week Priorities\n   [s]kip \u002F [m]erge \u002F [k]eep both?\n\n❓ NEEDS CLARIFICATION (1):\n5. \"Fix the bug\"\n   - Too vague. Which bug? What system?\n\n---\nProceed with ready items? [y\u002Fn]\n```\n\n---\n\n## How Structure Discovery Evolves\n\nBecause discovery happens at runtime:\n- **New projects** are automatically recognized in the next triage\n- **New people pages** become available for matching\n- **New companies** get detected\n- **Custom folders** you add are included as destinations\n\nNo configuration needed - triage adapts as your structure grows.\n\n---\n\n## Notes\n\n- Never auto-route without confirmation\n- Duplicates require explicit decision\n- Ambiguous items block until clarified\n- Use `mv` not `cp` when moving files\n- Entity matches show confidence level (high\u002Fmedium\u002Flow)\n- Multiple entity matches are shown for user to choose\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark inbox triage as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `triage_completed` and properties:\n- items_processed\n- tasks_extracted\n- files_routed\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n",{"name":5,"model_hint":20,"description":7},"main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Ftriage",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 triage",{"tool":44,"command":45},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill triage",{"tool":47,"command":48},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",true,[],[53,90,99,113,128,148],{"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],"setup","zoom setup","MCP","distribution","time","granola","scheduling","context","review","surfaces","recordings","process","connect","transcript","search","stats","oauth2","meetings","schedule","confirmation",{"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},[78,107,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","shape","priorities","SET","calendar","goals","task",{"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":138,"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",[134,137],{"categoryNo":135,"categoryName":136,"taxonomyType":62,"taxonomyTypeDesc":63},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},[139,70,140,72,141,82,142,143,144,145,127,146,147],"trello setup","trello","sync","server","api","bun","kanban","visual","token",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":156,"publishedAt":24},"01M6D3D8S2YSHSB0BN73W9HA0W","todoist-setup","Connect Todoist to Amp for two-way task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftodoist-setup\u002FSKILL.md",[154,155],{"categoryNo":135,"categoryName":136,"taxonomyType":62,"taxonomyTypeDesc":63},{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},[157,158,70,159,78,5,141,19,82,160,85,143,121,161,81,162,127,163,164,72],"todoist setup","todoist","daily plan","inbox","system","daily","creation","systems"]