[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C22ACXHVH5167GFPGASA92":3,"skill-same:01M6C22ACXHVH5167GFPGASA92":109},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":13,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M6C22ACXHVH5167GFPGASA92","inbox-setup",null,"One-time setup skill that builds a personalized inbox triage knowledge base via interactive interview. Interviews the user about their email patterns, business context, reply style, and priorities using grill-me discipline (one question at a time, forcing format where possible, dependency-ordered, each question explains why I'm asking), then generates the knowledge base files that power the companion 'inbox-triage' skill. Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly. Triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management', 'set up inbox triage', 'onboard email triage', or any variation where someone wants to get the email triage system running for the first time.","mne20114-hash\u002Fgest35bi","mne20114-hash","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224168109?v=4","01M6C0JCR7334CZ39YWTZXX2NG","01M6C0JCWN0NBWMQTW1CPG2Z4G",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"setup","inbox setup","inbox","onboard","kb","business","interview","interactive","initialize","question","system","configure","knowledge","pricing","first","SET","email","file","inbox triage","change","2026-11-10 10:12:30",false,"---\nname: inbox-setup\ndescription: \"One-time setup skill that builds a personalized inbox triage knowledge base via interactive interview. Interviews the user about their email patterns, business context, reply style, and priorities using grill-me discipline (one question at a time, forcing format where possible, dependency-ordered, each question explains why I'm asking), then generates the knowledge base files that power the companion 'inbox-triage' skill. Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly. Triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management', 'set up inbox triage', 'onboard email triage', or any variation where someone wants to get the email triage system running for the first time.\"\nlicense: MIT\nmetadata:\n  source_spec: \"megaprompts\u002F06-inbox-setup-megaprompt.md\"\n  build_pattern: \"Path B (direct conversion)\"\n  paired_with: \"inbox-triage (shared 7-file KB contract)\"\n  version: 1.0.0\n---\n\n# Inbox-Setup — Email Triage Onboarding\n\n> **Paired with `inbox-triage`.** This skill writes the 7-file knowledge base at `${WORKSPACE}\u002FEmail\u002F` that `inbox-triage` reads on every run. The file contracts (names, sections, fields) MUST match between the two skills exactly. See [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md).\n\nRun once (or re-run when business\u002Fpriorities change). Interview the user about their email patterns, business context, reply style, and priorities. Generate the structured knowledge base in `${WORKSPACE}\u002FEmail\u002F` that captures everything `inbox-triage` needs to process the inbox effectively.\n\n## Invocation Triggers\n\n- \"set up my inbox\"\n- \"configure inbox triage\"\n- \"set up my email system\"\n- \"configure email triage\"\n- \"build my email knowledge base\"\n- \"initialize email management\"\n- \"set up inbox triage\"\n- \"onboard email triage\"\n\n## Conduct Discipline\n\n**Do NOT generate all files at once.** Walk through the 8 sections one at a time. Each section commits its file(s) before moving on. Partial completion (e.g., user drops off mid-interview) still produces a usable partial KB.\n\nGrill-me discipline applies throughout:\n\n- **One question per turn.** Never bundle. Even across section boundaries.\n- **\"Why I'm asking\" on every question** — so users can answer well.\n- **Forcing format where possible.** Multi-choice > open-ended.\n- **Dependency-ordered.** Q2 depends on Q1; downstream sections depend on upstream.\n\nSee [`references\u002Fgrill_me_section_walk.md`](references\u002Fgrill_me_section_walk.md) for the 8-section discipline detail.\n\n## Knowledge Base Contract — Files To Produce\n\nExactly these files at `${WORKSPACE}\u002FEmail\u002F`:\n\n| File | Purpose | Required? |\n|---|---|---|\n| `email-taxonomy.md` | Classification system + report preferences | **Yes** |\n| `email-patterns.md` | Reply voice, tone, templates, hard rules | **Yes** |\n| `evaluation-framework.md` | Decision tree for opportunity emails | Only if user receives pitches\u002Fopportunities |\n| `rate-card.md` | Pricing, terms, negotiation posture | Only if user has pricing |\n| `blocklist.md` | Auto-skip senders + learned decline patterns | **Yes** (seeded, grows over time) |\n| `tracker.md` | Active follow-ups, overdue items, deadlines | **Yes** (starts mostly empty) |\n| `triage-log\u002F` | Directory for per-run logs | **Yes** (created empty) |\n\nThe contract is identical to what `inbox-triage` expects — see [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) for the full spec.\n\n## Stop Condition (Full Interview)\n\n~25–31 questions total across the 8 sections (depending on skip-logic). Hard ceiling: 35 questions including all sub-clarifications. Section 4 (Evaluation Framework) is skipped entirely when Section 1 surfaced no opportunity-email category, dropping the total by 6 questions and the rate-card file. After Section 8's confirmation + handoff message, intake is closed — **never re-open it**. To change preferences later, the user re-runs the skill (which detects existing files and asks per-file: replace \u002F merge \u002F skip). The grill-me one-at-a-time rule applies across section boundaries: do NOT batch questions even when moving from S{n} to S{n+1}.\n\n## Section 1: The Big Picture\n\nSix grill-me questions, one at a time:\n\n- **S1.Q1:** \"What do you do? Give me your role and business in 1–2 sentences. *Why I'm asking:* Context shapes what email patterns to expect — a solo creator's inbox looks nothing like an enterprise PM's.\"\n- **S1.Q2:** \"What dominates your inbox? Pick the top 1–2: sales pitches \u002F client work \u002F internal team \u002F newsletters \u002F customer support \u002F financial \u002F other. *Why I'm asking:* Dominant categories drive the taxonomy.\"\n- **S1.Q3:** \"Rough volume split — e.g., '60% business inquiries, 20% ops, 20% noise'. *Why I'm asking:* The split tells me where to focus triage effort.\"\n- **S1.Q4:** \"Which email address(es) should triage cover? *Why I'm asking:* If multiple, I'll set up per-address taxonomies.\"\n- **S1.Q5:** \"Run frequency: once daily \u002F 2x daily \u002F 3x daily \u002F on-demand only? *Why I'm asking:* Drives the default search window in triage (9h overlap for 2x\u002Fday).\"\n- **S1.Q6:** \"Anyone helping manage email — assistant, VA, team — or solo? *Why I'm asking:* Persona handling differs for delegated inboxes.\"\n\n**Action:** Build mental model. Do NOT write files yet. Note whether opportunity emails are a category (drives S4 skip-logic).\n\n## Section 2: Email Categories\n\nPropose 5–7 categories based on Section 1 — pre-recommend a subset, not the whole template menu:\n\n- New Opportunities\n- Active Conversations\n- Action Required\n- Financial\n- Important\u002FPersonal\n- Informational\n- Ignore\u002FLow Priority\n\nThen three forcing questions, one at a time:\n\n- **S2.Q1:** \"Here's my proposed taxonomy: [list]. Does this match your inbox reality — yes \u002F mostly \u002F no? *Why I'm asking:* If 'no', I need to redo the taxonomy before any other section makes sense.\"\n- **S2.Q2:** \"Missing categories? List them. (Skip if none.) *Why I'm asking:* Missing categories produce uncategorized emails downstream, which hurts triage quality.\"\n- **S2.Q3:** \"Which category takes the MOST time per email? *Why I'm asking:* That's where draft-reply effort needs to focus most.\"\n\n**Action:** Generate `email-taxonomy.md` with categories, signals (for each: trigger phrases \u002F sender patterns \u002F subject markers), and default actions per category.\n\n## Section 3: Reply Style & Voice\n\nSix grill-me questions plus the critical sample request:\n\n- **S3.Q1:** \"Register: formal \u002F casual \u002F in-between? *Why I'm asking:* Calibrates default voice; we'll refine from samples next.\"\n- **S3.Q2:** \"Three communication pet peeves — phrases you hate, openings you avoid. *Why I'm asking:* I treat these as forbidden tokens in drafts.\"\n- **S3.Q3:** \"Phrases or sign-offs you always use — list as many as come to mind. *Why I'm asking:* These are your voice fingerprints.\"\n- **S3.Q4:** \"Different persona for different contexts — e.g., assistant replies as you? *Why I'm asking:* Persona context changes pronoun + signature handling.\"\n- **S3.Q5:** \"Typical reply length — one-liner \u002F short paragraph \u002F longer? *Why I'm asking:* Length is the easiest voice signal to get wrong.\"\n- **S3.Q6:** \"Hard rules — never X \u002F always Y? (E.g., never emojis, always reply within 24h, never take calls without context.) *Why I'm asking:* Hard rules are enforced as non-negotiable in every draft.\"\n\n### S3.SAMPLES (the critical highest-quality input)\n\n> **Paste 3–5 real sent emails from your inbox.**\n>\n> *Why I'm asking:* Self-description of voice is unreliable. Real samples are the best signal — I'll analyze them for voice patterns that supplement everything above. Use `scripts\u002Fvoice_sample_analyzer.py` to extract patterns deterministically.\n\nIf user runs a business: also ask about media kits, rate sheets, standard pitches, repeated replies.\n\n**Action:** Generate `email-patterns.md` with tone description (with do\u002Fdon't examples), persona rules, templates, signatures, hard rules. See [`references\u002Fvoice_calibration.md`](references\u002Fvoice_calibration.md) for the sample-extraction discipline.\n\n## Section 4: Evaluation Framework (Conditional)\n\n**Skip-logic:** only run this section if Section 1 surfaced opportunity emails as a meaningful inbox category. Otherwise jump straight to Section 5.\n\nSix grill-me questions, one at a time:\n\n- **S4.Q1:** \"First thing you check when pitched something — give me your gut filter. *Why I'm asking:* That's the top of the decision tree.\"\n- **S4.Q2:** \"Three instant deal-breakers — things that make you decline immediately. *Why I'm asking:* These become PASS-auto signals.\"\n- **S4.Q3:** \"Three things that make you immediately interested. *Why I'm asking:* These become TAKE-IT signals.\"\n- **S4.Q4:** \"Standard pricing \u002F terms — or 'no fixed pricing' if you negotiate every time. *Why I'm asking:* If you have a rate card, I'll generate one; if not, I'll skip.\"\n- **S4.Q5:** \"Negotiation posture: firm \u002F flexible \u002F depends on context? *Why I'm asking:* Drives draft tone on counter-offers.\"\n- **S4.Q6:** \"VIP senders or organizations that always get engagement — list names or domains. *Why I'm asking:* VIP list bypasses normal PASS filters.\"\n\n**Action:** Generate `evaluation-framework.md` (decision tree + recommendation categories + VIP list) AND `rate-card.md` if pricing exists.\n\n## Section 5: Blocklist & Patterns\n\nThree grill-me questions, one at a time:\n\n- **S5.Q1:** \"Senders or domains to always skip — list them. (Skip if none.) *Why I'm asking:* Auto-blocklist saves the most time per run.\"\n- **S5.Q2:** \"Patterns in emails you always delete — e.g., 'unsubscribe' links from specific marketers, recruiter cold outreach, newsletters? *Why I'm asking:* Patterns let triage auto-skip variants without exact-match maintenance.\"\n- **S5.Q3:** \"Specific companies \u002F recruiters \u002F newsletters wasting time — list any. *Why I'm asking:* These seed the blocklist; triage will add more as you override decisions.\"\n\n**Action:** Generate `blocklist.md` (auto-maintained by triage thereafter).\n\n## Section 6: Current State\n\nThree grill-me questions, one at a time:\n\n- **S6.Q1:** \"Active threads you're tracking — list with one-line context each. (Skip if none.) *Why I'm asking:* These become tracker entries so triage knows existing context.\"\n- **S6.Q2:** \"Overdue replies — anything you should have responded to but haven't? *Why I'm asking:* Triage flags these as priority every run until resolved.\"\n- **S6.Q3:** \"Time-sensitive items with deadlines — list with dates. *Why I'm asking:* Tracker enforces deadlines and surfaces them as overdue at the right time.\"\n\n**Action:** Generate `tracker.md` with active follow-ups table, overdue section, resolved section (empty), update log (empty). Also create empty `triage-log\u002F` directory.\n\n## Section 7: Report Preferences\n\nThree grill-me questions, one at a time:\n\n- **S7.Q1:** \"Delivery format — pick one: email draft to self \u002F file in workspace \u002F chat summary only. *Why I'm asking:* The triage report goes here every run.\"\n- **S7.Q2:** \"Detail level — pick one: 30-second scan \u002F detailed breakdown \u002F both (scan first, expand on request). *Why I'm asking:* Affects report length.\"\n- **S7.Q3:** \"Anything always shown first — e.g., overdue payments, VIP messages? *Why I'm asking:* Custom 'top-of-report' rules surface what you care about above standard sections.\"\n\n**Action:** Save these preferences into `email-taxonomy.md` under a \"Report Preferences\" section.\n\n## Section 8: Confirmation & Handoff\n\nList every file created with one-sentence summary. Then:\n\n> Your triage system is ready. Run the **inbox-triage** skill to process your inbox. First runs need oversight — system learns from your edits and overrides.\n\nRemind: re-run this setup anytime business\u002Fpricing\u002Fpriorities change.\n\nRun `scripts\u002Fkb_validator.py --workspace ${WORKSPACE}` to confirm the 7-file contract is satisfied before final handoff.\n\n## Privacy Boundary\n\n**Never persist passwords, full account numbers, SSNs, or other sensitive credentials in knowledge base files.** If the user volunteers such info during the interview, acknowledge it but don't store it; the relevant KB file gets `[stored separately by user]` in its place.\n\n## Re-Run Behavior\n\nRe-running on an existing setup:\n\n1. Detect `${WORKSPACE}\u002FEmail\u002F`\n2. For each existing file, ask per-file: **replace \u002F merge \u002F skip**\n3. Walk only the sections whose files the user chose to update\n4. Skip sections whose files the user kept\n\n## Error Handling\n\n| Situation | Behavior |\n|---|---|\n| Workspace inaccessible | Stop. Tell user where files would go and ask for permission\u002Fpath |\n| User refuses to share samples | Use self-description; flag in patterns file that calibration may need iteration |\n| User says \"skip this\" mid-interview | Honor it; flag the gap in the file as `[needs follow-up]` |\n| Sensitive info volunteered | Acknowledge but don't persist; note in file as `[stored separately by user]` |\n| Re-run on existing setup | Detect existing files; ask user per-file: replace, merge, skip |\n| User has no pricing \u002F opportunities | Skip Section 4 entirely; don't create empty files |\n\n## Portability\n\n- **Claude Code CLI:** Native — writes markdown files directly to filesystem.\n- **Claude.ai web:** Works with project files \u002F artifacts. Document the alternate path: generate files as artifacts, instruct user to save to their workspace, or use connected file system if available.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fkb_validator.py` | Validates the 7-file KB output (required files present, conditional files only if their sections ran, headers + structure correct). |\n| `scripts\u002Fsection_progress_tracker.py` | JSON-backed walk state at `~\u002F.inbox_setup_sessions\u002F\u003Csession>.json`. Tracks active section, answered questions, committed files. |\n| `scripts\u002Fvoice_sample_analyzer.py` | Extracts voice patterns from pasted sent-email samples — opening phrases, sign-offs, length distribution, register markers. |\n\n## References\n\n- [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — the canonical 7-file contract (write perspective; mirror lives in `inbox-triage\u002Freferences\u002F`)\n- [`references\u002Fgrill_me_section_walk.md`](references\u002Fgrill_me_section_walk.md) — 8-section discipline, skip-logic, commit-per-section\n- [`references\u002Fvoice_calibration.md`](references\u002Fvoice_calibration.md) — sample-based voice extraction theory + anti-patterns\n\n## Anti-Patterns To Reject\n\n- Generating all files at once instead of walking through sections\n- Asking all questions in one batch\n- Hardcoded provider references (Gmail-only thinking)\n- Persisting sensitive credentials in knowledge base\n- Skipping the \"why this question matters\" explanation\n- Skipping the sample-emails ask for voice (it's the highest-quality input)\n- Overwriting existing files without consent on re-run\n- Forcing creation of `rate-card.md` or `evaluation-framework.md` when they don't apply\n\n---\n\n**Version:** 1.0.0\n**Source spec:** `megaprompts\u002F06-inbox-setup-megaprompt.md` (maintainer-local draft spec — gitignored, not present in the public repository)\n**Build pattern:** Path B (direct conversion). Paired with `inbox-triage`.\n","# Inbox-Setup — Email Triage Onboarding\n\n> **Paired with `inbox-triage`.** This skill writes the 7-file knowledge base at `${WORKSPACE}\u002FEmail\u002F` that `inbox-triage` reads on every run. The file contracts (names, sections, fields) MUST match between the two skills exactly. See [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md).\n\nRun once (or re-run when business\u002Fpriorities change). Interview the user about their email patterns, business context, reply style, and priorities. Generate the structured knowledge base in `${WORKSPACE}\u002FEmail\u002F` that captures everything `inbox-triage` needs to process the inbox effectively.\n\n## Invocation Triggers\n\n- \"set up my inbox\"\n- \"configure inbox triage\"\n- \"set up my email system\"\n- \"configure email triage\"\n- \"build my email knowledge base\"\n- \"initialize email management\"\n- \"set up inbox triage\"\n- \"onboard email triage\"\n\n## Conduct Discipline\n\n**Do NOT generate all files at once.** Walk through the 8 sections one at a time. Each section commits its file(s) before moving on. Partial completion (e.g., user drops off mid-interview) still produces a usable partial KB.\n\nGrill-me discipline applies throughout:\n\n- **One question per turn.** Never bundle. Even across section boundaries.\n- **\"Why I'm asking\" on every question** — so users can answer well.\n- **Forcing format where possible.** Multi-choice > open-ended.\n- **Dependency-ordered.** Q2 depends on Q1; downstream sections depend on upstream.\n\nSee [`references\u002Fgrill_me_section_walk.md`](references\u002Fgrill_me_section_walk.md) for the 8-section discipline detail.\n\n## Knowledge Base Contract — Files To Produce\n\nExactly these files at `${WORKSPACE}\u002FEmail\u002F`:\n\n| File | Purpose | Required? |\n|---|---|---|\n| `email-taxonomy.md` | Classification system + report preferences | **Yes** |\n| `email-patterns.md` | Reply voice, tone, templates, hard rules | **Yes** |\n| `evaluation-framework.md` | Decision tree for opportunity emails | Only if user receives pitches\u002Fopportunities |\n| `rate-card.md` | Pricing, terms, negotiation posture | Only if user has pricing |\n| `blocklist.md` | Auto-skip senders + learned decline patterns | **Yes** (seeded, grows over time) |\n| `tracker.md` | Active follow-ups, overdue items, deadlines | **Yes** (starts mostly empty) |\n| `triage-log\u002F` | Directory for per-run logs | **Yes** (created empty) |\n\nThe contract is identical to what `inbox-triage` expects — see [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) for the full spec.\n\n## Stop Condition (Full Interview)\n\n~25–31 questions total across the 8 sections (depending on skip-logic). Hard ceiling: 35 questions including all sub-clarifications. Section 4 (Evaluation Framework) is skipped entirely when Section 1 surfaced no opportunity-email category, dropping the total by 6 questions and the rate-card file. After Section 8's confirmation + handoff message, intake is closed — **never re-open it**. To change preferences later, the user re-runs the skill (which detects existing files and asks per-file: replace \u002F merge \u002F skip). The grill-me one-at-a-time rule applies across section boundaries: do NOT batch questions even when moving from S{n} to S{n+1}.\n\n## Section 1: The Big Picture\n\nSix grill-me questions, one at a time:\n\n- **S1.Q1:** \"What do you do? Give me your role and business in 1–2 sentences. *Why I'm asking:* Context shapes what email patterns to expect — a solo creator's inbox looks nothing like an enterprise PM's.\"\n- **S1.Q2:** \"What dominates your inbox? Pick the top 1–2: sales pitches \u002F client work \u002F internal team \u002F newsletters \u002F customer support \u002F financial \u002F other. *Why I'm asking:* Dominant categories drive the taxonomy.\"\n- **S1.Q3:** \"Rough volume split — e.g., '60% business inquiries, 20% ops, 20% noise'. *Why I'm asking:* The split tells me where to focus triage effort.\"\n- **S1.Q4:** \"Which email address(es) should triage cover? *Why I'm asking:* If multiple, I'll set up per-address taxonomies.\"\n- **S1.Q5:** \"Run frequency: once daily \u002F 2x daily \u002F 3x daily \u002F on-demand only? *Why I'm asking:* Drives the default search window in triage (9h overlap for 2x\u002Fday).\"\n- **S1.Q6:** \"Anyone helping manage email — assistant, VA, team — or solo? *Why I'm asking:* Persona handling differs for delegated inboxes.\"\n\n**Action:** Build mental model. Do NOT write files yet. Note whether opportunity emails are a category (drives S4 skip-logic).\n\n## Section 2: Email Categories\n\nPropose 5–7 categories based on Section 1 — pre-recommend a subset, not the whole template menu:\n\n- New Opportunities\n- Active Conversations\n- Action Required\n- Financial\n- Important\u002FPersonal\n- Informational\n- Ignore\u002FLow Priority\n\nThen three forcing questions, one at a time:\n\n- **S2.Q1:** \"Here's my proposed taxonomy: [list]. Does this match your inbox reality — yes \u002F mostly \u002F no? *Why I'm asking:* If 'no', I need to redo the taxonomy before any other section makes sense.\"\n- **S2.Q2:** \"Missing categories? List them. (Skip if none.) *Why I'm asking:* Missing categories produce uncategorized emails downstream, which hurts triage quality.\"\n- **S2.Q3:** \"Which category takes the MOST time per email? *Why I'm asking:* That's where draft-reply effort needs to focus most.\"\n\n**Action:** Generate `email-taxonomy.md` with categories, signals (for each: trigger phrases \u002F sender patterns \u002F subject markers), and default actions per category.\n\n## Section 3: Reply Style & Voice\n\nSix grill-me questions plus the critical sample request:\n\n- **S3.Q1:** \"Register: formal \u002F casual \u002F in-between? *Why I'm asking:* Calibrates default voice; we'll refine from samples next.\"\n- **S3.Q2:** \"Three communication pet peeves — phrases you hate, openings you avoid. *Why I'm asking:* I treat these as forbidden tokens in drafts.\"\n- **S3.Q3:** \"Phrases or sign-offs you always use — list as many as come to mind. *Why I'm asking:* These are your voice fingerprints.\"\n- **S3.Q4:** \"Different persona for different contexts — e.g., assistant replies as you? *Why I'm asking:* Persona context changes pronoun + signature handling.\"\n- **S3.Q5:** \"Typical reply length — one-liner \u002F short paragraph \u002F longer? *Why I'm asking:* Length is the easiest voice signal to get wrong.\"\n- **S3.Q6:** \"Hard rules — never X \u002F always Y? (E.g., never emojis, always reply within 24h, never take calls without context.) *Why I'm asking:* Hard rules are enforced as non-negotiable in every draft.\"\n\n### S3.SAMPLES (the critical highest-quality input)\n\n> **Paste 3–5 real sent emails from your inbox.**\n>\n> *Why I'm asking:* Self-description of voice is unreliable. Real samples are the best signal — I'll analyze them for voice patterns that supplement everything above. Use `scripts\u002Fvoice_sample_analyzer.py` to extract patterns deterministically.\n\nIf user runs a business: also ask about media kits, rate sheets, standard pitches, repeated replies.\n\n**Action:** Generate `email-patterns.md` with tone description (with do\u002Fdon't examples), persona rules, templates, signatures, hard rules. See [`references\u002Fvoice_calibration.md`](references\u002Fvoice_calibration.md) for the sample-extraction discipline.\n\n## Section 4: Evaluation Framework (Conditional)\n\n**Skip-logic:** only run this section if Section 1 surfaced opportunity emails as a meaningful inbox category. Otherwise jump straight to Section 5.\n\nSix grill-me questions, one at a time:\n\n- **S4.Q1:** \"First thing you check when pitched something — give me your gut filter. *Why I'm asking:* That's the top of the decision tree.\"\n- **S4.Q2:** \"Three instant deal-breakers — things that make you decline immediately. *Why I'm asking:* These become PASS-auto signals.\"\n- **S4.Q3:** \"Three things that make you immediately interested. *Why I'm asking:* These become TAKE-IT signals.\"\n- **S4.Q4:** \"Standard pricing \u002F terms — or 'no fixed pricing' if you negotiate every time. *Why I'm asking:* If you have a rate card, I'll generate one; if not, I'll skip.\"\n- **S4.Q5:** \"Negotiation posture: firm \u002F flexible \u002F depends on context? *Why I'm asking:* Drives draft tone on counter-offers.\"\n- **S4.Q6:** \"VIP senders or organizations that always get engagement — list names or domains. *Why I'm asking:* VIP list bypasses normal PASS filters.\"\n\n**Action:** Generate `evaluation-framework.md` (decision tree + recommendation categories + VIP list) AND `rate-card.md` if pricing exists.\n\n## Section 5: Blocklist & Patterns\n\nThree grill-me questions, one at a time:\n\n- **S5.Q1:** \"Senders or domains to always skip — list them. (Skip if none.) *Why I'm asking:* Auto-blocklist saves the most time per run.\"\n- **S5.Q2:** \"Patterns in emails you always delete — e.g., 'unsubscribe' links from specific marketers, recruiter cold outreach, newsletters? *Why I'm asking:* Patterns let triage auto-skip variants without exact-match maintenance.\"\n- **S5.Q3:** \"Specific companies \u002F recruiters \u002F newsletters wasting time — list any. *Why I'm asking:* These seed the blocklist; triage will add more as you override decisions.\"\n\n**Action:** Generate `blocklist.md` (auto-maintained by triage thereafter).\n\n## Section 6: Current State\n\nThree grill-me questions, one at a time:\n\n- **S6.Q1:** \"Active threads you're tracking — list with one-line context each. (Skip if none.) *Why I'm asking:* These become tracker entries so triage knows existing context.\"\n- **S6.Q2:** \"Overdue replies — anything you should have responded to but haven't? *Why I'm asking:* Triage flags these as priority every run until resolved.\"\n- **S6.Q3:** \"Time-sensitive items with deadlines — list with dates. *Why I'm asking:* Tracker enforces deadlines and surfaces them as overdue at the right time.\"\n\n**Action:** Generate `tracker.md` with active follow-ups table, overdue section, resolved section (empty), update log (empty). Also create empty `triage-log\u002F` directory.\n\n## Section 7: Report Preferences\n\nThree grill-me questions, one at a time:\n\n- **S7.Q1:** \"Delivery format — pick one: email draft to self \u002F file in workspace \u002F chat summary only. *Why I'm asking:* The triage report goes here every run.\"\n- **S7.Q2:** \"Detail level — pick one: 30-second scan \u002F detailed breakdown \u002F both (scan first, expand on request). *Why I'm asking:* Affects report length.\"\n- **S7.Q3:** \"Anything always shown first — e.g., overdue payments, VIP messages? *Why I'm asking:* Custom 'top-of-report' rules surface what you care about above standard sections.\"\n\n**Action:** Save these preferences into `email-taxonomy.md` under a \"Report Preferences\" section.\n\n## Section 8: Confirmation & Handoff\n\nList every file created with one-sentence summary. Then:\n\n> Your triage system is ready. Run the **inbox-triage** skill to process your inbox. First runs need oversight — system learns from your edits and overrides.\n\nRemind: re-run this setup anytime business\u002Fpricing\u002Fpriorities change.\n\nRun `scripts\u002Fkb_validator.py --workspace ${WORKSPACE}` to confirm the 7-file contract is satisfied before final handoff.\n\n## Privacy Boundary\n\n**Never persist passwords, full account numbers, SSNs, or other sensitive credentials in knowledge base files.** If the user volunteers such info during the interview, acknowledge it but don't store it; the relevant KB file gets `[stored separately by user]` in its place.\n\n## Re-Run Behavior\n\nRe-running on an existing setup:\n\n1. Detect `${WORKSPACE}\u002FEmail\u002F`\n2. For each existing file, ask per-file: **replace \u002F merge \u002F skip**\n3. Walk only the sections whose files the user chose to update\n4. Skip sections whose files the user kept\n\n## Error Handling\n\n| Situation | Behavior |\n|---|---|\n| Workspace inaccessible | Stop. Tell user where files would go and ask for permission\u002Fpath |\n| User refuses to share samples | Use self-description; flag in patterns file that calibration may need iteration |\n| User says \"skip this\" mid-interview | Honor it; flag the gap in the file as `[needs follow-up]` |\n| Sensitive info volunteered | Acknowledge but don't persist; note in file as `[stored separately by user]` |\n| Re-run on existing setup | Detect existing files; ask user per-file: replace, merge, skip |\n| User has no pricing \u002F opportunities | Skip Section 4 entirely; don't create empty files |\n\n## Portability\n\n- **Claude Code CLI:** Native — writes markdown files directly to filesystem.\n- **Claude.ai web:** Works with project files \u002F artifacts. Document the alternate path: generate files as artifacts, instruct user to save to their workspace, or use connected file system if available.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fkb_validator.py` | Validates the 7-file KB output (required files present, conditional files only if their sections ran, headers + structure correct). |\n| `scripts\u002Fsection_progress_tracker.py` | JSON-backed walk state at `~\u002F.inbox_setup_sessions\u002F\u003Csession>.json`. Tracks active section, answered questions, committed files. |\n| `scripts\u002Fvoice_sample_analyzer.py` | Extracts voice patterns from pasted sent-email samples — opening phrases, sign-offs, length distribution, register markers. |\n\n## References\n\n- [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — the canonical 7-file contract (write perspective; mirror lives in `inbox-triage\u002Freferences\u002F`)\n- [`references\u002Fgrill_me_section_walk.md`](references\u002Fgrill_me_section_walk.md) — 8-section discipline, skip-logic, commit-per-section\n- [`references\u002Fvoice_calibration.md`](references\u002Fvoice_calibration.md) — sample-based voice extraction theory + anti-patterns\n\n## Anti-Patterns To Reject\n\n- Generating all files at once instead of walking through sections\n- Asking all questions in one batch\n- Hardcoded provider references (Gmail-only thinking)\n- Persisting sensitive credentials in knowledge base\n- Skipping the \"why this question matters\" explanation\n- Skipping the sample-emails ask for voice (it's the highest-quality input)\n- Overwriting existing files without consent on re-run\n- Forcing creation of `rate-card.md` or `evaluation-framework.md` when they don't apply\n\n---\n\n**Version:** 1.0.0\n**Source spec:** `megaprompts\u002F06-inbox-setup-megaprompt.md` (maintainer-local draft spec — gitignored, not present in the public repository)\n**Build pattern:** Path B (direct conversion). Paired with `inbox-triage`.\n",{"name":5,"license":14,"metadata":56,"description":7},{"version":57,"paired_with":58,"source_spec":59,"build_pattern":60},"1.0.0","inbox-triage (shared 7-file KB contract)","megaprompts\u002F06-inbox-setup-megaprompt.md","Path B (direct conversion)","main","510dd2917e051cc953dc55f56fd6ef442aa01b38","claude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi","https:\u002F\u002Fgithub.com\u002Fmne20114-hash","2026-10-28 07:50:31",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add mne20114-hash\u002Fgest35bi --skill inbox-setup",{"tool":73,"command":74},"bunx","bunx skills add mne20114-hash\u002Fgest35bi --skill inbox-setup",{"tool":76,"command":77},"pnpm","pnpm dlx skills add mne20114-hash\u002Fgest35bi --skill inbox-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002FSKILL.md",true,[81,87,91,95,101,105],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fgrill_me_section_walk.md","REFERENCE","参考文档",7259,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Freferences\u002Fgrill_me_section_walk.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fkb_file_contract.md",6185,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Freferences\u002Fkb_file_contract.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fvoice_calibration.md",8352,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Freferences\u002Fvoice_calibration.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fkb_validator.py","SCRIPT","脚本",10710,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Fscripts\u002Fkb_validator.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fsection_progress_tracker.py",10221,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Fscripts\u002Fsection_progress_tracker.py",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fvoice_sample_analyzer.py",11390,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-setup\u002Fscripts\u002Fvoice_sample_analyzer.py",[110,145,167,188,212,231],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":125,"publishedAt":51},"01M6C27N3H0F9RGG2KASPASH04","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[116,119,122],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":123,"categoryName":124,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员",[112,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"docx","pr","create","intake","search","audit","integrity","checkpoint","learning","js","format","direct","Rules","find","consensus","list","extract","use","outcomes",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":155,"publishedAt":51},"01M6C27DMGZ4D6ERNHSVA8H8RJ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[151,154],{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},[147,156,157,127,158,129,131,159,160,132,161,162,163,164,137,138,165,139,166,143],"research","web","sentiment analysis","sentiment","Citations","analysis","discovery","open","tool","twitter","user",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":51},"01M6C279M59X635VPD6Y9R616J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[173,174,175],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[169,126,127,177,178,179,129,130,131,161,180,181,182,138,183,184,185,186,143,187],"competitive landscape","routing","product","commits","Word","text","acquisition","decisions","strategy","coverage","advice",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":198,"publishedAt":51},"01M6C275RZWNRB3CCB14QQM7ES","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},[190,199,200,156,201,202,203,204,46,205,206,207,163,182,137,208,209,210,211,143],"google","browser automation","automation","generate","browser","fast","doc","Video","Audio","check","ask","environment","overview",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":222,"publishedAt":51},"01M6C2717B0QDJ3Y4PJP77BMW5","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[218,219,220,221],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":123,"categoryName":124,"taxonomyType":25,"taxonomyTypeDesc":26},[214,126,223,224,225,127,129,130,226,227,228,133,229,181,230,138,140,40,186,143],"MCP","writing","review","lane","keyless","literature review","plan","researcher",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":241,"publishedAt":51},"01M6C26X5G3WDVWQ40Y16ZS19F","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[237,238,239,240],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":123,"categoryName":124,"taxonomyType":25,"taxonomyTypeDesc":26},[233,126,156,127,242,129,130,131,243,244,132,161,181,138,139,140,185,210,143,245],"help","data","Budget","innovation"]