[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MZFXV0B0B1EMYSR2FED5KQ":3,"skill-same:01M6MZFXV0B0B1EMYSR2FED5KQ":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},"01M6MZFXV0B0B1EMYSR2FED5KQ","financials",null,"Activate for: unit economics, CAC, LTV, customer acquisition cost, lifetime value, payback period, churn, gross margin, breakeven, runway, burn rate, MRR, ARR, monthly recurring revenue, annual recurring revenue, financial model, revenue model, revenue projections, fundraising model, scenario analysis, sensitivity analysis, how much money do I need, how long will the money last, how many customers to break even, what are my unit economics, Series A readiness. NOT for: business model canvas (use canvas), pitch deck (use pitch), competitive analysis (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-financials-skill-9dc61cb9\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"pitch","rate","break","my","recurring revenue","economics","unit","churn","revenue","canvas","scenario","revenue model","activate","runway","acquisition","model","how","analysis","customer","2026-11-10 10:12:30",false,"---\nname: financials\ndescription: >\n  Activate for: unit economics, CAC, LTV, customer acquisition cost, lifetime\n  value, payback period, churn, gross margin, breakeven, runway, burn rate,\n  MRR, ARR, monthly recurring revenue, annual recurring revenue, financial model,\n  revenue model, revenue projections, fundraising model, scenario analysis,\n  sensitivity analysis, how much money do I need, how long will the money last,\n  how many customers to break even, what are my unit economics, Series A readiness.\n  NOT for: business model canvas (use canvas), pitch deck (use pitch),\n  competitive analysis (use market).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Ffinancials\"\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\n- financial_model: unit_economics, current_state, milestones\n- business_model_canvas: revenue_streams, cost_structure\n- key_assumptions: business model assumptions (pricing, churn, CAC)\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 don't have enough data for a financial model yet. At the IDEA stage, unit economics are pure guesses. Consider running \u002Fdiscovery and \u002Fhypothesis first to get evidence-based inputs for your financial model.\"\n- DISCOVERY: Warning -- \"Financial modelling at the DISCOVERY stage is early. Your pricing and CAC assumptions are untested. Proceed, but mark everything as ASSUMED and flag high uncertainty.\"\n- VALIDATION: Financial modelling is appropriate -- you should have some evidence from assumption tests.\n- MVP: This is your focus stage. Financial models should be grounded in pilot data.\n- GROWTH: This is your focus stage. Financial models should use measured data.\n\n## DLA PROGRESSION CHECK\n\nIf venture.stage is IDEA or DISCOVERY and no validated pricing or customer data exists:\n\"You are building a financial model on assumed inputs. The outputs will\nlook precise but are unreliable. Focus on validating your pricing\nassumption and CAC before investing time in detailed financial models.\"\n\n## FINANCIAL MODELLING WORKFLOW\n\n### Task Types\n\nTYPE 1: UNIT ECONOMICS\n  Input: Pricing; CAC inputs; churn assumption; gross margin\n  Output: CAC, LTV, LTV:CAC, payback period, contribution margin, breakeven count\n\nTYPE 2: REVENUE AND RUNWAY MODEL\n  Input: Starting conditions + growth assumptions\n  Output: Month-by-month model (3 scenarios); breakeven date; fundraising trigger\n\nTYPE 3: FUNDRAISING MODEL\n  Input: Raise amount; current state; milestones\n  Output: What the capital buys; Series A readiness criteria; valuation framework\n\nTYPE 4: SENSITIVITY ANALYSIS\n  Input: Base model + key variable ranges\n  Output: How breakeven and runway shift under pessimistic assumptions\n\nTYPE 5: SERIES A READINESS ASSESSMENT\n  Input: Current metrics\n  Output: What metrics Series A investors expect; gap analysis; timeline to readiness\n\n### Unit Economics Output Structure\n\n```\nUNIT ECONOMICS MODEL\nVenture: [Name] | Currency: [USD \u002F local] | Date: [Date]\n================================================================\nCUSTOMER ACQUISITION COST (CAC):\n  [Method: list all cost inputs and calculation]\n  Founder-led CAC:        [Amount] (artificially low -- founder not at market rate)\n  Sustainable CAC:        [Amount] (use market-rate founder + any marketing spend)\n  [Note: use Sustainable CAC for all planning; Founder-led CAC understates true cost]\n\nLIFETIME VALUE (LTV):\n  MRR per customer:       [Amount]\n  Annual churn:           [%] (ASSUMED \u002F MEASURED -- specify)\n  Average lifetime:       [1 \u002F churn rate = years]\n  LTV (gross revenue):    [MRR x 12 x lifetime]\n  Gross margin:           [%]\n  LTV (gross profit):     [LTV x gross margin]\n  [WARNING: If churn is assumed, LTV is unreliable. Validate churn at Month 12.]\n\nKEY RATIOS:\n  LTV:CAC ratio:          [LTV \u002F CAC] -- [assessment: \u003C3 poor; 3-5 acceptable; >5 strong; >10 exceptional]\n  CAC payback:            [CAC \u002F monthly contribution = months]\n  Contribution margin:    [Revenue - variable cost = $ and %]\n\nCASH FLOW BREAKEVEN:\n  Monthly fixed costs:    [List major items + total]\n  Contribution\u002Fcustomer:  [Monthly revenue x gross margin]\n  Breakeven customer N:   [Fixed costs \u002F contribution per customer]\n  Timeline to breakeven:  [At current acquisition pace]\n\nKEY WARNINGS:\n  [Flag any assumption that is not yet measured]\n  [Flag any assumption where a 2x error would change the business viability]\n================================================================\n```\n\n### Three-Scenario Model Structure\n\nSCENARIO LABELS:\n  BASE:         Your realistic expectation\n  CONSERVATIVE: Half the growth; 1.5x the churn; 20% higher CAC\n  OPTIMISTIC:   1.5x the growth; half the churn; 20% lower CAC\n\nFOR EACH SCENARIO, SHOW MONTH BY MONTH:\n  New customers this month | Churned customers | Total customers\n  MRR | Monthly burn | Net cash flow | Cumulative cash balance\n  Runway remaining (months at current burn)\n\nMARK ON THE MODEL:\n  Breakeven date (MRR contribution >= burn)\n  Fundraising trigger point (runway \u003C 6 months)\n  Series A readiness (target ARR milestone)\n\n### Churn Warning Standard\n\nChurn is the most dangerous assumption in SaaS financial models.\n  At 10% annual churn: average lifetime = 10 years; LTV = 10x ARPU x margin\n  At 40% annual churn: average lifetime = 2.5 years; LTV = 2.5x ARPU x margin\n\nA 4x difference in churn produces a 4x difference in LTV.\nIf churn is assumed (not measured), flag the model as:\nHIGH UNCERTAINTY -- churn assumption is [X]%, not yet measured.\nModel validity depends heavily on this assumption. Validate at Month 12.\n\n### Series A Readiness Framework\n\nGeneral benchmarks (B2B SaaS -- adjust for sector and geography):\n  MINIMUM VIABLE METRICS for Series A conversation:\n  -- ARR: $1M-$3M (or local equivalent at similar purchasing power)\n  -- Growth rate: >100% year-over-year (or >15% month-over-month)\n  -- Churn: \u003C10% annual (net revenue retention ideally >100%)\n  -- LTV:CAC: >3x (ideally >5x)\n  -- At least 3-5 reference customers who will take investor calls\n\n## FINANCIAL REASONING STANDARD\n\nFor all financial outputs:\n- UNIT ECONOMICS FIRST: Before any revenue projections, establish\n  whether the unit economics work. If LTV:CAC \u003C 3, flag as a serious concern.\n- CHURN IS THE MOST DANGEROUS ASSUMPTION: Always test the churn\n  assumption explicitly. If churn is not yet measured, flag as HIGH RISK.\n- RUNWAY IS NON-NEGOTIABLE: Always show runway remaining.\n  If runway \u003C 6 months: flag as critical. If \u003C 3 months: flag as existential.\n- NEVER PRODUCE PROJECTIONS WITHOUT ASSUMPTIONS STATED:\n  Every revenue projection must list the growth rate, churn rate, and\n  pricing assumptions that produced it.\n\n## ASSUMPTION TRACKING\n\nAfter any financial output:\n- Surface the most critical untested financial assumption\n- Propose innov.local.md financial_model updates with new data\n- Always distinguish between ASSUMED and MEASURED inputs\n- Flag any input where a 2x error would change the conclusion\n\n## NEVER DO THESE\n\n- NEVER use founder-time CAC as the basis for fundraising models --\n  it understates the true cost of customer acquisition at scale\n- NEVER present revenue projections without stating all key assumptions\n  (growth rate, churn rate, pricing) in the same output\n- NEVER show a runway model without a fundraising trigger point --\n  the most common startup failure is running out of money because\n  the fundraising process started too late\n- NEVER call churn \"low\" without measured data -- assumed churn of 10%\n  is not low churn; it is an unvalidated assumption\n- NEVER model only the base case -- always include conservative scenario;\n  investors will ask \"what if growth is half of your base case?\"\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\n- financial_model: unit_economics, current_state, milestones\n- business_model_canvas: revenue_streams, cost_structure\n- key_assumptions: business model assumptions (pricing, churn, CAC)\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 don't have enough data for a financial model yet. At the IDEA stage, unit economics are pure guesses. Consider running \u002Fdiscovery and \u002Fhypothesis first to get evidence-based inputs for your financial model.\"\n- DISCOVERY: Warning -- \"Financial modelling at the DISCOVERY stage is early. Your pricing and CAC assumptions are untested. Proceed, but mark everything as ASSUMED and flag high uncertainty.\"\n- VALIDATION: Financial modelling is appropriate -- you should have some evidence from assumption tests.\n- MVP: This is your focus stage. Financial models should be grounded in pilot data.\n- GROWTH: This is your focus stage. Financial models should use measured data.\n\n## DLA PROGRESSION CHECK\n\nIf venture.stage is IDEA or DISCOVERY and no validated pricing or customer data exists:\n\"You are building a financial model on assumed inputs. The outputs will\nlook precise but are unreliable. Focus on validating your pricing\nassumption and CAC before investing time in detailed financial models.\"\n\n## FINANCIAL MODELLING WORKFLOW\n\n### Task Types\n\nTYPE 1: UNIT ECONOMICS\n  Input: Pricing; CAC inputs; churn assumption; gross margin\n  Output: CAC, LTV, LTV:CAC, payback period, contribution margin, breakeven count\n\nTYPE 2: REVENUE AND RUNWAY MODEL\n  Input: Starting conditions + growth assumptions\n  Output: Month-by-month model (3 scenarios); breakeven date; fundraising trigger\n\nTYPE 3: FUNDRAISING MODEL\n  Input: Raise amount; current state; milestones\n  Output: What the capital buys; Series A readiness criteria; valuation framework\n\nTYPE 4: SENSITIVITY ANALYSIS\n  Input: Base model + key variable ranges\n  Output: How breakeven and runway shift under pessimistic assumptions\n\nTYPE 5: SERIES A READINESS ASSESSMENT\n  Input: Current metrics\n  Output: What metrics Series A investors expect; gap analysis; timeline to readiness\n\n### Unit Economics Output Structure\n\n```\nUNIT ECONOMICS MODEL\nVenture: [Name] | Currency: [USD \u002F local] | Date: [Date]\n================================================================\nCUSTOMER ACQUISITION COST (CAC):\n  [Method: list all cost inputs and calculation]\n  Founder-led CAC:        [Amount] (artificially low -- founder not at market rate)\n  Sustainable CAC:        [Amount] (use market-rate founder + any marketing spend)\n  [Note: use Sustainable CAC for all planning; Founder-led CAC understates true cost]\n\nLIFETIME VALUE (LTV):\n  MRR per customer:       [Amount]\n  Annual churn:           [%] (ASSUMED \u002F MEASURED -- specify)\n  Average lifetime:       [1 \u002F churn rate = years]\n  LTV (gross revenue):    [MRR x 12 x lifetime]\n  Gross margin:           [%]\n  LTV (gross profit):     [LTV x gross margin]\n  [WARNING: If churn is assumed, LTV is unreliable. Validate churn at Month 12.]\n\nKEY RATIOS:\n  LTV:CAC ratio:          [LTV \u002F CAC] -- [assessment: \u003C3 poor; 3-5 acceptable; >5 strong; >10 exceptional]\n  CAC payback:            [CAC \u002F monthly contribution = months]\n  Contribution margin:    [Revenue - variable cost = $ and %]\n\nCASH FLOW BREAKEVEN:\n  Monthly fixed costs:    [List major items + total]\n  Contribution\u002Fcustomer:  [Monthly revenue x gross margin]\n  Breakeven customer N:   [Fixed costs \u002F contribution per customer]\n  Timeline to breakeven:  [At current acquisition pace]\n\nKEY WARNINGS:\n  [Flag any assumption that is not yet measured]\n  [Flag any assumption where a 2x error would change the business viability]\n================================================================\n```\n\n### Three-Scenario Model Structure\n\nSCENARIO LABELS:\n  BASE:         Your realistic expectation\n  CONSERVATIVE: Half the growth; 1.5x the churn; 20% higher CAC\n  OPTIMISTIC:   1.5x the growth; half the churn; 20% lower CAC\n\nFOR EACH SCENARIO, SHOW MONTH BY MONTH:\n  New customers this month | Churned customers | Total customers\n  MRR | Monthly burn | Net cash flow | Cumulative cash balance\n  Runway remaining (months at current burn)\n\nMARK ON THE MODEL:\n  Breakeven date (MRR contribution >= burn)\n  Fundraising trigger point (runway \u003C 6 months)\n  Series A readiness (target ARR milestone)\n\n### Churn Warning Standard\n\nChurn is the most dangerous assumption in SaaS financial models.\n  At 10% annual churn: average lifetime = 10 years; LTV = 10x ARPU x margin\n  At 40% annual churn: average lifetime = 2.5 years; LTV = 2.5x ARPU x margin\n\nA 4x difference in churn produces a 4x difference in LTV.\nIf churn is assumed (not measured), flag the model as:\nHIGH UNCERTAINTY -- churn assumption is [X]%, not yet measured.\nModel validity depends heavily on this assumption. Validate at Month 12.\n\n### Series A Readiness Framework\n\nGeneral benchmarks (B2B SaaS -- adjust for sector and geography):\n  MINIMUM VIABLE METRICS for Series A conversation:\n  -- ARR: $1M-$3M (or local equivalent at similar purchasing power)\n  -- Growth rate: >100% year-over-year (or >15% month-over-month)\n  -- Churn: \u003C10% annual (net revenue retention ideally >100%)\n  -- LTV:CAC: >3x (ideally >5x)\n  -- At least 3-5 reference customers who will take investor calls\n\n## FINANCIAL REASONING STANDARD\n\nFor all financial outputs:\n- UNIT ECONOMICS FIRST: Before any revenue projections, establish\n  whether the unit economics work. If LTV:CAC \u003C 3, flag as a serious concern.\n- CHURN IS THE MOST DANGEROUS ASSUMPTION: Always test the churn\n  assumption explicitly. If churn is not yet measured, flag as HIGH RISK.\n- RUNWAY IS NON-NEGOTIABLE: Always show runway remaining.\n  If runway \u003C 6 months: flag as critical. If \u003C 3 months: flag as existential.\n- NEVER PRODUCE PROJECTIONS WITHOUT ASSUMPTIONS STATED:\n  Every revenue projection must list the growth rate, churn rate, and\n  pricing assumptions that produced it.\n\n## ASSUMPTION TRACKING\n\nAfter any financial output:\n- Surface the most critical untested financial assumption\n- Propose innov.local.md financial_model updates with new data\n- Always distinguish between ASSUMED and MEASURED inputs\n- Flag any input where a 2x error would change the conclusion\n\n## NEVER DO THESE\n\n- NEVER use founder-time CAC as the basis for fundraising models --\n  it understates the true cost of customer acquisition at scale\n- NEVER present revenue projections without stating all key assumptions\n  (growth rate, churn rate, pricing) in the same output\n- NEVER show a runway model without a fundraising trigger point --\n  the most common startup failure is running out of money because\n  the fundraising process started too late\n- NEVER call churn \"low\" without measured data -- assumed churn of 10%\n  is not low churn; it is an unvalidated assumption\n- NEVER model only the base case -- always include conservative scenario;\n  investors will ask \"what if growth is half of your base case?\"\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":42,"description":46},{"author":43,"version":44,"plugin-commands":45},"Panaversity","1.0","\u002Ffinancials","Activate for: unit economics, CAC, LTV, customer acquisition cost, lifetime value, payback period, churn, gross margin, breakeven, runway, burn rate, MRR, ARR, monthly recurring revenue, annual recurring revenue, financial model, revenue model, revenue projections, fundraising model, scenario analysis, sensitivity analysis, how much money do I need, how long will the money last, how many customers to break even, what are my unit economics, Series A readiness. NOT for: business model canvas (use canvas), pitch deck (use pitch), competitive analysis (use market).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-financials-skill-9dc61cb9","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 financials",{"tool":59,"command":60},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill financials",{"tool":62,"command":63},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill financials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-financials-skill-9dc61cb9\u002FSKILL.md",true,[],[68,95,121,154,182,216],{"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":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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\".","MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[70,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"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'.","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,115,116,117,118,21,119,120],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","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":72,"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,144,145,146,147,148,88,149,150,151,152,93,153],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000011","运维与部署",[164,165,166,167,168,169,170,171,172,88,173,174,175,176,177,178,179,180,181,93],"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":199,"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",[188,191,196],{"categoryNo":189,"categoryName":190,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":197,"categoryName":198,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000038","人力资源",[200,201,202,203,204,205,206,207,103,208,88,209,210,211,30,212,213,214,93,215],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"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",[],[223,224,36,225,226,203,227,88,212,228,229,230,231,232,233,234,235,236,93,237],"steno mode","mode","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]