[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKA26049YF4EF0150W0J0V":3,"skill-same:01M6MKA26049YF4EF0150W0J0V":67},{"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":17,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6MKA26049YF4EF0150W0J0V","roast",null,"Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, \"convene the panel\", get a brutal second opinion before building something, or says \"\u002Froast\". Spins up a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) that attacks the idea from every angle, then a Judge returns one GO \u002F RESHAPE \u002F KILL verdict with the cheapest test to de-risk it.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-productivity-roast-skills-roast-skill-93595a28\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"stress-test","company","suite","context onboarding","judge","lens","de","investigator","get","analyst","go","me","grill","grill-me","up","persona","critic","pipeline","customer","2026-11-10 10:12:30",false,"---\nname: roast\ndescription: Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, \"convene the panel\", get a brutal second opinion before building something, or says \"\u002Froast\". Spins up a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) that attacks the idea from every angle, then a Judge returns one GO \u002F RESHAPE \u002F KILL verdict with the cheapest test to de-risk it.\nargument-hint: \"[the idea to roast]\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  build_pattern: \"Path-B persona skill — adversarial panel + deterministic verdict tools\"\n  distinct_from: \"andreessen (single market-first lens, not a panel); c-level boardroom (enterprise C-suite pipeline requiring company-context onboarding); grill-me (interrogates, no verdict)\"\n---\n\n# Roast — 5-Angle Idea Panel → One Verdict\n\n> **Portability:** Reasoning-led skill with 3 stdlib Python tools. No external APIs, no LLM calls in\n> scripts. Works in Claude Code CLI and Claude.ai web. The panel does the depth; the Judge does the call.\n\n## What this does\n\nClaude's default is to agree with you. `\u002Froast` is the opposite. It convenes a panel of five\nindependent reviewers — **The Critic, The Champion, The Analyst, The Investigator, and The\nCustomer** — who tear an idea apart and build it up from every angle, then a Judge synthesizes\neverything into one honest verdict. Use it before you sink time and money into building the wrong\nthing.\n\nThe panel is adversarial on purpose. No reviewer is allowed to hedge or be polite. The point is to\nsurface what you can't see because you're too close to it.\n\n## Step 1 — Frame the idea\n\nIf `$ARGUMENTS` contains the idea, start there. Then ask the user a tight set of clarifying\nquestions so the panel has real context to work with. Ask only what hasn't already been provided.\nKeep it to 3-4 questions max, in one batch:\n\n1. **The idea** in one or two sentences (what it is, what it does).\n2. **Who it's for** and **how it makes money** (the buyer + the price\u002Fmodel).\n3. **Your edge** — relevant skills, audience, or assets you already have.\n4. **Constraints** — budget, timeline, how fast you need first dollar.\n\nIf the user says \"just run it\" or gives you enough already, skip the questions and proceed. Don't\nover-interrogate. One round, then run the panel.\n\nAssemble the brief with `scripts\u002Fbrief_builder.py` — it normalizes the four load-bearing inputs into\none paragraph and tells you if anything critical is still missing before you spend five subagents:\n\n```bash\npython scripts\u002Fbrief_builder.py \\\n  --idea \"AI that drafts grant applications for small nonprofits from a 10-min intake call\" \\\n  --who \"1-3 person nonprofits with no grant writer\" \\\n  --money \"$99\u002Fmo SaaS\" --edge \"I ran a nonprofit for 8 years\" \\\n  --constraints \"bootstrapped, first dollar in 30 days\"\n```\n\nPaste the resulting brief verbatim into every panelist's prompt, so all five judge the same thing.\n\n## Step 2 — Run the 5-angle panel (5 reviewers, in parallel)\n\nSpin up **all five reviewers in parallel in a single message** (one Task call each,\n`subagent_type: general-purpose`). Paste the same brief into each, then give each its mandate below.\n\nEach panelist must return: a one-line stance, their 3-5 sharpest points, the single most important\nthing the user must hear, and a 1-10 score on their own dimension (1 = walk away, 10 = no-brainer).\n\n**1. The Critic — \"What kills this?\"**\n> You are The Critic on an idea panel. Assume this idea fails. Your job is to find the fatal flaws, the fastest way it dies, and the load-bearing assumptions that are probably wrong. Be ruthless and specific. No hedging, no \"but it could work.\" Attack the weakest points. THE BRIEF: [brief]\n\n**2. The Champion — \"What's the 10x upside?\"**\n> You are The Champion on an idea panel. Make the strongest possible case FOR this idea. Find the biggest upside, the 10x version, the adjacent opportunities and unlock points the founder isn't seeing. Fight for the potential. Be specific about where the real money and leverage could be. THE BRIEF: [brief]\n\n**3. The Analyst — \"Does the logic actually hold?\"**\n> You are The Analyst on an idea panel. Use NO outside research and NO web. Reason purely from first principles: does the core mechanism make sense, do the incentives line up, is the underlying logic sound, does the math even work in theory? Strip it to fundamentals and tell us if it holds together. THE BRIEF: [brief]\n\n**4. The Investigator — \"What does the real market say?\"**\n> You are The Investigator on an idea panel. Use web search. Bring real-world evidence: who the existing competitors are, market size or demand signals, what comparable products charge, whether this is validated by what's already out there or contradicted by it. Cite what you find. Is the real world saying yes or no? THE BRIEF: [brief]\n\n**5. The Customer — \"Would I actually pay?\"**\n> You are The Customer on an idea panel. Role-play the exact target customer described in the brief. React as them, in first person. Would you actually pay for this? What's your real objection? What would make you choose a competitor or just do nothing instead? What price feels right, and what would make you say yes today? Be the honest, slightly skeptical customer, not a cheerleader. THE BRIEF: [brief]\n\n## Step 3 — Call the verdict\n\nOnce all five return, YOU act as the Judge. Read every panelist's findings, weigh them, and\nsynthesize one decisive verdict. **Do not just average the scores.** Run the five scores through the\nsynthesizer so the call is reproducible weighting, not vibes — then name the real tension between the\nreviewers and resolve it in prose:\n\n```bash\npython scripts\u002Fverdict_synthesizer.py \\\n  --critic 4 --champion 8 --analyst 7 --investigator 5 --customer 6\n```\n\nThe tool weights demand (Customer) and survival (Critic) heaviest and the bull (Champion) lightest,\napplies hard gates (a Customer who won't pay, or a fatal flaw the Critic landed, vetoes a GO), and\nflags the widest disagreement as the tension you must resolve. Use its verdict + confidence as your\nspine; write the prose yourself.\n\nFold in the **economics lens** yourself: rough pricing, realistic time-to-first-dollar, and whether\nthe user can actually ship this fast given the edge they described. Then design the cheapest test\nfrom the riskiest assumption the panel surfaced:\n\n```bash\npython scripts\u002Fcheapest_test_designer.py --risk price --price 99\n```\n\nOutput the verdict in this exact shape:\n\n```\n## THE VERDICT: GO \u002F RESHAPE \u002F KILL\nConfidence: [low \u002F medium \u002F high]\n\n**The call in one line:** [the decision, plainly]\n\n**Why:** [2-3 sentences resolving the panel's tension]\n\n**Biggest risk:** [the single thing most likely to kill it]\n**Biggest upside:** [the strongest reason to do it]\n\n**Money read:** [rough price, time-to-first-dollar, can they ship fast]\n\n**The cheapest 48-hour test:** [the smallest, fastest thing they can do\nto validate the riskiest assumption BEFORE building anything]\n\n**If RESHAPE:** [the specific pivot that fixes the fatal flaw while keeping the upside]\n```\n\nThen list the five panel scores in one line: `Critic X\u002F10 · Champion X\u002F10 · Analyst X\u002F10 · Investigator X\u002F10 · Customer X\u002F10`.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fbrief_builder.py` | Normalizes the 4 load-bearing inputs into one shared brief; flags missing\u002Fthin inputs before the panel convenes. |\n| `scripts\u002Fverdict_synthesizer.py` | Weights the 5 panel scores (Customer + Critic heaviest, Champion lightest), applies veto gates, flags the real tension → GO \u002F RESHAPE \u002F KILL + confidence. |\n| `scripts\u002Fcheapest_test_designer.py` | Maps the riskiest assumption (demand\u002Fprice\u002Ffeasibility\u002Fdifferentiation\u002Fchannel\u002Fretention) to a concrete 48-hour test with pass\u002Ffail signals. |\n\n## References\n\n- [`references\u002Fadversarial_panel_canon.md`](references\u002Fadversarial_panel_canon.md) — why a diverse adversarial panel beats one reviewer (red-teaming, devil's advocacy, dialectical inquiry; 7 sources)\n- [`references\u002Fverdict_synthesis_method.md`](references\u002Fverdict_synthesis_method.md) — the weighting, the veto gates, and why you must not average (6 sources)\n- [`references\u002Fcheapest_test_canon.md`](references\u002Fcheapest_test_canon.md) — demand testing before building: smoke test, pre-sale, concierge, fake-door (7 sources)\n\n## Assets\n\n- [`assets\u002Froast_brief_worksheet.md`](assets\u002Froast_brief_worksheet.md) — fillable 4-input brief worksheet\n- [`assets\u002Fexample_roast_verdict.md`](assets\u002Fexample_roast_verdict.md) — a full worked roast (brief → 5 panel scores → tension → verdict → cheapest test)\n\n## Rules\n\n- Every reviewer stays in character. None of them hedges or softens. The value is in the friction.\n- The Judge must make an actual call. \"It depends\" is not a verdict. Pick GO, RESHAPE, or KILL and own it.\n- **Do not average the scores.** A high mean can hide a fatal split or a vetoed dimension — run the synthesizer and resolve the tension it names.\n- The cheapest 48-hour test is the most important output. It's how the user finds out if they're right without building the whole thing.\n- Keep the final verdict skimmable. The panel does the depth; the Judge does the decision.\n\n## Anti-Patterns To Reject\n\n- Softening the verdict to spare feelings (\"there's definitely something here…\"). If it's a KILL, say KILL.\n- Averaging the five scores into a mushy 6\u002F10 and calling it a day.\n- Letting the Champion's enthusiasm override a Customer who won't pay or a Critic who found the fatal flaw.\n- Ending on advice with no falsifiable test (\"go validate it\"). Name the test, the cost, and the pass\u002Ffail line.\n- Running the panel on a one-line brief so all five argue past each other.\n\n## Distinct From (don't reach for the wrong tool)\n\n- **`productivity\u002Fandreessen`** — a single market-first operator. `roast` is five independent lenses → a judge. Use andreessen when you specifically want the market-dominates thesis; use roast when you want 360° coverage.\n- **`c-level-advisor` boardroom \u002F `\u002Fcs:boardroom`** — an enterprise C-suite pipeline that needs `company-context.md` onboarding and outputs a board memo. `roast` is a zero-setup, solo-founder, 90-second gut check.\n- **`engineering\u002Fgrill-me`** — interrogates a plan one question at a time to reach shared understanding. It does not issue a GO\u002FKILL verdict. Roast judges; grill-me clarifies.\n\n---\n\n**Version:** 1.0.0\n**Build pattern:** Path-B persona skill — adversarial panel preserved + deterministic verdict tooling added.\n","# Roast — 5-Angle Idea Panel → One Verdict\n\n> **Portability:** Reasoning-led skill with 3 stdlib Python tools. No external APIs, no LLM calls in\n> scripts. Works in Claude Code CLI and Claude.ai web. The panel does the depth; the Judge does the call.\n\n## What this does\n\nClaude's default is to agree with you. `\u002Froast` is the opposite. It convenes a panel of five\nindependent reviewers — **The Critic, The Champion, The Analyst, The Investigator, and The\nCustomer** — who tear an idea apart and build it up from every angle, then a Judge synthesizes\neverything into one honest verdict. Use it before you sink time and money into building the wrong\nthing.\n\nThe panel is adversarial on purpose. No reviewer is allowed to hedge or be polite. The point is to\nsurface what you can't see because you're too close to it.\n\n## Step 1 — Frame the idea\n\nIf `$ARGUMENTS` contains the idea, start there. Then ask the user a tight set of clarifying\nquestions so the panel has real context to work with. Ask only what hasn't already been provided.\nKeep it to 3-4 questions max, in one batch:\n\n1. **The idea** in one or two sentences (what it is, what it does).\n2. **Who it's for** and **how it makes money** (the buyer + the price\u002Fmodel).\n3. **Your edge** — relevant skills, audience, or assets you already have.\n4. **Constraints** — budget, timeline, how fast you need first dollar.\n\nIf the user says \"just run it\" or gives you enough already, skip the questions and proceed. Don't\nover-interrogate. One round, then run the panel.\n\nAssemble the brief with `scripts\u002Fbrief_builder.py` — it normalizes the four load-bearing inputs into\none paragraph and tells you if anything critical is still missing before you spend five subagents:\n\n```bash\npython scripts\u002Fbrief_builder.py \\\n  --idea \"AI that drafts grant applications for small nonprofits from a 10-min intake call\" \\\n  --who \"1-3 person nonprofits with no grant writer\" \\\n  --money \"$99\u002Fmo SaaS\" --edge \"I ran a nonprofit for 8 years\" \\\n  --constraints \"bootstrapped, first dollar in 30 days\"\n```\n\nPaste the resulting brief verbatim into every panelist's prompt, so all five judge the same thing.\n\n## Step 2 — Run the 5-angle panel (5 reviewers, in parallel)\n\nSpin up **all five reviewers in parallel in a single message** (one Task call each,\n`subagent_type: general-purpose`). Paste the same brief into each, then give each its mandate below.\n\nEach panelist must return: a one-line stance, their 3-5 sharpest points, the single most important\nthing the user must hear, and a 1-10 score on their own dimension (1 = walk away, 10 = no-brainer).\n\n**1. The Critic — \"What kills this?\"**\n> You are The Critic on an idea panel. Assume this idea fails. Your job is to find the fatal flaws, the fastest way it dies, and the load-bearing assumptions that are probably wrong. Be ruthless and specific. No hedging, no \"but it could work.\" Attack the weakest points. THE BRIEF: [brief]\n\n**2. The Champion — \"What's the 10x upside?\"**\n> You are The Champion on an idea panel. Make the strongest possible case FOR this idea. Find the biggest upside, the 10x version, the adjacent opportunities and unlock points the founder isn't seeing. Fight for the potential. Be specific about where the real money and leverage could be. THE BRIEF: [brief]\n\n**3. The Analyst — \"Does the logic actually hold?\"**\n> You are The Analyst on an idea panel. Use NO outside research and NO web. Reason purely from first principles: does the core mechanism make sense, do the incentives line up, is the underlying logic sound, does the math even work in theory? Strip it to fundamentals and tell us if it holds together. THE BRIEF: [brief]\n\n**4. The Investigator — \"What does the real market say?\"**\n> You are The Investigator on an idea panel. Use web search. Bring real-world evidence: who the existing competitors are, market size or demand signals, what comparable products charge, whether this is validated by what's already out there or contradicted by it. Cite what you find. Is the real world saying yes or no? THE BRIEF: [brief]\n\n**5. The Customer — \"Would I actually pay?\"**\n> You are The Customer on an idea panel. Role-play the exact target customer described in the brief. React as them, in first person. Would you actually pay for this? What's your real objection? What would make you choose a competitor or just do nothing instead? What price feels right, and what would make you say yes today? Be the honest, slightly skeptical customer, not a cheerleader. THE BRIEF: [brief]\n\n## Step 3 — Call the verdict\n\nOnce all five return, YOU act as the Judge. Read every panelist's findings, weigh them, and\nsynthesize one decisive verdict. **Do not just average the scores.** Run the five scores through the\nsynthesizer so the call is reproducible weighting, not vibes — then name the real tension between the\nreviewers and resolve it in prose:\n\n```bash\npython scripts\u002Fverdict_synthesizer.py \\\n  --critic 4 --champion 8 --analyst 7 --investigator 5 --customer 6\n```\n\nThe tool weights demand (Customer) and survival (Critic) heaviest and the bull (Champion) lightest,\napplies hard gates (a Customer who won't pay, or a fatal flaw the Critic landed, vetoes a GO), and\nflags the widest disagreement as the tension you must resolve. Use its verdict + confidence as your\nspine; write the prose yourself.\n\nFold in the **economics lens** yourself: rough pricing, realistic time-to-first-dollar, and whether\nthe user can actually ship this fast given the edge they described. Then design the cheapest test\nfrom the riskiest assumption the panel surfaced:\n\n```bash\npython scripts\u002Fcheapest_test_designer.py --risk price --price 99\n```\n\nOutput the verdict in this exact shape:\n\n```\n## THE VERDICT: GO \u002F RESHAPE \u002F KILL\nConfidence: [low \u002F medium \u002F high]\n\n**The call in one line:** [the decision, plainly]\n\n**Why:** [2-3 sentences resolving the panel's tension]\n\n**Biggest risk:** [the single thing most likely to kill it]\n**Biggest upside:** [the strongest reason to do it]\n\n**Money read:** [rough price, time-to-first-dollar, can they ship fast]\n\n**The cheapest 48-hour test:** [the smallest, fastest thing they can do\nto validate the riskiest assumption BEFORE building anything]\n\n**If RESHAPE:** [the specific pivot that fixes the fatal flaw while keeping the upside]\n```\n\nThen list the five panel scores in one line: `Critic X\u002F10 · Champion X\u002F10 · Analyst X\u002F10 · Investigator X\u002F10 · Customer X\u002F10`.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fbrief_builder.py` | Normalizes the 4 load-bearing inputs into one shared brief; flags missing\u002Fthin inputs before the panel convenes. |\n| `scripts\u002Fverdict_synthesizer.py` | Weights the 5 panel scores (Customer + Critic heaviest, Champion lightest), applies veto gates, flags the real tension → GO \u002F RESHAPE \u002F KILL + confidence. |\n| `scripts\u002Fcheapest_test_designer.py` | Maps the riskiest assumption (demand\u002Fprice\u002Ffeasibility\u002Fdifferentiation\u002Fchannel\u002Fretention) to a concrete 48-hour test with pass\u002Ffail signals. |\n\n## References\n\n- [`references\u002Fadversarial_panel_canon.md`](references\u002Fadversarial_panel_canon.md) — why a diverse adversarial panel beats one reviewer (red-teaming, devil's advocacy, dialectical inquiry; 7 sources)\n- [`references\u002Fverdict_synthesis_method.md`](references\u002Fverdict_synthesis_method.md) — the weighting, the veto gates, and why you must not average (6 sources)\n- [`references\u002Fcheapest_test_canon.md`](references\u002Fcheapest_test_canon.md) — demand testing before building: smoke test, pre-sale, concierge, fake-door (7 sources)\n\n## Assets\n\n- [`assets\u002Froast_brief_worksheet.md`](assets\u002Froast_brief_worksheet.md) — fillable 4-input brief worksheet\n- [`assets\u002Fexample_roast_verdict.md`](assets\u002Fexample_roast_verdict.md) — a full worked roast (brief → 5 panel scores → tension → verdict → cheapest test)\n\n## Rules\n\n- Every reviewer stays in character. None of them hedges or softens. The value is in the friction.\n- The Judge must make an actual call. \"It depends\" is not a verdict. Pick GO, RESHAPE, or KILL and own it.\n- **Do not average the scores.** A high mean can hide a fatal split or a vetoed dimension — run the synthesizer and resolve the tension it names.\n- The cheapest 48-hour test is the most important output. It's how the user finds out if they're right without building the whole thing.\n- Keep the final verdict skimmable. The panel does the depth; the Judge does the decision.\n\n## Anti-Patterns To Reject\n\n- Softening the verdict to spare feelings (\"there's definitely something here…\"). If it's a KILL, say KILL.\n- Averaging the five scores into a mushy 6\u002F10 and calling it a day.\n- Letting the Champion's enthusiasm override a Customer who won't pay or a Critic who found the fatal flaw.\n- Ending on advice with no falsifiable test (\"go validate it\"). Name the test, the cost, and the pass\u002Ffail line.\n- Running the panel on a one-line brief so all five argue past each other.\n\n## Distinct From (don't reach for the wrong tool)\n\n- **`productivity\u002Fandreessen`** — a single market-first operator. `roast` is five independent lenses → a judge. Use andreessen when you specifically want the market-dominates thesis; use roast when you want 360° coverage.\n- **`c-level-advisor` boardroom \u002F `\u002Fcs:boardroom`** — an enterprise C-suite pipeline that needs `company-context.md` onboarding and outputs a board memo. `roast` is a zero-setup, solo-founder, 90-second gut check.\n- **`engineering\u002Fgrill-me`** — interrogates a plan one question at a time to reach shared understanding. It does not issue a GO\u002FKILL verdict. Roast judges; grill-me clarifies.\n\n---\n\n**Version:** 1.0.0\n**Build pattern:** Path-B persona skill — adversarial panel preserved + deterministic verdict tooling added.\n",{"name":5,"license":14,"metadata":42,"description":7,"argument-hint":46},{"version":43,"build_pattern":44,"distinct_from":45},"1.0.0","Path-B persona skill — adversarial panel + deterministic verdict tools","andreessen (single market-first lens, not a panel); c-level boardroom (enterprise C-suite pipeline requiring company-context onboarding); grill-me (interrogates, no verdict)","[the idea to roast]","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-productivity-roast-skills-roast-skill-93595a28","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill roast",{"tool":59,"command":60},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill roast",{"tool":62,"command":63},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill roast","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-productivity-roast-skills-roast-skill-93595a28\u002FSKILL.md",true,[],[68,94,121,153,181,215],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":37},"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\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[70,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":37},"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'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,29,115,116,117,118,119,120],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":37},"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",[127,132],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":133,"categoryName":134,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,137,138,139,140,141,142,143,35,144,145,146,147,87,148,149,150,151,92,152],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"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":162,"publishedAt":37},"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",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000011","运维与部署",[163,164,165,166,167,168,169,170,171,87,172,173,174,175,176,177,178,179,180,92],"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":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":198,"publishedAt":37},"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",[187,190,195],{"categoryNo":188,"categoryName":189,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":191,"categoryName":192,"taxonomyType":193,"taxonomyTypeDesc":194},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":196,"categoryName":197,"taxonomyType":193,"taxonomyTypeDesc":194},"01JBSEEDCAT000000000000038","人力资源",[199,200,201,202,203,204,205,206,103,207,87,32,208,209,210,211,212,213,92,214],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","engineer","general","activate","do","task","cv","letter",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":37},"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",[],[222,223,36,224,225,202,226,87,211,227,228,229,230,231,232,233,234,235,92,236],"steno mode","mode","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]