[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cat:01JBSEEDCAT000000000000031":3,"cat-list:01JBSEEDCAT000000000000031:stars:1":14},{"categoryNo":4,"taxonomyType":5,"taxonomyTypeDesc":6,"categoryName":7,"categoryNameEn":8,"description":9,"level":10,"skillCount":11,"parentNo":12,"parentName":12,"children":13},"01JBSEEDCAT000000000000031","PROFESSION","适用职业","产品经理","Product Manager","负责需求、规划与产品设计",1,2810,null,[],{"records":15,"total":11,"current":10,"size":495},[16,52,77,102,127,144,160,192,223,246,267,292,319,344,400,422,451,475],{"skillNo":17,"name":18,"nameZh":12,"description":19,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":28,"categories":29,"keywords":31,"publishedAt":51},"01M6AE0B8T4SQSSX84DPX8AR4A","prd","Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fprd\u002FSKILL.md",[30],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[18,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"product","generate","risk analysis","documents","analysis","features","software","user stories","Product Requirements","risk","for","technical","requirements","stories","summaries","high","specifications","quality","systems","2026-11-10 10:12:30",{"skillNo":53,"name":54,"nameZh":12,"description":55,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":56,"categories":57,"keywords":59,"publishedAt":51},"01M6ADPQP88ZGDTHN0FA505RXG","gtm-technical-product-pricing","Pricing strategy for technical products. Use when choosing usage-based vs seat-based, designing freemium thresholds, structuring enterprise pricing conversations, deciding when to raise prices, or using price as a positioning signal.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgtm-technical-product-pricing\u002FSKILL.md",[58],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[32,60,61,62,43,21,63,64,65,66,67,68,69,70,71,42,72,73,74,75,76],"pricing","gtm technical product pricing","gtm","https","conversations","prices","positioning","when","pricing strategy","as","usage","thresholds","Enterprise","signal","linkedin","strategy","use",{"skillNo":78,"name":79,"nameZh":12,"description":80,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":81,"categories":82,"keywords":84,"publishedAt":51},"01M6ADPMSM4PV567D5KG082Z0Q","gtm-product-led-growth","Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgtm-product-led-growth\u002FSKILL.md",[83],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[85,32,62,86,87,88,21,63,89,90,67,91,92,93,94,95,96,97,98,99,100,74,101],"gtm product led growth","growth","product led growth","test","complexity","plg","conversion","freemium conversion","self","acquisition","revenue","human","expansion","activation","10x","parallel","touch",{"skillNo":103,"name":104,"nameZh":12,"description":105,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":106,"categories":107,"keywords":114,"publishedAt":51},"01M6ADPHRT0ZTM3JAZS95YQYJ5","gtm-positioning-strategy","Find and own a defensible market position. Use when messaging sounds like competitors, conversion is weak despite awareness, repositioning a product, or testing positioning claims. Includes Crawl-Walk-Run rollout methodology and the word change that improved enterprise deal progression.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgtm-positioning-strategy\u002FSKILL.md",[108,113],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[115,66,62,116,75,117,118,21,32,119,63,120,121,67,122,91,123,124,125,72,74,126],"gtm positioning strategy","positioning strategy","change","messaging","run","testing","crawl","rollout","claims","competitors","Word","awareness",{"skillNo":128,"name":129,"nameZh":12,"description":130,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":131,"categories":132,"keywords":137,"publishedAt":51},"01M6AD9V7G4NCQQZDATT0ZM2R5","breakdown-feature-prd","Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbreakdown-feature-prd\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[138,139,140,18,32,35,42,141,142,143,44,37,40],"breakdown feature prd","feature","breakdown","new","prompt","EPIC",{"skillNo":145,"name":146,"nameZh":12,"description":147,"descriptionZh":12,"repositoryFullName":20,"ownerLogin":21,"ownerAvatarUrl":22,"ownerAccountNo":23,"ownerDisplayName":24,"repositoryNo":25,"starsCount":26,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":148,"categories":149,"keywords":152,"publishedAt":51},"01M6AD9PCWRWTPTHKDG3SCM7AW","breakdown-epic-pm","Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbreakdown-epic-pm\u002FSKILL.md",[150,151],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[153,154,143,140,32,155,69,42,141,43,156,142,44,157,158,159,18,40],"breakdown epic pm","pm","architecture","document","specification","input","new epic",{"skillNo":161,"name":162,"nameZh":12,"description":163,"descriptionZh":12,"repositoryFullName":164,"ownerLogin":165,"ownerAvatarUrl":166,"ownerAccountNo":167,"ownerDisplayName":168,"repositoryNo":169,"starsCount":170,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":172,"categories":173,"keywords":176,"publishedAt":51},"01M6AFY6CKMW3NAB7TY566J7N4","performing-nist-csf-maturity-assessment","Conduct a NIST Cybersecurity Framework (CSF) 2.0 maturity assessment across the six core Functions (Govern, Identify, Protect, Detect, Respond, Recover), scoring organizational posture against the four Implementation Tiers (Partial, Risk-Informed, Repeatable, Adaptive) and producing an improvement roadmap. Use when benchmarking an organization's cybersecurity program maturity or preparing a CSF-based gap analysis and remediation plan.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35884,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-nist-csf-maturity-assessment\u002FSKILL.md",[174,175],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[177,178,179,180,41,181,182,183,36,184,185,186,187,188,189,190,191],"nist csf","assessment","NIST","performing nist csf maturity assessment","core","risk-management","cybersecurity","t1078","benchmarking","compliance","governance","remediation","csf","maturity-assessment","framework",{"skillNo":193,"name":194,"nameZh":12,"description":195,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":51},"01M718NFCARWCKFNDVDWBYNX6Y","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35379,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fproduct-management\u002Fskills\u002Fwrite-spec\u002FSKILL.md",[205],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[207,208,209,210,211,212,67,213,214,215,216,217,218,139,219,76,156,220,221,222],"write","write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","problem statement","with","acceptance criteria","goals",{"skillNo":224,"name":225,"nameZh":12,"description":226,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":227,"categories":228,"keywords":230,"publishedAt":51},"01M718N2M6GN10W43KHPGFC2WZ","roadmap-update","Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now\u002FNext\u002FLater view from scratch.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fproduct-management\u002Fskills\u002Froadmap-update\u002FSKILL.md",[229],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[231,232,233,141,234,235,67,236,237,238,32,239,240,241,242,243,244,76,245],"roadmap update","roadmap","update","now","information","create","later","next","dependency","priorities","make","product roadmap","view","scratch","From Scratch",{"skillNo":247,"name":248,"nameZh":12,"description":249,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":250,"categories":251,"keywords":254,"publishedAt":51},"01M718N080M5B5VAK7TS51DZPG","product-brainstorming","Brainstorm product ideas, explore problem spaces, and challenge assumptions as a thinking partner. Use when exploring a new opportunity, generating solutions to a product problem, stress-testing an idea, or when a PM needs to think out loud with a sharp sparring partner before converging on a direction.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fproduct-management\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",[252,253],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[255,32,256,257,211,258,259,260,120,261,262,154,141,263,67,264,265,266,217,69],"product brainstorming","brainstorming","thinking","direction","thinking partner","explore","brainstorm","challenge","opportunity","solutions","sharp","stress",{"skillNo":268,"name":269,"nameZh":12,"description":270,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":271,"categories":272,"keywords":275,"publishedAt":51},"01M718JAD3R4N9AHK1DD9HX23Y","plan-zoom-product","Choose the right Zoom building surface for a use case and explain the tradeoffs clearly. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific product idea or integration goal.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fpartner-built\u002Fzoom-plugin\u002Fskills\u002Fplan-zoom-product\u002FSKILL.md",[273,274],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[276,277,278,32,279,280,42,281,282,283,284,76,285,286,67,287,288,289,290,291],"zoom","plan zoom product","plan","Video","app","choose","video sdk","phone","MCP","false","apps","explain","api","zoom apps sdk","type","case",{"skillNo":293,"name":294,"nameZh":12,"description":295,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":296,"categories":297,"keywords":306,"publishedAt":51},"01M718GYN1Q2BXF4BFRKGHXY8S","zoom-general","Cross-product Zoom reference skill. Use after the workflow is clear when you need shared platform guidance, app-model comparisons, authentication context, scopes, marketplace considerations, or API-vs-MCP routing.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fpartner-built\u002Fzoom-plugin\u002Fskills\u002Fgeneral\u002FSKILL.md",[298,301,302,305],{"categoryNo":299,"categoryName":300,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":303,"categoryName":304,"taxonomyType":5,"taxonomyTypeDesc":6},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[307,276,308,309,310,280,311,312,281,313,284,285,67,314,315,288,32,316,317,318],"general","zoom general","shared","getting started","which","model","authentication","workflow","you","context","platform","reference skill",{"skillNo":320,"name":321,"nameZh":12,"description":322,"descriptionZh":12,"repositoryFullName":196,"ownerLogin":197,"ownerAvatarUrl":198,"ownerAccountNo":199,"ownerDisplayName":200,"repositoryNo":201,"starsCount":202,"licenseSpdxId":171,"licenseFileUrl":12,"sourceHtmlUrl":323,"categories":324,"keywords":332,"publishedAt":51},"01M718E46656MQ79XDJ4N6WWWP","campaign-plan","Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fmarketing\u002Fskills\u002Fcampaign-plan\u002FSKILL.md",[325,328,329],{"categoryNo":326,"categoryName":327,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},{"categoryNo":330,"categoryName":331,"taxonomyType":5,"taxonomyTypeDesc":6},"01JBSEEDCAT000000000000035","市场营销",[333,278,334,335,118,67,315,32,33,336,337,338,339,340,341,218,342,343,126,75],"campaign","campaign plan","brief","goal","calendar","content calendar","marketing","lead","full","push","planning",{"skillNo":345,"name":346,"nameZh":12,"description":347,"descriptionZh":12,"repositoryFullName":348,"ownerLogin":349,"ownerAvatarUrl":350,"ownerAccountNo":351,"ownerDisplayName":352,"repositoryNo":353,"starsCount":354,"licenseSpdxId":27,"licenseFileUrl":355,"sourceHtmlUrl":356,"categories":357,"keywords":367,"publishedAt":51},"01M6ADRQC2SM9G2VRBRHT4JBMT","loki-mode","Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data\u002FML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A\u002FB testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33286,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Floki-mode\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Floki-mode\u002FSKILL.md",[358,361,362,363,364],{"categoryNo":359,"categoryName":360,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},{"categoryNo":365,"categoryName":366,"taxonomyType":5,"taxonomyTypeDesc":6},"01JBSEEDCAT000000000000038","人力资源",[368,369,370,371,372,373,374,120,375,376,377,378,379,380,381,382,32,383,384,385,386,387,388,389,390,391,392,95,96,393,394,395,396,397,398,399],"loki mode","mode","loki","ZeRO","deployment","code review","issue triage","qa","ml","incident response","distributed","code","review","state","permissions","customer","data","startup","cloud","triage","customer feedback","auto","subagent","specialized","limits","rate","issue","automatic","security","multi-agent","circuit","letter",{"skillNo":401,"name":402,"nameZh":12,"description":403,"descriptionZh":12,"repositoryFullName":348,"ownerLogin":349,"ownerAvatarUrl":350,"ownerAccountNo":351,"ownerDisplayName":352,"repositoryNo":353,"starsCount":354,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":404,"categories":405,"keywords":407,"publishedAt":51},"01M6AF85P9HVGKKKFAA3MQG9F5","requirements-clarity","Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Frequirements-clarity\u002FSKILL.md",[406],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[408,44,409,181,410,411,412,76,67,213,413,414,415,416,417,418,419,37,420,421],"requirements clarity","clarity","clarify","dialogue","team coordination","coordination","team","check","yagni","why","kiss","questions","ambiguous","implementation",{"skillNo":423,"name":424,"nameZh":12,"description":425,"descriptionZh":12,"repositoryFullName":348,"ownerLogin":349,"ownerAvatarUrl":350,"ownerAccountNo":351,"ownerDisplayName":352,"repositoryNo":353,"starsCount":354,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":426,"categories":427,"keywords":431,"publishedAt":51},"01M6AF64609DMP6PCM7SRM3ART","devil","Reviews a product document (PRD, spec, design brief) BEFORE implementation to surface holes — undefined edge cases, missing states, policy gaps — by attacking what the document is SILENT about (things unwritten, and things written only for the happy path). Acts as a strict \"sign-off manager,\" ruling Approve \u002F Conditional \u002F Reject and producing a polite, forwardable question list. Works for planners\u002FPMs (self-review before sharing), engineers (blocking questions before coding), and designers (screen states with no mockup). Use whenever the user wants a spec\u002FPRD\u002Fplan\u002Fbrief checked for readiness or gaps, or says \"review this spec\", \"find holes in this PRD\", \"poke holes in this\", \"is this plan good to build?\", \"can I start implementing this?\", \"what states\u002Fedge cases am I missing?\", \"what should I ask the PM before coding?\", \"run devil\", or pastes\u002Flinks a planning document and asks whether it's ready to act on. Do NOT use it to: write or draft a new spec, summarize or translate a document, estimate\u002Fbreak down tickets, generate test cases, review or debug code, or compare already-built code against a doc — this skill runs on the DOCUMENT stage, before code exists.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdevil\u002FSKILL.md",[428,429,430],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":303,"categoryName":304,"taxonomyType":5,"taxonomyTypeDesc":6},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[424,335,88,21,32,343,33,119,432,433,63,434,209,435,436,437,438,439,18,379,440,441,442,154,443,278,444,445,207,446,447,448,449,450],"sharing","translate","policy","start","edge","design","doc","debug","ready","reviews","implementing","question","screen","break","act","list","manager","coding","test cases",{"skillNo":452,"name":453,"nameZh":12,"description":454,"descriptionZh":12,"repositoryFullName":348,"ownerLogin":349,"ownerAvatarUrl":350,"ownerAccountNo":351,"ownerDisplayName":352,"repositoryNo":353,"starsCount":354,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":455,"categories":456,"keywords":459,"publishedAt":51},"01M6AESYT6QB2CFSS8SK1D6RTM","screenshot-feature-extractor","Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD\u002Ftask lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fscreenshot-feature-extractor\u002FSKILL.md",[457,458],{"categoryNo":134,"categoryName":135,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[460,461,139,32,33,462,463,464,18,465,466,467,468,280,42,469,470,76,67,471,36,472,473,474],"screenshot feature extractor","screenshot","development","analyzing","ui","extraction","batch","screenshots","competitive","competitor","extract feature","visual","task","analyze","references",{"skillNo":476,"name":477,"nameZh":12,"description":478,"descriptionZh":12,"repositoryFullName":348,"ownerLogin":349,"ownerAvatarUrl":350,"ownerAccountNo":351,"ownerDisplayName":352,"repositoryNo":353,"starsCount":354,"licenseSpdxId":27,"licenseFileUrl":12,"sourceHtmlUrl":479,"categories":480,"keywords":482,"publishedAt":51},"01M6AE321J799DJEM9TQSHFJF6","product-strategist","Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-strategist\u002FSKILL.md",[481],{"categoryNo":4,"categoryName":7,"taxonomyType":5,"taxonomyTypeDesc":6},[483,32,484,437,343,485,468,486,487,488,42,489,76,490,36,491,414,492,493,494],"product strategist","strategist","toolkit","alignment","market analysis","scaling","strategic","strategic planning","Market","leadership","head","generation",18]