[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFHWXW091MJ3V4SA557H8D":3,"skill-same:01M6MFHWXW091MJ3V4SA557H8D":80},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":13,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6MFHWXW091MJ3V4SA557H8D","commercial-skills",null,"Use when reviewing, approving, or designing commercial motion — pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP\u002FRFI response, bookings forecast. Triggers on \"review this deal\", \"should we discount\", \"pricing model\", \"partner economics\", \"RFP response\", \"bookings forecast\", \"channel mix\". Forks context to route to one of seven Commercial sub-skills (pricing-strategist, deal-desk, partnerships-architect, channel-economics, commercial-policy, rfp-responder, commercial-forecaster) and returns a digest. Distinct from business-growth (sales execution) and c-level-advisor\u002Fcro-advisor (strategic CRO judgment).","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-gemini-skills-commercial-skills-skill-52ffe3a4\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"commercial skills","commercial","rfi","mix","pricing model","economics","judgment","digest","deal review","route","advisor","opencode","review","orchestrator","context","returns","model","Responder","code","cli","2026-11-10 10:12:30",false,"---\nname: commercial-skills\ndescription: Use when reviewing, approving, or designing commercial motion — pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP\u002FRFI response, bookings forecast. Triggers on \"review this deal\", \"should we discount\", \"pricing model\", \"partner economics\", \"RFP response\", \"bookings forecast\", \"channel mix\". Forks context to route to one of seven Commercial sub-skills (pricing-strategist, deal-desk, partnerships-architect, channel-economics, commercial-policy, rfp-responder, commercial-forecaster) and returns a digest. Distinct from business-growth (sales execution) and c-level-advisor\u002Fcro-advisor (strategic CRO judgment).\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [commercial, pricing, deal-desk, partnerships, channel, rfp, forecast, cro, orchestrator]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Commercial — Domain Orchestrator\n\nThe Commercial surface is **per-deal economics and packaging**: how the company prices, packages, approves, and forecasts revenue. This orchestrator forks its context, routes your inquiry to one of seven sub-skills, then returns a digest. Heavy intake (RFP PDFs, pipeline exports, partner agreements) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"We're losing deals on price — should we drop prices or repackage?\" | `pricing-strategist` |\n| \"Can we approve a 40% discount on this Enterprise deal?\" | `deal-desk` |\n| \"Should we sign with this reseller? What's their tier?\" | `partnerships-architect` |\n| \"Is our partner channel actually profitable?\" | `channel-economics` |\n| \"What should our standard discount matrix look like?\" | `commercial-policy` |\n| \"Help me respond to this 60-page RFP\" | `rfp-responder` |\n| \"What's our Q4 bookings forecast at current conversion?\" | `commercial-forecaster` |\n\n## Routing logic (deterministic)\n\nSame two-signal threshold pattern as `business-operations-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in follow-up turn.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PRICING** | pricing, price, packaging, tier, WTP, willingness to pay, Van Westendorp, value pricing | `pricing-strategist` |\n| **DEAL** | deal, discount, approval, margin, T&Cs, redline, exception, MSA | `deal-desk` |\n| **PARTNERSHIP** | partner, reseller, OEM, co-sell, joint GTM, revenue share, channel agreement | `partnerships-architect` |\n| **CHANNEL_ECON** | channel mix, cost to serve, channel ROI, direct vs partner, channel economics | `channel-economics` |\n| **POLICY** | commercial policy, discount matrix, T&C library, exception policy, deal framework | `commercial-policy` |\n| **RFP** | RFP, RFI, RFQ, proposal request, vendor questionnaire, security questionnaire | `rfp-responder` |\n| **FORECAST** | forecast, bookings, billings, ARR, NRR forecast, pipeline math, funnel projection | `commercial-forecaster` |\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the SaaS pricing \u002F deal desk canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nCheck the user's working directory first:\n- Is there a deal record, pricing comp table, RFP doc, or pipeline export already in the workspace?\n- Does the inquiry already disambiguate the lane (e.g., \"review this 60-page RFP\" — that's `rfp-responder`, no question needed)?\n- Is there an artifact filename that resolves the lane (`pipeline-Q4.csv` → forecast; `MSA-redline.docx` → deal)?\n\nIf the workspace resolves the lane, **route silently**.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle. Always recommend.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Csignal-table rationale>]\n\n(Confirm, or override?)\n```\n\n### Step 3 — Decision-tree walk for multi-lane inquiries\n\nIf the inquiry legitimately crosses two lanes (e.g., \"this RFP wants a discount we don't normally give\" = RFP + DEAL + maybe POLICY), walk depth-first:\n\n1. Highest-confidence lane first → run sub-skill in forked context → digest\n2. Ask: \"Now run [second lane]? Recommended: yes, because [dependency].\"\n3. Confirm before chaining.\n\nNever silently chain.\n\n### Step 4 — Invoke sub-skill in forked context\n\nForward original prompt + structured inputs (pipeline CSV, RFP doc path, pricing comp table, MSA redline).\n\n### Step 5 — Return digest with cited canon challenge\n\n≤ 200 words: analyzed, top 3 findings (anchored to canon citation), top 3 next actions (named approver where applicable), artifact path, and **one grill challenge** for the user. Examples:\n\n- \"Your deal scorecard shows 38% margin after discount. Skok's For Entrepreneurs benchmark says SaaS deals \u003C 70% gross margin pre-discount need scrutiny. Did you model fulfillment cost or just COGS?\"\n- \"Your packaging has 14 features in Better and 16 in Best. Madhavan Ramanujam (Monetizing Innovation): tiers with no clear differentiator make 70% of customers pick the cheapest. What's the one feature that forces an upgrade?\"\n\n## Forcing-question library (grill-with-docs pattern)\n\nGrill the user on lane-defining decisions before invoking the sub-skill. One per turn, recommended answer, canon citation:\n\n- **PRICING lane**: \"Before picking a model: is your customer paying for outcomes, seats, or usage? Recommended: outcomes (value-based) if you can measure them. Anti-pattern (Ramanujam 2016 *Monetizing Innovation*): seat-based pricing on a usage-variable product caps your TAM at 20% of WTP.\"\n- **DEAL lane**: \"Before approving: what's the gross margin at full discount, **and** what does next quarter's pipeline look like at the same terms? Recommended: model both. Anti-pattern (Tunguz benchmarks): one 40% precedent reshapes 3 quarters of pipeline.\"\n- **FORECAST lane**: \"Before forecasting: are you using stage-conversion rates from the last 4 quarters, or the last 12? Recommended: last 4 weighted heavier. Anti-pattern (Skok, OpenView): equal-weighting 12 months hides the recent slowdown.\"\n- **PARTNERSHIP lane**: \"Before signing: does the partner have **independent demand**, or are they reselling our pipeline? Recommended: insist on indep demand evidence. Anti-pattern (Forrester channel research): channel-led deals from your own pipeline cost more than direct.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. User has commercial authority OR is preparing analysis for someone who does.\n2. User wants **deterministic decision support**, not the final answer — the human approves the deal, sets the price, signs the partner.\n3. Inputs may be partial — every sub-skill ships templated dummy data so the user can see the shape before filling in their own.\n\n## Non-goals\n\n- Not a CRM, CPQ system, or contract repository.\n- Does not auto-approve deals. Every output is **a score + recommendation + human-approver routing**.\n- Does not store deal history across sessions.\n\n## Distinct from\n\n- **`business-growth\u002Fsales-engineer`** — that's the **technical sale** (demos, POCs). Commercial is **economic shape** of the deal.\n- **`business-growth\u002Frevenue-operations`** — that's **process** (lead routing, SDR motion). Commercial is **per-deal economics + policy**.\n- **`business-growth\u002Fcontract-and-proposal-writer`** — that's **authoring** prose. Commercial is **decision logic + structured response**.\n- **`c-level-advisor\u002Fcro-advisor`** — that's strategic CRO judgment (\"when do we hire VP Sales?\"). Commercial is tactical (\"approve this discount\").\n- **`finance\u002Ffinancial-analysis`** — that's **close + report**. Commercial is **forecast + per-deal economics**.\n\n## Output artifacts\n\n| Sub-skill | Artifact |\n|---|---|\n| pricing-strategist | `pricing_model.md` + `wtp_analysis.json` |\n| deal-desk | `deal_scorecard.md` + `discount_approval_routing.json` |\n| partnerships-architect | `partner_tier_assignment.md` + `revshare_model.json` |\n| channel-economics | `channel_mix_analysis.md` + `cost_to_serve.json` |\n| commercial-policy | `commercial_policy.md` (discount matrix + exception flow) |\n| rfp-responder | `rfp_response.md` + `winrate_estimate.json` |\n| commercial-forecaster | `forecast.md` + `pipeline_math.json` |\n\n## Anti-patterns (do not)\n\n- ❌ Recommend a specific price — recommend a **range + model**, user picks the number\n- ❌ Auto-approve discounts above policy — every >X% discount routes to a named human approver\n- ❌ Generate an RFP response without proof points the user can verify\n- ❌ Forecast bookings without surfacing the **conversion assumption** explicitly\n- ❌ Run all 7 sub-skills \"to be thorough\" — pick one, digest, chain if needed\n\n## References\n\n- SaaS pricing canon: Tomasz Tunguz, David Skok, Bessemer Venture Partners\n- Deal desk: SaaStr playbooks, Winning by Design\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n","# Commercial — Domain Orchestrator\n\nThe Commercial surface is **per-deal economics and packaging**: how the company prices, packages, approves, and forecasts revenue. This orchestrator forks its context, routes your inquiry to one of seven sub-skills, then returns a digest. Heavy intake (RFP PDFs, pipeline exports, partner agreements) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"We're losing deals on price — should we drop prices or repackage?\" | `pricing-strategist` |\n| \"Can we approve a 40% discount on this Enterprise deal?\" | `deal-desk` |\n| \"Should we sign with this reseller? What's their tier?\" | `partnerships-architect` |\n| \"Is our partner channel actually profitable?\" | `channel-economics` |\n| \"What should our standard discount matrix look like?\" | `commercial-policy` |\n| \"Help me respond to this 60-page RFP\" | `rfp-responder` |\n| \"What's our Q4 bookings forecast at current conversion?\" | `commercial-forecaster` |\n\n## Routing logic (deterministic)\n\nSame two-signal threshold pattern as `business-operations-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in follow-up turn.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PRICING** | pricing, price, packaging, tier, WTP, willingness to pay, Van Westendorp, value pricing | `pricing-strategist` |\n| **DEAL** | deal, discount, approval, margin, T&Cs, redline, exception, MSA | `deal-desk` |\n| **PARTNERSHIP** | partner, reseller, OEM, co-sell, joint GTM, revenue share, channel agreement | `partnerships-architect` |\n| **CHANNEL_ECON** | channel mix, cost to serve, channel ROI, direct vs partner, channel economics | `channel-economics` |\n| **POLICY** | commercial policy, discount matrix, T&C library, exception policy, deal framework | `commercial-policy` |\n| **RFP** | RFP, RFI, RFQ, proposal request, vendor questionnaire, security questionnaire | `rfp-responder` |\n| **FORECAST** | forecast, bookings, billings, ARR, NRR forecast, pipeline math, funnel projection | `commercial-forecaster` |\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the SaaS pricing \u002F deal desk canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nCheck the user's working directory first:\n- Is there a deal record, pricing comp table, RFP doc, or pipeline export already in the workspace?\n- Does the inquiry already disambiguate the lane (e.g., \"review this 60-page RFP\" — that's `rfp-responder`, no question needed)?\n- Is there an artifact filename that resolves the lane (`pipeline-Q4.csv` → forecast; `MSA-redline.docx` → deal)?\n\nIf the workspace resolves the lane, **route silently**.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle. Always recommend.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Csignal-table rationale>]\n\n(Confirm, or override?)\n```\n\n### Step 3 — Decision-tree walk for multi-lane inquiries\n\nIf the inquiry legitimately crosses two lanes (e.g., \"this RFP wants a discount we don't normally give\" = RFP + DEAL + maybe POLICY), walk depth-first:\n\n1. Highest-confidence lane first → run sub-skill in forked context → digest\n2. Ask: \"Now run [second lane]? Recommended: yes, because [dependency].\"\n3. Confirm before chaining.\n\nNever silently chain.\n\n### Step 4 — Invoke sub-skill in forked context\n\nForward original prompt + structured inputs (pipeline CSV, RFP doc path, pricing comp table, MSA redline).\n\n### Step 5 — Return digest with cited canon challenge\n\n≤ 200 words: analyzed, top 3 findings (anchored to canon citation), top 3 next actions (named approver where applicable), artifact path, and **one grill challenge** for the user. Examples:\n\n- \"Your deal scorecard shows 38% margin after discount. Skok's For Entrepreneurs benchmark says SaaS deals \u003C 70% gross margin pre-discount need scrutiny. Did you model fulfillment cost or just COGS?\"\n- \"Your packaging has 14 features in Better and 16 in Best. Madhavan Ramanujam (Monetizing Innovation): tiers with no clear differentiator make 70% of customers pick the cheapest. What's the one feature that forces an upgrade?\"\n\n## Forcing-question library (grill-with-docs pattern)\n\nGrill the user on lane-defining decisions before invoking the sub-skill. One per turn, recommended answer, canon citation:\n\n- **PRICING lane**: \"Before picking a model: is your customer paying for outcomes, seats, or usage? Recommended: outcomes (value-based) if you can measure them. Anti-pattern (Ramanujam 2016 *Monetizing Innovation*): seat-based pricing on a usage-variable product caps your TAM at 20% of WTP.\"\n- **DEAL lane**: \"Before approving: what's the gross margin at full discount, **and** what does next quarter's pipeline look like at the same terms? Recommended: model both. Anti-pattern (Tunguz benchmarks): one 40% precedent reshapes 3 quarters of pipeline.\"\n- **FORECAST lane**: \"Before forecasting: are you using stage-conversion rates from the last 4 quarters, or the last 12? Recommended: last 4 weighted heavier. Anti-pattern (Skok, OpenView): equal-weighting 12 months hides the recent slowdown.\"\n- **PARTNERSHIP lane**: \"Before signing: does the partner have **independent demand**, or are they reselling our pipeline? Recommended: insist on indep demand evidence. Anti-pattern (Forrester channel research): channel-led deals from your own pipeline cost more than direct.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. User has commercial authority OR is preparing analysis for someone who does.\n2. User wants **deterministic decision support**, not the final answer — the human approves the deal, sets the price, signs the partner.\n3. Inputs may be partial — every sub-skill ships templated dummy data so the user can see the shape before filling in their own.\n\n## Non-goals\n\n- Not a CRM, CPQ system, or contract repository.\n- Does not auto-approve deals. Every output is **a score + recommendation + human-approver routing**.\n- Does not store deal history across sessions.\n\n## Distinct from\n\n- **`business-growth\u002Fsales-engineer`** — that's the **technical sale** (demos, POCs). Commercial is **economic shape** of the deal.\n- **`business-growth\u002Frevenue-operations`** — that's **process** (lead routing, SDR motion). Commercial is **per-deal economics + policy**.\n- **`business-growth\u002Fcontract-and-proposal-writer`** — that's **authoring** prose. Commercial is **decision logic + structured response**.\n- **`c-level-advisor\u002Fcro-advisor`** — that's strategic CRO judgment (\"when do we hire VP Sales?\"). Commercial is tactical (\"approve this discount\").\n- **`finance\u002Ffinancial-analysis`** — that's **close + report**. Commercial is **forecast + per-deal economics**.\n\n## Output artifacts\n\n| Sub-skill | Artifact |\n|---|---|\n| pricing-strategist | `pricing_model.md` + `wtp_analysis.json` |\n| deal-desk | `deal_scorecard.md` + `discount_approval_routing.json` |\n| partnerships-architect | `partner_tier_assignment.md` + `revshare_model.json` |\n| channel-economics | `channel_mix_analysis.md` + `cost_to_serve.json` |\n| commercial-policy | `commercial_policy.md` (discount matrix + exception flow) |\n| rfp-responder | `rfp_response.md` + `winrate_estimate.json` |\n| commercial-forecaster | `forecast.md` + `pipeline_math.json` |\n\n## Anti-patterns (do not)\n\n- ❌ Recommend a specific price — recommend a **range + model**, user picks the number\n- ❌ Auto-approve discounts above policy — every >X% discount routes to a named human approver\n- ❌ Generate an RFP response without proof points the user can verify\n- ❌ Forecast bookings without surfacing the **conversion assumption** explicitly\n- ❌ Run all 7 sub-skills \"to be thorough\" — pick one, digest, chain if needed\n\n## References\n\n- SaaS pricing canon: Tomasz Tunguz, David Skok, Bessemer Venture Partners\n- Deal desk: SaaStr playbooks, Winning by Design\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n",{"name":5,"tags":43,"author":51,"context":52,"license":14,"version":53,"description":7,"compatible_tools":54},[19,44,45,46,47,48,49,50,31],"pricing","deal-desk","partnerships","channel","rfp","forecast","cro","claude-code-skills","fork","2.8.0",[55,56,57,58,29,59],"claude-code","codex-cli","cursor","antigravity","gemini-cli","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-commercial-skills-skill-52ffe3a4","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill commercial-skills",{"tool":72,"command":73},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill commercial-skills",{"tool":75,"command":76},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill commercial-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-commercial-skills-skill-52ffe3a4\u002FSKILL.md",true,[],[81,106,133,166,194,229],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":38},"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",[],[83,88,89,90,91,36,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"github","ai agents","web","notes","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":38},"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",[],[114,115,116,37,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"vardoger analyze","analyze","directory","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":147,"publishedAt":38},"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",[139,144],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":145,"categoryName":146,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,149,150,151,152,153,154,155,156,157,158,159,160,99,161,162,163,164,104,165],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":38},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000011","运维与部署",[176,177,178,179,180,181,182,183,184,99,185,186,187,188,189,190,191,192,193,104],"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":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":211,"publishedAt":38},"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",[200,203,208],{"categoryNo":201,"categoryName":202,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":204,"categoryName":205,"taxonomyType":206,"taxonomyTypeDesc":207},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":209,"categoryName":210,"taxonomyType":206,"taxonomyTypeDesc":207},"01JBSEEDCAT000000000000038","人力资源",[212,213,214,215,216,217,218,219,115,220,99,221,222,223,224,225,226,227,104,228],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":235,"publishedAt":38},"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",[],[236,237,238,239,240,215,241,99,225,242,243,244,245,246,247,248,249,250,104,251],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]