[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N03P0BBNK6THD9YSWF5CBG":3,"skill-same:01M6N03P0BBNK6THD9YSWF5CBG":73},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6N03P0BBNK6THD9YSWF5CBG","prd",null,"Activate for: PRD, product requirements document, product requirements, full requirements, initiative doc, initiative requirements, platform change, new product, product launch, major release, quarterly initiative, program brief, product vision doc, comprehensive requirements, cross-functional alignment doc, launch plan requirements, multi-team initiative. NOT for: single-feature specifications (use official \u002Fwrite-spec), roadmap planning (use official \u002Froadmap-update), sprint planning (use official \u002Fsprint-planning).","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-product-strategy-skills-prd-skill-17c977f3\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"sprint-planning","product vision","functional","Product Requirements","sprint","full","activate","alignment","roadmap","write","change","plan","team","doc","brief","product","release","update","official","2026-11-10 10:12:30",false,"---\nname: prd\ndescription: >\n  Activate for: PRD, product requirements document, product requirements,\n  full requirements, initiative doc, initiative requirements, platform change,\n  new product, product launch, major release, quarterly initiative, program\n  brief, product vision doc, comprehensive requirements, cross-functional\n  alignment doc, launch plan requirements, multi-team initiative.\n  NOT for: single-feature specifications (use official \u002Fwrite-spec),\n  roadmap planning (use official \u002Froadmap-update), sprint planning\n  (use official \u002Fsprint-planning).\nlicense: Apache-2.0\nargument-hint: \"\u003Cinitiative name>\"\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fprd\"\n---\n\n## CONTEXT LOADING\n\nBefore generating a PRD, load `product.local.md` for product context,\npersonas, engineering team details, and stakeholder map. If not configured,\nask the user for product name, personas, and engineering context.\n\n## PRD WORKFLOW\n\n### When to Write a PRD (vs. a Feature Spec)\n\nWrite a SPEC when: One feature, one team, one-to-three sprints\nWrite a PRD when: Multiple features, multiple teams, major platform\nchange, new product area, or executive alignment required\n\nIf unsure, ask the user: \"Is this one feature for one team (use \u002Fwrite-spec)\nor a multi-team initiative (use \u002Fprd)?\"\n\n### PRD Sections -- Full Template\n\nSECTION 1: EXECUTIVE SUMMARY\n[3-4 sentences only]\nWhat: [What are we building -- in plain language]\nWhy: [What commercial or user problem does it solve]\nWhen: [Target delivery -- quarter, not date unless confirmed]\nWin: [How we will know it worked -- headline metric]\n\nSECTION 2: BUSINESS CONTEXT\nProblem statement:\n[The specific user pain or business gap -- with evidence]\n\nCommercial evidence (use what is available):\n\n- Lost deals: \"[N] deals cited [issue] as blocker in [period]\"\n- Customer requests: \"[N] requests logged; [source]\"\n- Competitive gap: \"[Competitor] offers [feature]; we do not\"\n- Revenue opportunity: \"[Estimate] ARR blocked or at risk\"\n- Support cost: \"[N] tickets \u002F [hours] PM support time per [period]\"\n\nStrategic fit:\n[How this initiative connects to the company\u002Fproduct strategy.\nOne sentence. If you cannot write this sentence, the initiative\nmay not belong in the roadmap.]\n\nSuccess metrics:\nPrimary (measure at 6-12 months post-launch):\n[Specific, measurable outcome: not \"improve NPS\" but \"enterprise NPS\nfrom 42 to 52 within 6 months of launch\"]\n\n    Secondary (measure at 30-90 days):\n      [Leading indicators: adoption rate; support volume change;\n       sales cycle impact]\n\n    Failure threshold:\n      [What outcome would cause us to reconsider or change direction?\n       Define before launch, not after.]\n\nSECTION 3: USER REQUIREMENTS\nPrimary persona:\nName: [Persona name from product.local.md]\nRole: [Job title \u002F function]\nCurrent state: [How they handle this today -- the workaround]\nDesired state: [What \"10\u002F10\" looks like for them]\nKey user stories: [Top 3 as \"As a... I want... So that...\"]\n\nSecondary persona (if applicable):\n[Same structure -- brief]\n\nUser journey map:\nCurrent state: [Step-by-step of how they do it today]\nPain points: [Where the friction is in the current flow]\nFuture state: [Step-by-step with the new product in place]\n\nSECTION 4: FUNCTIONAL REQUIREMENTS\nFor each feature\u002Fcapability in scope:\n\nFeature [N]: [Name]\nPriority: MUST \u002F SHOULD \u002F COULD (MoSCoW)\nDescription: [What it does]\nKey flows: [Primary user flows]\nDependencies: [Other features or teams this depends on]\nSpec ref: [Link to individual spec if exists]\n\nRule: Every item labelled MUST must ship before launch.\nIf more than 60% of items are labelled MUST, the scope is too large.\n\nSECTION 5: NON-FUNCTIONAL REQUIREMENTS\nPerformance:\n[Page load time; API response time; export generation time -- with numbers]\n\nReliability:\n[Uptime SLA; error rate tolerance; recovery time objective]\n\nSecurity:\n[Authentication requirements; data encryption; audit requirements;\npenetration testing if required]\n\nCompliance:\n[GDPR \u002F CCPA data handling; SOC 2 implications; HIPAA if applicable;\nsector-specific regulations]\n\nAccessibility:\n[WCAG standard; keyboard navigation; screen reader requirements]\n\nScalability:\n[Expected load at launch; growth assumptions; capacity planning notes]\n\nSECTION 6: TECHNICAL ARCHITECTURE NOTES\n[High-level approach -- not implementation detail]\n\n- Key technical decisions already made\n- Platform or infrastructure dependencies\n- Third-party integrations required\n- Data model changes (high level)\n- Migration requirements (existing users \u002F data)\n- Feature flags required\n\nNote: This section is written by PM in collaboration with engineering.\nIt must be reviewed and confirmed by the engineering lead before\nthe PRD is marked as REVIEW-ready.\n\nSECTION 7: GO-TO-MARKET REQUIREMENTS\nDocumentation:\n[Customer-facing docs required; doc owner; due date]\n\nCustomer Success enablement:\n[What CS needs to know before launch; training requirements]\n\nSales enablement:\n[What sales needs to demo\u002Fdiscuss this feature; talking points]\n\nPricing:\n[Is this in the current plan? New tier? Add-on? Pricing team review needed?]\n\nBeta programme:\n[Which customers; how many; invite criteria; beta start date; GA date]\n\nCustomer communication:\n[Announcement channel; timing; who sends it]\n\nSECTION 8: LAUNCH PLAN\nPhased rollout:\nPhase 1 -- Beta: [Audience; dates; success gates for Phase 2]\nPhase 2 -- GA: [Full availability; announcement plan]\nRollback plan: [How to undo if critical bug discovered post-launch]\n\nFeature flags:\n[Required flags; rollout percentages; sunset plan]\n\nMonitoring:\n[What metrics are watched in the first 48 hours post-launch;\nwho is on-call; escalation path]\n\nSECTION 9: DEPENDENCIES AND RISKS\nExternal dependencies:\n| Dependency | Owner | Status | Risk if delayed |\n|---|---|---|---|\n| [Third party \u002F platform team] | [Name] | [On track \u002F TBD] | [Impact] |\n\nTop risks:\n| Risk | Likelihood | Impact | Mitigation |\n|---|---|---|---|\n| [Risk description] | H\u002FM\u002FL | H\u002FM\u002FL | [Specific mitigation action] |\n\nSECTION 10: OPEN QUESTIONS\n[Numbered; owner; due date]\nAll questions must be resolved before PRD moves to REFINED status.\n\nAPPENDICES (include as available)\nA. Competitive analysis\nB. User research excerpts\nC. Technical discovery notes\nD. Prior art \u002F related specs\n\n### PRD Status Gates\n\nDRAFT: All sections present; some may be incomplete\nREVIEW: All sections complete; open questions have owners and dates;\nengineering lead has confirmed architecture notes\nREFINED: All open questions resolved; effort estimated by engineering;\nGTM requirements confirmed by CS\u002FSales\nAPPROVED: CPO\u002FCEO sign-off; ready for sprint planning\nSHIPPED: Feature live; success metrics being tracked\n\n## COMPLEMENTARY WORKFLOWS\n\nThis skill handles multi-team PRDs. For related PM workflows:\n\n- Single-feature specifications: use official `\u002Fwrite-spec`\n- Decomposing PRD into user stories: use `\u002Fstories` from this plugin\n- Roadmap placement: use official `\u002Froadmap-update`\n- Sprint planning from PRD: use official `\u002Fsprint-planning`\n\n## NEVER DO THESE\n\n- NEVER approve a PRD for sprint planning without engineering lead\n  sign-off on the architecture notes section\n- NEVER mark a PRD REVIEW-ready with empty sections --\n  a gap in the PRD is a gap in the product thinking\n- NEVER define success metrics after launch -- they must be in the PRD\n  before the first sprint starts\n- NEVER omit the failure threshold -- knowing when to change direction\n  is as important as knowing when to celebrate\n- NEVER list a MUST requirement you would actually ship without --\n  if you would ship without it, it is a SHOULD\n- NEVER use \"a user\" as the persona -- always reference named personas\n  from product.local.md\n\nALL OUTPUTS REQUIRE REVIEW BY THE PM AND ENGINEERING LEAD BEFORE APPROVAL.\n","## CONTEXT LOADING\n\nBefore generating a PRD, load `product.local.md` for product context,\npersonas, engineering team details, and stakeholder map. If not configured,\nask the user for product name, personas, and engineering context.\n\n## PRD WORKFLOW\n\n### When to Write a PRD (vs. a Feature Spec)\n\nWrite a SPEC when: One feature, one team, one-to-three sprints\nWrite a PRD when: Multiple features, multiple teams, major platform\nchange, new product area, or executive alignment required\n\nIf unsure, ask the user: \"Is this one feature for one team (use \u002Fwrite-spec)\nor a multi-team initiative (use \u002Fprd)?\"\n\n### PRD Sections -- Full Template\n\nSECTION 1: EXECUTIVE SUMMARY\n[3-4 sentences only]\nWhat: [What are we building -- in plain language]\nWhy: [What commercial or user problem does it solve]\nWhen: [Target delivery -- quarter, not date unless confirmed]\nWin: [How we will know it worked -- headline metric]\n\nSECTION 2: BUSINESS CONTEXT\nProblem statement:\n[The specific user pain or business gap -- with evidence]\n\nCommercial evidence (use what is available):\n\n- Lost deals: \"[N] deals cited [issue] as blocker in [period]\"\n- Customer requests: \"[N] requests logged; [source]\"\n- Competitive gap: \"[Competitor] offers [feature]; we do not\"\n- Revenue opportunity: \"[Estimate] ARR blocked or at risk\"\n- Support cost: \"[N] tickets \u002F [hours] PM support time per [period]\"\n\nStrategic fit:\n[How this initiative connects to the company\u002Fproduct strategy.\nOne sentence. If you cannot write this sentence, the initiative\nmay not belong in the roadmap.]\n\nSuccess metrics:\nPrimary (measure at 6-12 months post-launch):\n[Specific, measurable outcome: not \"improve NPS\" but \"enterprise NPS\nfrom 42 to 52 within 6 months of launch\"]\n\n    Secondary (measure at 30-90 days):\n      [Leading indicators: adoption rate; support volume change;\n       sales cycle impact]\n\n    Failure threshold:\n      [What outcome would cause us to reconsider or change direction?\n       Define before launch, not after.]\n\nSECTION 3: USER REQUIREMENTS\nPrimary persona:\nName: [Persona name from product.local.md]\nRole: [Job title \u002F function]\nCurrent state: [How they handle this today -- the workaround]\nDesired state: [What \"10\u002F10\" looks like for them]\nKey user stories: [Top 3 as \"As a... I want... So that...\"]\n\nSecondary persona (if applicable):\n[Same structure -- brief]\n\nUser journey map:\nCurrent state: [Step-by-step of how they do it today]\nPain points: [Where the friction is in the current flow]\nFuture state: [Step-by-step with the new product in place]\n\nSECTION 4: FUNCTIONAL REQUIREMENTS\nFor each feature\u002Fcapability in scope:\n\nFeature [N]: [Name]\nPriority: MUST \u002F SHOULD \u002F COULD (MoSCoW)\nDescription: [What it does]\nKey flows: [Primary user flows]\nDependencies: [Other features or teams this depends on]\nSpec ref: [Link to individual spec if exists]\n\nRule: Every item labelled MUST must ship before launch.\nIf more than 60% of items are labelled MUST, the scope is too large.\n\nSECTION 5: NON-FUNCTIONAL REQUIREMENTS\nPerformance:\n[Page load time; API response time; export generation time -- with numbers]\n\nReliability:\n[Uptime SLA; error rate tolerance; recovery time objective]\n\nSecurity:\n[Authentication requirements; data encryption; audit requirements;\npenetration testing if required]\n\nCompliance:\n[GDPR \u002F CCPA data handling; SOC 2 implications; HIPAA if applicable;\nsector-specific regulations]\n\nAccessibility:\n[WCAG standard; keyboard navigation; screen reader requirements]\n\nScalability:\n[Expected load at launch; growth assumptions; capacity planning notes]\n\nSECTION 6: TECHNICAL ARCHITECTURE NOTES\n[High-level approach -- not implementation detail]\n\n- Key technical decisions already made\n- Platform or infrastructure dependencies\n- Third-party integrations required\n- Data model changes (high level)\n- Migration requirements (existing users \u002F data)\n- Feature flags required\n\nNote: This section is written by PM in collaboration with engineering.\nIt must be reviewed and confirmed by the engineering lead before\nthe PRD is marked as REVIEW-ready.\n\nSECTION 7: GO-TO-MARKET REQUIREMENTS\nDocumentation:\n[Customer-facing docs required; doc owner; due date]\n\nCustomer Success enablement:\n[What CS needs to know before launch; training requirements]\n\nSales enablement:\n[What sales needs to demo\u002Fdiscuss this feature; talking points]\n\nPricing:\n[Is this in the current plan? New tier? Add-on? Pricing team review needed?]\n\nBeta programme:\n[Which customers; how many; invite criteria; beta start date; GA date]\n\nCustomer communication:\n[Announcement channel; timing; who sends it]\n\nSECTION 8: LAUNCH PLAN\nPhased rollout:\nPhase 1 -- Beta: [Audience; dates; success gates for Phase 2]\nPhase 2 -- GA: [Full availability; announcement plan]\nRollback plan: [How to undo if critical bug discovered post-launch]\n\nFeature flags:\n[Required flags; rollout percentages; sunset plan]\n\nMonitoring:\n[What metrics are watched in the first 48 hours post-launch;\nwho is on-call; escalation path]\n\nSECTION 9: DEPENDENCIES AND RISKS\nExternal dependencies:\n| Dependency | Owner | Status | Risk if delayed |\n|---|---|---|---|\n| [Third party \u002F platform team] | [Name] | [On track \u002F TBD] | [Impact] |\n\nTop risks:\n| Risk | Likelihood | Impact | Mitigation |\n|---|---|---|---|\n| [Risk description] | H\u002FM\u002FL | H\u002FM\u002FL | [Specific mitigation action] |\n\nSECTION 10: OPEN QUESTIONS\n[Numbered; owner; due date]\nAll questions must be resolved before PRD moves to REFINED status.\n\nAPPENDICES (include as available)\nA. Competitive analysis\nB. User research excerpts\nC. Technical discovery notes\nD. Prior art \u002F related specs\n\n### PRD Status Gates\n\nDRAFT: All sections present; some may be incomplete\nREVIEW: All sections complete; open questions have owners and dates;\nengineering lead has confirmed architecture notes\nREFINED: All open questions resolved; effort estimated by engineering;\nGTM requirements confirmed by CS\u002FSales\nAPPROVED: CPO\u002FCEO sign-off; ready for sprint planning\nSHIPPED: Feature live; success metrics being tracked\n\n## COMPLEMENTARY WORKFLOWS\n\nThis skill handles multi-team PRDs. For related PM workflows:\n\n- Single-feature specifications: use official `\u002Fwrite-spec`\n- Decomposing PRD into user stories: use `\u002Fstories` from this plugin\n- Roadmap placement: use official `\u002Froadmap-update`\n- Sprint planning from PRD: use official `\u002Fsprint-planning`\n\n## NEVER DO THESE\n\n- NEVER approve a PRD for sprint planning without engineering lead\n  sign-off on the architecture notes section\n- NEVER mark a PRD REVIEW-ready with empty sections --\n  a gap in the PRD is a gap in the product thinking\n- NEVER define success metrics after launch -- they must be in the PRD\n  before the first sprint starts\n- NEVER omit the failure threshold -- knowing when to change direction\n  is as important as knowing when to celebrate\n- NEVER list a MUST requirement you would actually ship without --\n  if you would ship without it, it is a SHOULD\n- NEVER use \"a user\" as the persona -- always reference named personas\n  from product.local.md\n\nALL OUTPUTS REQUIRE REVIEW BY THE PM AND ENGINEERING LEAD BEFORE APPROVAL.\n",{"name":5,"license":14,"metadata":47,"description":51,"argument-hint":52},{"author":48,"version":49,"plugin-commands":50},"Panaversity","1.0","\u002Fprd","Activate for: PRD, product requirements document, product requirements, full requirements, initiative doc, initiative requirements, platform change, new product, product launch, major release, quarterly initiative, program brief, product vision doc, comprehensive requirements, cross-functional alignment doc, launch plan requirements, multi-team initiative. NOT for: single-feature specifications (use official \u002Fwrite-spec), roadmap planning (use official \u002Froadmap-update), sprint planning (use official \u002Fsprint-planning).\n","\u003Cinitiative name>","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-product-strategy-skills-prd-skill-17c977f3","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill prd",{"tool":65,"command":66},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill prd",{"tool":68,"command":69},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-product-strategy-skills-prd-skill-17c977f3\u002FSKILL.md",true,[],[74,101,127,160,188,220],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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",[],[76,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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",[],[108,109,110,111,112,113,114,40,115,116,117,118,119,120,121,122,123,124,125,126],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","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":78,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":141,"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,138],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":139,"categoryName":140,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,146,147,148,149,150,151,152,153,154,94,155,156,157,158,99,159],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000011","运维与部署",[170,171,172,173,174,175,176,177,178,94,179,180,181,182,183,184,185,186,187,99],"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":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"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",[194,197,200],{"categoryNo":195,"categoryName":196,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":198,"categoryName":199,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":201,"categoryName":202,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源",[204,205,206,207,208,209,210,211,109,212,94,213,214,215,29,216,217,218,99,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":78,"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,94,216,232,233,234,235,236,237,238,239,240,99,241],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]