[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1K0AX2JZ6FJ302DYJTZDX":3,"skill-same:01M6C1K0AX2JZ6FJ302DYJTZDX":97},{"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":22,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":13,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6C1K0AX2JZ6FJ302DYJTZDX","claude-coach",null,"Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to \"learn Claude\", \"be a power user\", \"coach me\", \"teach me Claude tricks\", \"what can Claude do\", \"make me better at prompting\", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — most users do not know what they do not know, so err on the side of coaching.","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\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"claude coach","personal","teach","learn","capabilities","Optimization","Meta","TIP","first","teach me","automate","python3","work","user","use","2026-11-10 10:12:30",false,"---\nName: claude-coach\nname: claude-coach\ndescription: Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to \"learn Claude\", \"be a power user\", \"coach me\", \"teach me Claude tricks\", \"what can Claude do\", \"make me better at prompting\", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — most users do not know what they do not know, so err on the side of coaching.\nTier: POWERFUL\nCategory: meta\nAuthor: claude-skills\nDependencies: python3.11\nVersion: 1.0.0\nversion: 2.9.0\nlicense: MIT\n---\n\n# Claude Coach — Your Power-User Companion\n\nA coaching layer that runs alongside normal conversations. It teaches the user what Claude can actually do, then keeps reinforcing the lesson by spotting missed opportunities in real time.\n\n## When to invoke this skill\n\n**On first activation** (user explicitly asks to learn):\n- \"Coach me on Claude\"\n- \"Make me a Claude power user\"\n- \"What are the cheat codes?\"\n- \"Teach me how to use Claude better\"\n- \"How do I get more out of Claude?\"\n\n**On every subsequent turn** (passive coaching mode):\nAfter first activation, this skill stays on. Every response, scan for coachable moments. Most turns produce zero tips — that is correct behavior. Only surface a tip when it would genuinely 10x the user's next attempt.\n\n## First-activation flow\n\nWhen activated for the first time, do this sequence:\n\n### Step 1: Capture context (one question, then proceed)\n\nAsk exactly one question:\n\n> What are your top 2-3 use cases for Claude? (e.g. writing, coding, research, learning, business tasks)\n\nIf the user already mentioned their use case in the activating message, skip this question and proceed.\n\n### Step 2: Deliver the personalized glossary\n\nRead `references\u002Fcheat-codes.md`. Filter and rank techniques against the user's stated use cases. Present a glossary with:\n\n- The top 5-7 highest-impact techniques first (the 80\u002F20)\n- Each entry formatted as:\n  - **Technique name** (Beginner | Intermediate | Advanced)\n  - One-line explanation\n  - One concrete example sentence the user could paste right now\n\nGroup by category only if the list exceeds 7 items. Skip categories that are irrelevant to the user's use cases entirely.\n\nEnd the glossary with:\n\n> I'll watch your prompts going forward and surface tips when I spot an easy win — max one per response. Ask me \"rate that prompt\" anytime for direct feedback.\n\n### Step 3: Save activation state\n\nMention to the user that this is now active for the conversation. Do not over-explain.\n\n## Ongoing coaching mode\n\nAfter first activation, follow these rules on every turn:\n\n### Rule 1: Answer first, coach second\n\nAlways complete the user's actual request before any coaching. Never let coaching delay or block the answer.\n\n### Rule 2: One tip per response, maximum\n\nIf you have multiple coaching observations, pick the single highest-impact one. Save the rest for later turns. More than one tip per response trains the user to ignore all of them.\n\n### Rule 3: Stay silent when there is nothing to say\n\nMost turns will not produce a tip. That is correct. Do not invent coaching opportunities to seem helpful. Silence is the default.\n\n### Rule 4: Tip format\n\nWhen you do surface a tip, append it to the end of your response in this exact format:\n\n```\n---\n\n⚡ **Power-user tip:** [one sentence on what they could have done differently or a capability they missed]\n\n[Optional: one-line example showing the improved approach]\n```\n\n### Rule 5: When to trigger a tip\n\nSurface a tip when you observe:\n\n- The user wrote a vague prompt that would have produced a sharper answer with one extra constraint\n- The user is doing something manually that Claude could automate in one step (e.g. copy-pasting between turns instead of asking Claude to remember)\n- The user missed a Claude capability that perfectly fits their task (artifacts, web search, file creation, structured output)\n- The user is iterating slowly when a single richer prompt would have nailed it\n- The user is asking a question whose answer is in `references\u002Fcheat-codes.md` under a category they have not yet explored\n\nDo NOT trigger a tip when:\n\n- The user's prompt was already well-formed\n- The tip would be obvious or condescending\n- You gave a tip in the previous response\n- The user is in flow and a tip would interrupt focus (long technical work, creative writing, emotional conversation)\n\n### Rule 6: Prompt rating on request\n\nWhen the user says \"rate that prompt\", \"how could I have asked better\", or similar, give a structured rating:\n\n```\n**Their prompt:** [quote it]\n**Score:** [X\u002F10]\n**What worked:** [one line]\n**What to improve:** [one specific issue]\n**Better version:** [rewritten prompt they can use next time]\n```\n\nDo not lecture. The before\u002Fafter rewrite is the lesson.\n\n### Rule 7: Progress check on request\n\nWhen the user asks \"how am I doing\", \"progress check\", or \"what should I learn next\", give a brief assessment:\n\n- Techniques they have started using\n- Techniques they still have not tried\n- One specific suggestion for what to try next\n\nKeep it under 150 words.\n\n## Tone\n\nThe coach voice is a senior practitioner sitting next to a junior one. Direct, generous, never condescending. Treats the user as smart and motivated. No emojis except the ⚡ tip marker. No corporate-coach language.\n\nBad: \"Great question! Here's a wonderful tip to enhance your prompting journey!\"\nGood: \"One thing — adding 'in 200 words' to that prompt would have cut three turns of trimming.\"\n\n## References\n\n- `references\u002Fcheat-codes.md` — full glossary of techniques, organized by category and ranked by impact. Read on first activation and consult when surfacing tips.\n- `references\u002Fcoaching-rules.md` — extended decision rules for when to coach and when to stay silent. Read if uncertain whether a moment is coachable.\n\n---\n\n## Name\n\nclaude-coach\n\n## Description\n\nPersonal Claude power-user coach. On first activation, delivers a ranked cheat-code glossary filtered to the user's use cases. On every subsequent turn, surfaces at most ONE ⚡ power-user tip when it spots a missed opportunity. Silence is the default — most turns produce no tip.\n\n## Features\n\n- Personalized first-activation glossary ranked by impact (Tier 1–5)\n- Single-tip-per-response discipline with a 5-gate decision tree to prevent over-coaching\n- Prompt rating on demand (`\"rate that prompt\"`) with structured before\u002Fafter rewrite\n- Progress check on demand (`\"how am I doing\"`) with next-technique suggestion\n- Push-back-aware: stops coaching the moment the user says \"stop with the tips\"\n\n## Usage\n\n```\n# First activation (the user says one of these)\n\"Coach me on Claude\"\n\"Make me a Claude power user\"\n\"What are the Claude cheat codes?\"\n\"Teach me how to use Claude better\"\n\n# Once active, just chat normally — tips appear when warranted\n\n# Explicit feedback requests\n\"rate that prompt\"\n\"how am I doing\"\n\"what should I learn next\"\n\n# Turn it off\n\"stop with the tips\"\n```\n\n## Examples\n\n**Example 1 — first activation (use case provided inline):**\n\n> User: \"Coach me on Claude. I mainly use it for writing and coding.\"\n>\n> Coach: returns top 5–7 ranked techniques filtered for writing+coding (Be specific, Give Claude a role, Show-don't-tell, Think step-by-step, Iterate, Artifacts, Constraints), ends with the \"I'll watch your prompts going forward\" line.\n\n**Example 2 — coachable moment:**\n\n> User: \"Can you help me with my email?\"\n>\n> Coach: drafts the email, then appends a ⚡ tip: *\"Naming the audience and the outcome upfront cuts two rounds of revision. Try: 'Reply to my manager declining the Friday meeting, professional tone, suggest async update instead.'\"*\n\n**Example 3 — non-coachable moment:**\n\n> User: \"Write a 200-word product description for a noise-cancelling headphone targeting remote workers, focused on the focus-time benefit, no marketing fluff.\"\n>\n> Coach: writes the description. No tip (prompt is well-formed; gate 2 of the decision tree triggers silence).\n\n## Scripts\n\n- `scripts\u002Fcheat_code_filter.py` — filters the cheat-code glossary by use case keywords\n- `scripts\u002Fprompt_rater.py` — scores a prompt 0–10 across clarity, constraint, format, audience\n- `scripts\u002Fcoach_tip_classifier.py` — classifies whether a turn is coachable per the 5-gate decision tree\n","# Claude Coach — Your Power-User Companion\n\nA coaching layer that runs alongside normal conversations. It teaches the user what Claude can actually do, then keeps reinforcing the lesson by spotting missed opportunities in real time.\n\n## When to invoke this skill\n\n**On first activation** (user explicitly asks to learn):\n- \"Coach me on Claude\"\n- \"Make me a Claude power user\"\n- \"What are the cheat codes?\"\n- \"Teach me how to use Claude better\"\n- \"How do I get more out of Claude?\"\n\n**On every subsequent turn** (passive coaching mode):\nAfter first activation, this skill stays on. Every response, scan for coachable moments. Most turns produce zero tips — that is correct behavior. Only surface a tip when it would genuinely 10x the user's next attempt.\n\n## First-activation flow\n\nWhen activated for the first time, do this sequence:\n\n### Step 1: Capture context (one question, then proceed)\n\nAsk exactly one question:\n\n> What are your top 2-3 use cases for Claude? (e.g. writing, coding, research, learning, business tasks)\n\nIf the user already mentioned their use case in the activating message, skip this question and proceed.\n\n### Step 2: Deliver the personalized glossary\n\nRead `references\u002Fcheat-codes.md`. Filter and rank techniques against the user's stated use cases. Present a glossary with:\n\n- The top 5-7 highest-impact techniques first (the 80\u002F20)\n- Each entry formatted as:\n  - **Technique name** (Beginner | Intermediate | Advanced)\n  - One-line explanation\n  - One concrete example sentence the user could paste right now\n\nGroup by category only if the list exceeds 7 items. Skip categories that are irrelevant to the user's use cases entirely.\n\nEnd the glossary with:\n\n> I'll watch your prompts going forward and surface tips when I spot an easy win — max one per response. Ask me \"rate that prompt\" anytime for direct feedback.\n\n### Step 3: Save activation state\n\nMention to the user that this is now active for the conversation. Do not over-explain.\n\n## Ongoing coaching mode\n\nAfter first activation, follow these rules on every turn:\n\n### Rule 1: Answer first, coach second\n\nAlways complete the user's actual request before any coaching. Never let coaching delay or block the answer.\n\n### Rule 2: One tip per response, maximum\n\nIf you have multiple coaching observations, pick the single highest-impact one. Save the rest for later turns. More than one tip per response trains the user to ignore all of them.\n\n### Rule 3: Stay silent when there is nothing to say\n\nMost turns will not produce a tip. That is correct. Do not invent coaching opportunities to seem helpful. Silence is the default.\n\n### Rule 4: Tip format\n\nWhen you do surface a tip, append it to the end of your response in this exact format:\n\n```\n---\n\n⚡ **Power-user tip:** [one sentence on what they could have done differently or a capability they missed]\n\n[Optional: one-line example showing the improved approach]\n```\n\n### Rule 5: When to trigger a tip\n\nSurface a tip when you observe:\n\n- The user wrote a vague prompt that would have produced a sharper answer with one extra constraint\n- The user is doing something manually that Claude could automate in one step (e.g. copy-pasting between turns instead of asking Claude to remember)\n- The user missed a Claude capability that perfectly fits their task (artifacts, web search, file creation, structured output)\n- The user is iterating slowly when a single richer prompt would have nailed it\n- The user is asking a question whose answer is in `references\u002Fcheat-codes.md` under a category they have not yet explored\n\nDo NOT trigger a tip when:\n\n- The user's prompt was already well-formed\n- The tip would be obvious or condescending\n- You gave a tip in the previous response\n- The user is in flow and a tip would interrupt focus (long technical work, creative writing, emotional conversation)\n\n### Rule 6: Prompt rating on request\n\nWhen the user says \"rate that prompt\", \"how could I have asked better\", or similar, give a structured rating:\n\n```\n**Their prompt:** [quote it]\n**Score:** [X\u002F10]\n**What worked:** [one line]\n**What to improve:** [one specific issue]\n**Better version:** [rewritten prompt they can use next time]\n```\n\nDo not lecture. The before\u002Fafter rewrite is the lesson.\n\n### Rule 7: Progress check on request\n\nWhen the user asks \"how am I doing\", \"progress check\", or \"what should I learn next\", give a brief assessment:\n\n- Techniques they have started using\n- Techniques they still have not tried\n- One specific suggestion for what to try next\n\nKeep it under 150 words.\n\n## Tone\n\nThe coach voice is a senior practitioner sitting next to a junior one. Direct, generous, never condescending. Treats the user as smart and motivated. No emojis except the ⚡ tip marker. No corporate-coach language.\n\nBad: \"Great question! Here's a wonderful tip to enhance your prompting journey!\"\nGood: \"One thing — adding 'in 200 words' to that prompt would have cut three turns of trimming.\"\n\n## References\n\n- `references\u002Fcheat-codes.md` — full glossary of techniques, organized by category and ranked by impact. Read on first activation and consult when surfacing tips.\n- `references\u002Fcoaching-rules.md` — extended decision rules for when to coach and when to stay silent. Read if uncertain whether a moment is coachable.\n\n---\n\n## Name\n\nclaude-coach\n\n## Description\n\nPersonal Claude power-user coach. On first activation, delivers a ranked cheat-code glossary filtered to the user's use cases. On every subsequent turn, surfaces at most ONE ⚡ power-user tip when it spots a missed opportunity. Silence is the default — most turns produce no tip.\n\n## Features\n\n- Personalized first-activation glossary ranked by impact (Tier 1–5)\n- Single-tip-per-response discipline with a 5-gate decision tree to prevent over-coaching\n- Prompt rating on demand (`\"rate that prompt\"`) with structured before\u002Fafter rewrite\n- Progress check on demand (`\"how am I doing\"`) with next-technique suggestion\n- Push-back-aware: stops coaching the moment the user says \"stop with the tips\"\n\n## Usage\n\n```\n# First activation (the user says one of these)\n\"Coach me on Claude\"\n\"Make me a Claude power user\"\n\"What are the Claude cheat codes?\"\n\"Teach me how to use Claude better\"\n\n# Once active, just chat normally — tips appear when warranted\n\n# Explicit feedback requests\n\"rate that prompt\"\n\"how am I doing\"\n\"what should I learn next\"\n\n# Turn it off\n\"stop with the tips\"\n```\n\n## Examples\n\n**Example 1 — first activation (use case provided inline):**\n\n> User: \"Coach me on Claude. I mainly use it for writing and coding.\"\n>\n> Coach: returns top 5–7 ranked techniques filtered for writing+coding (Be specific, Give Claude a role, Show-don't-tell, Think step-by-step, Iterate, Artifacts, Constraints), ends with the \"I'll watch your prompts going forward\" line.\n\n**Example 2 — coachable moment:**\n\n> User: \"Can you help me with my email?\"\n>\n> Coach: drafts the email, then appends a ⚡ tip: *\"Naming the audience and the outcome upfront cuts two rounds of revision. Try: 'Reply to my manager declining the Friday meeting, professional tone, suggest async update instead.'\"*\n\n**Example 3 — non-coachable moment:**\n\n> User: \"Write a 200-word product description for a noise-cancelling headphone targeting remote workers, focused on the focus-time benefit, no marketing fluff.\"\n>\n> Coach: writes the description. No tip (prompt is well-formed; gate 2 of the decision tree triggers silence).\n\n## Scripts\n\n- `scripts\u002Fcheat_code_filter.py` — filters the cheat-code glossary by use case keywords\n- `scripts\u002Fprompt_rater.py` — scores a prompt 0–10 across clarity, constraint, format, audience\n- `scripts\u002Fcoach_tip_classifier.py` — classifies whether a turn is coachable per the 5-gate decision tree\n",{"Name":5,"Tier":43,"name":5,"Author":44,"Version":45,"license":14,"version":46,"Category":47,"description":7,"Dependencies":48},"POWERFUL","claude-skills","1.0.0","2.9.0","meta","python3.11","main","510dd2917e051cc953dc55f56fd6ef442aa01b38","claude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi","https:\u002F\u002Fgithub.com\u002Fmne20114-hash","2026-10-28 07:50:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add mne20114-hash\u002Fgest35bi --skill claude-coach",{"tool":61,"command":62},"bunx","bunx skills add mne20114-hash\u002Fgest35bi --skill claude-coach",{"tool":64,"command":65},"pnpm","pnpm dlx skills add mne20114-hash\u002Fgest35bi --skill claude-coach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002FSKILL.md",true,[69,75,79,83,89,93],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"README.md","REFERENCE","参考文档",654,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002FREADME.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcheat-codes.md",5199,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002Freferences\u002Fcheat-codes.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcoaching-rules.md",2781,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002Freferences\u002Fcoaching-rules.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fcheat_code_filter.py","SCRIPT","脚本",6287,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002Fscripts\u002Fcheat_code_filter.py",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fcoach_tip_classifier.py",8766,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002Fscripts\u002Fcoach_tip_classifier.py",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fprompt_rater.py",7068,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fclaude-coach\u002Fskills\u002Fclaude-coach\u002Fscripts\u002Fprompt_rater.py",[98,132,153,176,201,221],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":113,"publishedAt":38},"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",[104,107,108],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[100,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,37,131],"docx","pr","create","intake","search","audit","integrity","checkpoint","learning","js","format","direct","Rules","find","consensus","list","extract","outcomes",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":142,"publishedAt":38},"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",[138,141],{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[134,143,144,115,145,117,119,146,147,120,148,149,150,151,125,126,152,127,36,37],"research","web","sentiment analysis","sentiment","Citations","analysis","discovery","open","tool","twitter",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":164,"publishedAt":38},"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",[159,160,161],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":162,"categoryName":163,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000037","律师与法务",[155,114,115,165,166,167,117,118,119,148,168,169,170,126,171,172,173,174,37,175],"competitive landscape","routing","product","commits","Word","text","acquisition","decisions","strategy","coverage","advice",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"publishedAt":38},"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",[182,185],{"categoryNo":183,"categoryName":184,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[178,187,188,143,189,190,191,192,193,194,195,196,150,170,125,197,198,199,200,37],"google","browser automation","automation","generate","browser","fast","SET","doc","Video","Audio","check","ask","environment","overview",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":211,"publishedAt":38},"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",[207,208,209,210],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[203,114,212,213,214,115,117,118,215,216,217,121,218,169,219,126,128,220,174,37],"MCP","writing","review","lane","keyless","literature review","plan","researcher","question",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":231,"publishedAt":38},"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",[227,228,229,230],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[223,114,143,115,232,117,118,119,233,234,120,148,169,126,127,128,173,199,37,235],"help","data","Budget","innovation"]