[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MZMWH6M1H3EQJEWAF97C0R":3,"skill-same:01M6MZMWH6M1H3EQJEWAF97C0R":72},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6MZMWH6M1H3EQJEWAF97C0R","pitch",null,"Activate for: pitch, investor deck, fundraising, pitch deck, pitch narrative, investor presentation, raise money, seed round, Series A, SAFE, convertible note, valuation, investor story, narrative architecture, pitch slides, executive summary, investor email, one pager, funding, angel investor, venture capital, VC pitch, pitch practice, hard questions, investor Q&A, term sheet, data room, investor brief. NOT for: unit economics or financial modelling (use financials), business model canvas (use canvas), market sizing (use market).","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-pitch-skill-902f92e1\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"seed","financials","vc","funding","q&a","presentation","economics","unit","narrative","canvas","activate","one pager","model","data","brief","executive summary","architecture","valuation","safe","2026-11-10 10:12:30",false,"---\nname: pitch\ndescription: >\n  Activate for: pitch, investor deck, fundraising, pitch deck, pitch narrative,\n  investor presentation, raise money, seed round, Series A, SAFE, convertible note,\n  valuation, investor story, narrative architecture, pitch slides, executive summary,\n  investor email, one pager, funding, angel investor, venture capital, VC pitch,\n  pitch practice, hard questions, investor Q&A, term sheet, data room, investor brief.\n  NOT for: unit economics or financial modelling (use financials),\n  business model canvas (use canvas), market sizing (use market).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fpitch\"\n---\n\n## CONTEXT LOADING\n\nBefore executing, check for `innov.local.md` in the working directory.\nIf found, extract:\n\n- venture: name, stage, type, problem_statement, solution_hypothesis, unfair_advantage\n- financial_model: unit_economics, current_state, milestones\n- business_model_canvas: all blocks with evidence quality\n- competitive_landscape: direct_competitors, differentiation, moat_building\n- fundraising: current_round, investor_pipeline, data_room_status\n- customer_profiles: personas, WTP, buying_process\n\nIf `innov.local.md` is not found:\nContinue with conversation context. After first substantive output, prompt:\n\"I'm working without your venture context. Run Exercise 8 from Chapter 40\nto build innov.local.md -- it will make every subsequent output specific\nto your venture rather than generic.\"\n\n## STAGE-AWARE CALIBRATION\n\nCheck venture.stage and calibrate:\n\n- IDEA: Warning -- \"You have no traction to pitch. Investors at the seed stage need at minimum discovery insights, a clear problem statement, and evidence of customer willingness to pay. Consider running \u002Fdiscovery and \u002Fhypothesis first.\"\n- DISCOVERY: Warning -- \"Pitching at the DISCOVERY stage is early. You can build the narrative architecture, but the traction slide will be weak. Focus on completing discovery and getting LOIs before pitching.\"\n- VALIDATION: Pitching is appropriate if you have pilot results or LOIs.\n- MVP: This is a strong pitching stage -- you should have real metrics.\n- GROWTH: This is your focus stage for fundraising -- strong traction story.\n\n## DLA PROGRESSION CHECK\n\nIf no financial_model or business_model_canvas data exists in innov.local.md:\n\"You are building a pitch without financial data or a business model canvas.\nYour Slide 6 (Business Model) and Slide 4 (Market) will be weak.\nConsider running \u002Fcanvas and \u002Ffinancials first.\"\n\n## PITCH AND FUNDRAISING WORKFLOW\n\n### Task Types\n\nTYPE 1: PITCH DECK NARRATIVE\nPurpose: Build the narrative architecture for a full investor pitch deck.\nInput: Venture context + traction + raise details + investor type\nOutput: 9-slide structure with headline, content, verbal script, emotional job\n\nTYPE 2: HARD QUESTIONS PREP\nPurpose: Prepare for the 15 hardest questions investors will ask.\nInput: Venture context + investor type + known weaknesses\nOutput: Question + honest answer + what to do before the pitch if no good answer\n\nTYPE 3: EXECUTIVE SUMMARY\nPurpose: One-paragraph (100-word) venture summary for investor email intro.\nInput: Venture context\nOutput: Problem, solution, traction, ask, why worth their time -- specific, no cliches\n\nTYPE 4: INVESTOR RESEARCH BRIEF\nPurpose: Pre-meeting brief on a specific investor.\nInput: Investor name \u002F firm\nOutput: Portfolio, known thesis, past questions from public sources, 5 likely hard questions\n\nTYPE 5: TERM SHEET ANALYSIS\nPurpose: Identify non-standard terms in a term sheet.\nInput: Term sheet (or key terms)\nOutput: Standard vs. non-standard; what to push back on; what is acceptable\n\n### Pitch Deck Narrative Structure\n\n9 SLIDES -- NARRATIVE ARC:\n\nSLIDE 1: THE HOOK -- Why does this matter, and why now?\nHeadline: [The most memorable one-sentence claim]\nContent: [The number that makes the problem real; or the striking contrast]\nSays: [30-second verbal; make the investor feel why this matters]\nEmotional job: Curiosity + urgency\n\nSLIDE 2: THE PROBLEM -- Make the investor feel the pain\nHeadline: [The specific, surprising, or counterintuitive problem framing]\nContent: [Journey map or pain stats from discovery; customer quote]\nSays: [Walk through how it actually works today -- the messy reality]\nEmotional job: Recognition; empathy with the customer\n\nSLIDE 3: THE SOLUTION -- Your specific answer\nHeadline: [What makes this different from the obvious solution]\nContent: [Screenshot or demo; 3 capabilities; key differentiator]\nSays: [What you built differently; why it works with existing behaviour]\nEmotional job: Relief; \"this makes sense\"\n\nSLIDE 4: THE MARKET -- The size of the opportunity\nHeadline: [Bottom-up market size -- specific and credible]\nContent: [TAM \u002F SAM \u002F SOM from bottom-up model; market timing reason]\nSays: [The math; why now; why this market]\nEmotional job: Scale calibration; serious but achievable\n\nSLIDE 5: TRACTION -- Why should investors believe you?\nHeadline: [Your strongest traction claim -- specific numbers]\nContent: [Paying customers; revenue; retention; usage; LOIs; growth rate]\nSays: [What you have built and proved without institutional capital]\nEmotional job: De-risking; this team can execute\n\nSLIDE 6: BUSINESS MODEL -- How it makes money\nHeadline: [Unit economics headline -- LTV:CAC or payback or margin]\nContent: [Pricing; unit economics; breakeven; 18-month ARR target]\nSays: [The math that shows this is a real business, not just a product]\nEmotional job: Financial conviction\n\nSLIDE 7: THE TEAM -- Why this team\nHeadline: [The founding team's specific unfair advantage for this problem]\nContent: [Relevant experience -- not generic CVs; why this problem, why now]\nSays: [Authentic; personal; why you are the right people]\nEmotional job: Trust\n\nSLIDE 8: THE ASK -- What you need and exactly how you'll use it\nHeadline: [$X to go from [current state] to [18-month milestone]]\nContent: [Use of funds in %; 18-month milestone; instrument + cap\u002Frate]\nSays: [This is exactly what the capital buys; when we raise again]\nEmotional job: Clarity; the investor knows what they are buying\n\nSLIDE 9: THE VISION -- Where this goes\nHeadline: [The big picture -- what this becomes in 5-10 years]\nContent: [Product path; market expansion; comparable exit \u002F category]\nSays: [The wedge is X; the real opportunity is Y]\nEmotional job: Ambition; this could be very large\n\n## PITCH QUALITY STANDARD\n\nEVERY CLAIM must have a source:\n\n- Customer data: \"9 of 10 CFOs in our discovery interviews...\"\n- Pilot results: \"In our 3 pilots, adoption was 71-89%...\"\n- Market data: \"According to [source], there are X companies...\"\n- Your own metrics: \"$X MRR; N customers; X% month-over-month growth\"\n\nNEVER USE THESE PHRASES (red flags for experienced investors):\n\n- \"Massive market opportunity\" -- give the number\n- \"Disruptive technology\" -- explain the specific disruption mechanism\n- \"First mover advantage\" -- explain what makes the advantage durable\n- \"Proprietary AI\" -- what specifically is proprietary about it?\n- \"Conservative projections\" -- all projections are optimistic; say \"base case\"\n- \"We just need 1% of the market\" -- this is not a strategy; it's math\n- \"No direct competition\" -- if there's no competition, there's no market\n\nTRACTION HIERARCHY (most to least convincing):\n\n1. Revenue + growth rate (paying customers; MRR; month-over-month)\n2. Pilot results with specific metrics (adoption rate; retention; NPS)\n3. Letters of intent with specific terms (amount; timeline)\n4. Waitlist with conversion rate\n5. Discovery interviews with specific insights and quotes\n\n### Investor Research Brief Format\n\n```\nINVESTOR BRIEF -- [Name \u002F Firm] -- Pre-Meeting\n================================================================\nINVESTOR PROFILE:\n  Known focus: [Stage, sector, geography preferences]\n  Portfolio: [Relevant portfolio companies -- especially in your sector]\n  Investment thesis: [Any public statements about what they look for]\n\nWHAT THEY CARE ABOUT (based on portfolio and public statements):\n  [2-3 specific themes this investor has shown pattern interest in]\n\nLIKELY HARD QUESTIONS:\n  1. [Question they will almost certainly ask -- with recommended answer]\n  2. [Question based on known portfolio pattern]\n  3. [Question based on your known weaknesses]\n  4. [Question based on market conditions]\n  5. [The question that tests whether you know your numbers]\n\nHOW TO APPROACH THIS MEETING:\n  Opening: [What to emphasise given their known focus]\n  Watch for: [Any sensitivity; portfolio conflicts; known preferences]\n================================================================\n```\n\n## FINANCIAL REASONING STANDARD\n\nFor Slide 6 (Business Model) and any financial claims in the pitch:\n\n- Unit economics first: LTV:CAC must be stated with evidence level\n- Churn must be flagged if ASSUMED -- investors will ask\n- Market size must use bottom-up methodology, not top-down analyst TAM\n- Runway and use of funds must be specific and add up\n\n## ASSUMPTION TRACKING\n\nAfter any pitch output:\n\n- Surface any claim in the pitch that is ASSUMED rather than validated\n- Propose strengthening weak claims before the pitch meeting\n- Identify the strongest and weakest slides based on evidence quality\n\n## NEVER DO THESE\n\n- NEVER send a pitch deck without practicing the verbal narrative out loud\n  at least once -- the slide is the prompt; the verbal is the pitch\n- NEVER claim traction you cannot defend with specifics in a follow-up\n- NEVER show only the base-case financial scenario -- always have the\n  conservative scenario ready; investors will ask\n- NEVER leave the team slide generic -- it must explain WHY this team\n  has an advantage for this specific problem\n- NEVER use a top-down TAM (\"the market is $X trillion\") without a\n  bottom-up sanity check; investors know the top-down number is misleading\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## CONTEXT LOADING\n\nBefore executing, check for `innov.local.md` in the working directory.\nIf found, extract:\n\n- venture: name, stage, type, problem_statement, solution_hypothesis, unfair_advantage\n- financial_model: unit_economics, current_state, milestones\n- business_model_canvas: all blocks with evidence quality\n- competitive_landscape: direct_competitors, differentiation, moat_building\n- fundraising: current_round, investor_pipeline, data_room_status\n- customer_profiles: personas, WTP, buying_process\n\nIf `innov.local.md` is not found:\nContinue with conversation context. After first substantive output, prompt:\n\"I'm working without your venture context. Run Exercise 8 from Chapter 40\nto build innov.local.md -- it will make every subsequent output specific\nto your venture rather than generic.\"\n\n## STAGE-AWARE CALIBRATION\n\nCheck venture.stage and calibrate:\n\n- IDEA: Warning -- \"You have no traction to pitch. Investors at the seed stage need at minimum discovery insights, a clear problem statement, and evidence of customer willingness to pay. Consider running \u002Fdiscovery and \u002Fhypothesis first.\"\n- DISCOVERY: Warning -- \"Pitching at the DISCOVERY stage is early. You can build the narrative architecture, but the traction slide will be weak. Focus on completing discovery and getting LOIs before pitching.\"\n- VALIDATION: Pitching is appropriate if you have pilot results or LOIs.\n- MVP: This is a strong pitching stage -- you should have real metrics.\n- GROWTH: This is your focus stage for fundraising -- strong traction story.\n\n## DLA PROGRESSION CHECK\n\nIf no financial_model or business_model_canvas data exists in innov.local.md:\n\"You are building a pitch without financial data or a business model canvas.\nYour Slide 6 (Business Model) and Slide 4 (Market) will be weak.\nConsider running \u002Fcanvas and \u002Ffinancials first.\"\n\n## PITCH AND FUNDRAISING WORKFLOW\n\n### Task Types\n\nTYPE 1: PITCH DECK NARRATIVE\nPurpose: Build the narrative architecture for a full investor pitch deck.\nInput: Venture context + traction + raise details + investor type\nOutput: 9-slide structure with headline, content, verbal script, emotional job\n\nTYPE 2: HARD QUESTIONS PREP\nPurpose: Prepare for the 15 hardest questions investors will ask.\nInput: Venture context + investor type + known weaknesses\nOutput: Question + honest answer + what to do before the pitch if no good answer\n\nTYPE 3: EXECUTIVE SUMMARY\nPurpose: One-paragraph (100-word) venture summary for investor email intro.\nInput: Venture context\nOutput: Problem, solution, traction, ask, why worth their time -- specific, no cliches\n\nTYPE 4: INVESTOR RESEARCH BRIEF\nPurpose: Pre-meeting brief on a specific investor.\nInput: Investor name \u002F firm\nOutput: Portfolio, known thesis, past questions from public sources, 5 likely hard questions\n\nTYPE 5: TERM SHEET ANALYSIS\nPurpose: Identify non-standard terms in a term sheet.\nInput: Term sheet (or key terms)\nOutput: Standard vs. non-standard; what to push back on; what is acceptable\n\n### Pitch Deck Narrative Structure\n\n9 SLIDES -- NARRATIVE ARC:\n\nSLIDE 1: THE HOOK -- Why does this matter, and why now?\nHeadline: [The most memorable one-sentence claim]\nContent: [The number that makes the problem real; or the striking contrast]\nSays: [30-second verbal; make the investor feel why this matters]\nEmotional job: Curiosity + urgency\n\nSLIDE 2: THE PROBLEM -- Make the investor feel the pain\nHeadline: [The specific, surprising, or counterintuitive problem framing]\nContent: [Journey map or pain stats from discovery; customer quote]\nSays: [Walk through how it actually works today -- the messy reality]\nEmotional job: Recognition; empathy with the customer\n\nSLIDE 3: THE SOLUTION -- Your specific answer\nHeadline: [What makes this different from the obvious solution]\nContent: [Screenshot or demo; 3 capabilities; key differentiator]\nSays: [What you built differently; why it works with existing behaviour]\nEmotional job: Relief; \"this makes sense\"\n\nSLIDE 4: THE MARKET -- The size of the opportunity\nHeadline: [Bottom-up market size -- specific and credible]\nContent: [TAM \u002F SAM \u002F SOM from bottom-up model; market timing reason]\nSays: [The math; why now; why this market]\nEmotional job: Scale calibration; serious but achievable\n\nSLIDE 5: TRACTION -- Why should investors believe you?\nHeadline: [Your strongest traction claim -- specific numbers]\nContent: [Paying customers; revenue; retention; usage; LOIs; growth rate]\nSays: [What you have built and proved without institutional capital]\nEmotional job: De-risking; this team can execute\n\nSLIDE 6: BUSINESS MODEL -- How it makes money\nHeadline: [Unit economics headline -- LTV:CAC or payback or margin]\nContent: [Pricing; unit economics; breakeven; 18-month ARR target]\nSays: [The math that shows this is a real business, not just a product]\nEmotional job: Financial conviction\n\nSLIDE 7: THE TEAM -- Why this team\nHeadline: [The founding team's specific unfair advantage for this problem]\nContent: [Relevant experience -- not generic CVs; why this problem, why now]\nSays: [Authentic; personal; why you are the right people]\nEmotional job: Trust\n\nSLIDE 8: THE ASK -- What you need and exactly how you'll use it\nHeadline: [$X to go from [current state] to [18-month milestone]]\nContent: [Use of funds in %; 18-month milestone; instrument + cap\u002Frate]\nSays: [This is exactly what the capital buys; when we raise again]\nEmotional job: Clarity; the investor knows what they are buying\n\nSLIDE 9: THE VISION -- Where this goes\nHeadline: [The big picture -- what this becomes in 5-10 years]\nContent: [Product path; market expansion; comparable exit \u002F category]\nSays: [The wedge is X; the real opportunity is Y]\nEmotional job: Ambition; this could be very large\n\n## PITCH QUALITY STANDARD\n\nEVERY CLAIM must have a source:\n\n- Customer data: \"9 of 10 CFOs in our discovery interviews...\"\n- Pilot results: \"In our 3 pilots, adoption was 71-89%...\"\n- Market data: \"According to [source], there are X companies...\"\n- Your own metrics: \"$X MRR; N customers; X% month-over-month growth\"\n\nNEVER USE THESE PHRASES (red flags for experienced investors):\n\n- \"Massive market opportunity\" -- give the number\n- \"Disruptive technology\" -- explain the specific disruption mechanism\n- \"First mover advantage\" -- explain what makes the advantage durable\n- \"Proprietary AI\" -- what specifically is proprietary about it?\n- \"Conservative projections\" -- all projections are optimistic; say \"base case\"\n- \"We just need 1% of the market\" -- this is not a strategy; it's math\n- \"No direct competition\" -- if there's no competition, there's no market\n\nTRACTION HIERARCHY (most to least convincing):\n\n1. Revenue + growth rate (paying customers; MRR; month-over-month)\n2. Pilot results with specific metrics (adoption rate; retention; NPS)\n3. Letters of intent with specific terms (amount; timeline)\n4. Waitlist with conversion rate\n5. Discovery interviews with specific insights and quotes\n\n### Investor Research Brief Format\n\n```\nINVESTOR BRIEF -- [Name \u002F Firm] -- Pre-Meeting\n================================================================\nINVESTOR PROFILE:\n  Known focus: [Stage, sector, geography preferences]\n  Portfolio: [Relevant portfolio companies -- especially in your sector]\n  Investment thesis: [Any public statements about what they look for]\n\nWHAT THEY CARE ABOUT (based on portfolio and public statements):\n  [2-3 specific themes this investor has shown pattern interest in]\n\nLIKELY HARD QUESTIONS:\n  1. [Question they will almost certainly ask -- with recommended answer]\n  2. [Question based on known portfolio pattern]\n  3. [Question based on your known weaknesses]\n  4. [Question based on market conditions]\n  5. [The question that tests whether you know your numbers]\n\nHOW TO APPROACH THIS MEETING:\n  Opening: [What to emphasise given their known focus]\n  Watch for: [Any sensitivity; portfolio conflicts; known preferences]\n================================================================\n```\n\n## FINANCIAL REASONING STANDARD\n\nFor Slide 6 (Business Model) and any financial claims in the pitch:\n\n- Unit economics first: LTV:CAC must be stated with evidence level\n- Churn must be flagged if ASSUMED -- investors will ask\n- Market size must use bottom-up methodology, not top-down analyst TAM\n- Runway and use of funds must be specific and add up\n\n## ASSUMPTION TRACKING\n\nAfter any pitch output:\n\n- Surface any claim in the pitch that is ASSUMED rather than validated\n- Propose strengthening weak claims before the pitch meeting\n- Identify the strongest and weakest slides based on evidence quality\n\n## NEVER DO THESE\n\n- NEVER send a pitch deck without practicing the verbal narrative out loud\n  at least once -- the slide is the prompt; the verbal is the pitch\n- NEVER claim traction you cannot defend with specifics in a follow-up\n- NEVER show only the base-case financial scenario -- always have the\n  conservative scenario ready; investors will ask\n- NEVER leave the team slide generic -- it must explain WHY this team\n  has an advantage for this specific problem\n- NEVER use a top-down TAM (\"the market is $X trillion\") without a\n  bottom-up sanity check; investors know the top-down number is misleading\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":47,"description":51},{"author":48,"version":49,"plugin-commands":50},"Panaversity","1.0","\u002Fpitch","Activate for: pitch, investor deck, fundraising, pitch deck, pitch narrative, investor presentation, raise money, seed round, Series A, SAFE, convertible note, valuation, investor story, narrative architecture, pitch slides, executive summary, investor email, one pager, funding, angel investor, venture capital, VC pitch, pitch practice, hard questions, investor Q&A, term sheet, data room, investor brief. NOT for: unit economics or financial modelling (use financials), business model canvas (use canvas), market sizing (use market).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-pitch-skill-902f92e1","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill pitch",{"tool":64,"command":65},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill pitch",{"tool":67,"command":68},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill pitch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-pitch-skill-902f92e1\u002FSKILL.md",true,[],[73,100,127,158,186,220],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":42},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[75,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":42},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":139,"publishedAt":42},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,141,142,143,144,145,146,147,148,149,150,151,152,93,153,154,155,156,98,157],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":42},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[168,169,170,171,172,173,174,175,176,93,177,178,179,180,181,182,183,184,185,98],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":203,"publishedAt":42},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[192,195,200],{"categoryNo":193,"categoryName":194,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":196,"categoryName":197,"taxonomyType":198,"taxonomyTypeDesc":199},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":201,"categoryName":202,"taxonomyType":198,"taxonomyTypeDesc":199},"01JBSEEDCAT000000000000038","人力资源",[204,205,206,207,208,209,210,211,108,212,93,213,214,215,33,216,217,218,98,219],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":42},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[227,228,229,37,230,207,231,93,216,232,233,234,235,236,237,238,239,240,98,241],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]