[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-Swiftner-Factory-Floor-zh-CN":3,"guides-for-Swiftner-Factory-Floor":368,"similar-k17bg2t9tbchs76s2ampxqnpax86nz64-zh-CN":369},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":17,"identity":263,"isFallback":248,"parentExtension":268,"providers":269,"relations":276,"repo":279,"tags":364,"workflow":365},1778697975059.0923,"k17bg2t9tbchs76s2ampxqnpax86nz64",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":15,"sourceUrl":16},"为创始人及早期团队提供创业指导。当用户提到以下关键词时触发：“我们应该关注什么”，“我们应该开发X吗”，“我们应该融资吗”，“我们卡住了”，“为什么这个项目没有增长”，“潜在客户太少”，“我们转化率不高”，“我们精力分散”，“团队很忙但没有产出”，“我不知道下一步该做什么”，或者询问关于客户流失、招聘、运行周期、消耗率、交易流程、融资、在制品（WIP）、用户目标（JTBD）、客户工厂、瓶颈、吞吐量——并且是在创业的背景下。不适用于：自由职业者、代理机构、成熟公司、编程帮助、调试。\n",{"claudeCode":12,"clawhub":13,"npm":14},"Swiftner/Factory-Floor","factory-floor","@swiftner/factory-floor","Factory Floor","https://github.com/Swiftner/Factory-Floor",{"_creationTime":18,"_id":19,"extensionId":5,"locale":20,"result":21,"trustSignals":246,"workflow":261},1778697975059.0925,"kn770vcggczkb702hvnhmervv586mt98","zh-CN",{"checks":22,"evaluatedAt":198,"extensionSummary":199,"features":200,"nonGoals":206,"practices":210,"prerequisites":215,"promptVersionExtension":218,"promptVersionScoring":219,"purpose":220,"rationale":221,"score":222,"summary":223,"tags":224,"tier":233,"useCases":234,"workflow":239},[23,28,31,34,38,41,46,50,53,56,60,64,68,72,75,78,81,84,87,90,93,97,101,105,109,112,116,119,123,126,129,132,135,138,141,145,149,153,156,160,163,166,169,172,176,179,182,185,188,191,195],{"category":24,"check":25,"severity":26,"summary":27},"Practical Utility","Problem relevance","pass","描述清楚地指出了具体的用户问题（创业优先级排序和执行）以及它出现的情境，为该技能的实用性奠定了基础。",{"category":24,"check":29,"severity":26,"summary":30},"Unique selling proposition","该技能通过整合多个框架和强制执行有纪律的工作流程，提供了一种超越标准 LLM 能力的结构化创业战略和执行方法。",{"category":24,"check":32,"severity":26,"summary":33},"Production readiness","该技能的基于 Markdown 的架构、清晰的协议以及与状态管理的集成表明它已准备好在指导创始人进行战略决策的生产环境中使用。",{"category":35,"check":36,"severity":26,"summary":37},"Scope","Single responsibility principle","该技能专注于一个单一、连贯的领域：充当创业指导者，负责优先级排序和执行，并以结构化的决策树和框架集成作为指导。",{"category":35,"check":39,"severity":26,"summary":40},"Description quality","描述简洁、易读，并准确反映了该技能作为创业指导者的目的和范围。",{"category":42,"check":43,"severity":44,"summary":45},"Invocation","Scoped tools","not_applicable","该技能通过基于 Markdown 的决策树运行，并且不以传统意义上暴露特定工具。",{"category":47,"check":48,"severity":44,"summary":49},"Documentation","Configuration & parameter reference","该技能不公开除核心工作流程之外的配置参数或选项，因此无需显式文档。",{"category":35,"check":51,"severity":44,"summary":52},"Tool naming","该技能不公开具有名称的单个工具；其操作由 Markdown 内容指导。",{"category":35,"check":54,"severity":44,"summary":55},"Minimal I/O surface","该技能的 I/O 是对话式和基于状态的，而不是通过具有参数的正式工具模式。",{"category":57,"check":58,"severity":26,"summary":59},"License","License usability","虽然在提供的上下文中未检测到特定的 LICENSE 文件或 SPDX 标识符，但 `package.json` 指示为 MIT 许可证，这是一个宽松且可用的许可证。",{"category":61,"check":62,"severity":26,"summary":63},"Maintenance","Commit recency","该存储库显示在过去 3 个月内有近期提交，表明正在积极维护。",{"category":61,"check":65,"severity":66,"summary":67},"Dependency Management","info","该项目有一个用于其脚本的 package.json，但缺少锁定文件，这表明可能存在依赖漂移和缺乏严格的版本固定。",{"category":69,"check":70,"severity":26,"summary":71},"Security","Secret Management","该技能基于 Markdown 运行，似乎不直接处理秘密；提交的代码中未暴露任何秘密，并且在其运行流程中也不预期会处理秘密。",{"category":69,"check":73,"severity":26,"summary":74},"Injection","该技能的基于 Markdown 的逻辑和并行读取策略旨在将加载的内容视为数据而非指令，从而降低了注入风险。",{"category":69,"check":76,"severity":26,"summary":77},"Transitive Supply-Chain Grenades","该技能依赖于捆绑的 Markdown 和一个用于图表渲染的 Node.js 脚本；它不在运行时获取远程代码或数据。",{"category":69,"check":79,"severity":26,"summary":80},"Sandbox Isolation","作为一个基于 Markdown 且脚本极少的技能，它在 Claude Code 环境内运行，并且不与指定范围 `.factory/` 之外的文件系统进行交互。",{"category":69,"check":82,"severity":26,"summary":83},"Sandbox escape primitives","在捆绑的脚本或 Markdown 中未找到分离的进程、拒绝调用周围的重试循环或其他沙箱逃逸原语。",{"category":69,"check":85,"severity":26,"summary":86},"Data Exfiltration","该技能的操作是自包含的，不涉及出站调用进行遥测或数据提交，因此不会有数据泄露的风险。",{"category":69,"check":88,"severity":26,"summary":89},"Hidden Text Tricks","Markdown 内容似乎干净，没有隐藏的操纵技巧、控制字符或不可见的 Unicode 字符。",{"category":69,"check":91,"severity":26,"summary":92},"Opaque code execution","唯一使用的脚本是用于图表渲染的，它是纯 JavaScript，没有混淆或动态获取。",{"category":94,"check":95,"severity":26,"summary":96},"Portability","Structural Assumption","该技能的状态层正确处理了 `.factory/` 和 `.gitignore` 文件缺失的情况，使其能够适应不同的项目设置。",{"category":98,"check":99,"severity":26,"summary":100},"Trust","Issues Attention","信任信号中没有报告的开放性问题，这表明维护者参与度很高或没有报告问题。",{"category":102,"check":103,"severity":26,"summary":104},"Versioning","Release Management","`package.json` 包含版本号，满足了可检测版本化的要求。",{"category":106,"check":107,"severity":44,"summary":108},"Execution","Validation","该技能的核心逻辑基于 Markdown；它不公开可执行代码或需要模式验证库的结构化输出。",{"category":69,"check":110,"severity":26,"summary":111},"Unguarded Destructive Operations","该技能的操作主要对用户项目状态是只读的，任何写入都发生在专用的本地状态目录中，并且不使用破坏性原语。",{"category":113,"check":114,"severity":26,"summary":115},"Code Execution","Error Handling","该技能的 Markdown 和极简脚本逻辑预计能够优雅地处理错误，方法是告知用户或在可能的情况下继续进行，而不会导致代理崩溃。",{"category":113,"check":117,"severity":26,"summary":118},"Logging","状态层包含一个用于记录交互的日志文件，该文件默认被 gitignore，允许在不进行版本控制的情况下进行审查。",{"category":120,"check":121,"severity":26,"summary":122},"Compliance","GDPR","该技能不处理个人数据；其状态管理是项目目录本地的，不涉及第三方提交。",{"category":120,"check":124,"severity":26,"summary":125},"Target market","该技能是一个通用的创业指导工具，没有明显的区域或司法限制；其目标市场是全球性的。",{"category":94,"check":127,"severity":26,"summary":128},"Runtime stability","该技能的 Markdown 核心和用于图表的 Node.js 脚本在 POSIX 类环境中具有广泛的便携性，并且不假定特定的操作系统或编辑器功能。",{"category":47,"check":130,"severity":26,"summary":131},"README","存在 README.md 文件，并清楚地说明了扩展的目的和功能。",{"category":35,"check":133,"severity":44,"summary":134},"Tool surface size","这是一个单一目的的 Markdown 技能，而不是一组工具。",{"category":42,"check":136,"severity":44,"summary":137},"Overlapping near-synonym tools","该技能不公开具有重叠功能的多个工具或命令。",{"category":47,"check":139,"severity":26,"summary":140},"Phantom features","所有宣传的功能，特别是状态层和协议命名，都已实现，并且可以在代码和文档中进行验证。",{"category":142,"check":143,"severity":26,"summary":144},"Install","Installation instruction","README 提供了清晰的 Claude Code、OpenAI Codex 的安装说明以及 Claude Desktop 的手动设置，包括复制粘贴示例。",{"category":146,"check":147,"severity":26,"summary":148},"Errors","Actionable error messages","该技能的设计暗示在状态加载或写入过程中遇到的错误将报告给用户，并提供足够的上下文以理解问题。",{"category":106,"check":150,"severity":151,"summary":152},"Pinned dependencies","warning","脚本的 `package.json` 文件存在，但缺少锁定文件（`package-lock.json` 或 `yarn.lock`），这意味着依赖项未被固定，这可能导致执行不稳定。",{"category":35,"check":154,"severity":44,"summary":155},"Dry-run preview","该技能不执行需要预演模式的状态更改操作；其写入操作针对本地专用状态目录，不涉及破坏性操作。",{"category":157,"check":158,"severity":26,"summary":159},"Protocol","Idempotent retry & timeouts","该技能的操作主要是文件 I/O 和 Markdown 解析，而不是需要幂等性或超时处理的远程调用或状态更改操作。",{"category":120,"check":161,"severity":26,"summary":162},"Telemetry opt-in","该技能不发出任何遥测数据；其状态日志是本地的，并且默认被 gitignore。",{"category":42,"check":164,"severity":26,"summary":165},"Precise Purpose","描述清楚地阐述了该技能作为创业指导者的目的，并明确了其触发条件和非目标，为调用提供了精确的指导。",{"category":42,"check":167,"severity":26,"summary":168},"Concise Frontmatter","SKILL.md 中的 frontmatter 简洁、自包含，并有效地总结了核心功能和触发器，没有关键词堆砌。",{"category":47,"check":170,"severity":26,"summary":171},"Concise Body","SKILL.md 的正文结构良好，决策树和核心规则被简洁地呈现，将更深入的材料委托给单独的参考文件。",{"category":173,"check":174,"severity":26,"summary":175},"Context","Progressive Disclosure","该技能有效地利用了渐进式披露，根据上下文路由到特定的阶段文件，使初始交互保持专注，并将详细的框架信息委托给单独的参考文件。",{"category":173,"check":177,"severity":44,"summary":178},"Forked exploration","该技能不涉及需要“context: fork”设置的深度代码探索或多文件检查。",{"category":24,"check":180,"severity":26,"summary":181},"Usage examples","README 和 `references/state.md` 提供了清晰的状态文件和对话交互示例，有效地展示了该技能的用法。",{"category":24,"check":183,"severity":26,"summary":184},"Edge cases","`references/state.md` 文件详细记录了八个与状态管理相关的边缘情况，包括处理缺失文件、重命名和创始人覆盖，并提供了清晰的恢复路径。",{"category":113,"check":186,"severity":44,"summary":187},"Tool Fallback","该技能不依赖外部工具或 MCP 服务器，因此无需回退机制。",{"category":94,"check":189,"severity":26,"summary":190},"Stack assumptions","该技能依赖 Node.js 来处理一个小型脚本以及通用的 Markdown 处理，这表明其在标准环境中具有广泛的便携性。",{"category":192,"check":193,"severity":26,"summary":194},"Safety","Halt on unexpected state","状态层的设计包括对陈旧数据和已重命名标题的特定处理，确保工作流程能够顺利纠正或提示用户澄清，而不是意外停止。",{"category":94,"check":196,"severity":26,"summary":197},"Cross-skill coupling","Factory Floor 技能是独立的，并且似乎不依赖于或隐式耦合于在同一会话中加载的任何其他特定技能。",1778697943566,"Factory Floor 充当一个创业操作系统，利用 Goldratt 的约束理论、Maurya 的客户工厂和 Sharp 的品牌增长法则等战略框架的结合，指导创始人进行优先级排序和执行。它具有一个状态层，用于在会话之间保持连续性，并通过命名引用实现协议可发现性。",[201,202,203,204,205],"跨越多种战略框架的创业指导","用于会话连续性的持久化状态层","基于阶段的路由和指导协议","约束识别和管理","用于特定操作的可发现命名协议",[207,208,209],"提供直接的编码或调试帮助。","取代创始人战略思考，而是对其进行增强。","充当通用的任务管理器。",[211,212,213,214],"战略纪律","约束管理","客户导向","迭代改进",[216,217],"Claude Code 或兼容的代理环境","Node.js（用于可选的图表渲染脚本）","3.0.0","4.4.0","通过充当一个严谨的思考伙伴，帮助创业创始人及团队做出更好的战略决策并更有效地执行。","该技能有非常完善的文档，集成了强大的状态管理系统，并跨多个创业框架提供了清晰、可操作的指导。主动处理边缘情况和改进可发现性都有助于提供高质量的用户体验。",99,"一个整合了多种框架和持久化状态层的综合性创业指导工具。",[225,226,227,228,229,230,231,232],"startup","strategy","coaching","prioritization","frameworks","lean","goldratt","jtbd","community",[235,236,237,238],"当你需要帮助确定工作重点时使用。","当你被困在某个特定的漏斗瓶颈时使用。","当你需要对创业公司的进展进行每周回顾时使用。","当你想要根据既定的业务框架做出战略决策时使用。",[240,241,242,243,244,245],"基于创始人对优先级排序/指导的需求触发技能。","如果可用，加载现有状态，否则运行初始设置协议。","根据上下文（阶段、约束）路由到适当的阶段文件。","指导创始人完成诊断、战略和执行步骤。","在仪式完成后写入状态更新（日志条目、上下文更改）。","提供用于特定操作的可发现命名协议。",{"codeQuality":247,"collectedAt":249,"documentation":250,"maintenance":253,"popularity":256,"security":258,"testCoverage":260},{"hasLockfile":248},false,1778697933836,{"descriptionLength":251,"readmeSize":252},551,8703,{"closedIssues90d":8,"forks":8,"hasChangelog":248,"openIssues90d":8,"pushedAt":254,"stars":255},1775667002000,8,{"npmDownloads":257},67,{"hasNpmPackage":259,"smitheryVerified":248},true,{"hasCi":248,"hasTests":248},{"updatedAt":262},1778697975059,{"basePath":264,"githubOwner":265,"githubRepo":266,"locale":20,"slug":266,"type":267},"","Swiftner","Factory-Floor","skill",null,{"evaluate":270,"extract":273},{"promptVersionExtension":218,"promptVersionScoring":219,"score":222,"tags":271,"targetMarket":272,"tier":233},[225,226,227,228,229,230,231,232],"global",{"commitSha":274,"license":275},"HEAD","MIT",{"repoId":277,"translatedFrom":278},"kd7ec0p3r45yy0rdjk4ckhqb7s86mbc1","k178dq3rcjtezryta3djb0hsmh86nve2",{"_creationTime":280,"_id":277,"identity":281,"providers":282,"workflow":359},1778697898982.3347,{"githubOwner":265,"githubRepo":266,"sourceUrl":16},{"classify":283,"discover":351,"extract":354,"github":355,"npm":358},{"commitSha":274,"extensions":284},[285,340],{"basePath":264,"description":286,"displayName":13,"installMethods":287,"rationale":288,"selectedPaths":289,"source":338,"sourceLanguage":339,"type":267},"Startup coach for founders and early-stage teams. Trigger when someone mentions: \"what should we focus on\", \"should we build X\", \"should we raise\", \"we're stuck\", \"why isn't this growing\", \"pipeline is thin\", \"we're not converting\", \"we're spread too thin\", \"team is busy but nothing ships\", \"I don't know what to do next\", or asks about churn, hiring, runway, burn rate, deal flow, fundraising, WIP, JTBD, customer factory, constraint, throughput — in a startup context. NOT for: freelancers, agencies, established companies, coding help, debugging.\n",{"claudeCode":12},"SKILL.md frontmatter at SKILL.md",[290,293,296,299,302,304,306,308,310,312,314,316,318,320,322,324,326,328,330,332,334,336],{"path":291,"priority":292},"SKILL.md","mandatory",{"path":294,"priority":295},"README.md","high",{"path":297,"priority":298},"CLAUDE.md","medium",{"path":300,"priority":301},"assets/icon.svg","low",{"path":303,"priority":301},"docs/superpowers/plans/2026-04-07-factory-floor-state-layer.md",{"path":305,"priority":301},"docs/superpowers/specs/2026-04-07-factory-floor-state-layer-design.md",{"path":307,"priority":298},"references/coaching-patterns.md",{"path":309,"priority":298},"references/estimation.md",{"path":311,"priority":298},"references/intake.md",{"path":313,"priority":298},"references/jtbd.md",{"path":315,"priority":298},"references/misdiagnoses.md",{"path":317,"priority":298},"references/pillar-goldratt.md",{"path":319,"priority":298},"references/pillar-maurya.md",{"path":321,"priority":298},"references/pillar-ritson.md",{"path":323,"priority":298},"references/pillar-sharp.md",{"path":325,"priority":298},"references/pillar-strategy.md",{"path":327,"priority":298},"references/state.md",{"path":329,"priority":298},"references/weekly-diagrams.md",{"path":331,"priority":298},"references/weekly-review.md",{"path":333,"priority":301},"scripts/package-skill.mjs",{"path":335,"priority":301},"scripts/package.json",{"path":337,"priority":301},"scripts/render-diagram.mjs","rule","en",{"basePath":264,"description":341,"displayName":14,"installMethods":342,"license":275,"rationale":343,"selectedPaths":344,"source":338,"sourceLanguage":339,"type":350},"A Claude Code skill for startup prioritisation using Theory of Constraints, Customer Factory, How Brands Grow, Marketing Strategy Discipline, and Strategic Thinking",{"npm":14},"cli ecosystem detected at /",[345,347,348],{"path":346,"priority":292},"package.json",{"path":294,"priority":292},{"path":349,"priority":298},"bin/install.mjs","cli",{"sources":352},[353],"manual",{"npmPackage":14},{"closedIssues90d":8,"description":356,"forks":8,"openIssues90d":8,"pushedAt":254,"readmeSize":252,"stars":255,"topics":357},"A Claude Code skill that coaches founders through prioritization, bottlenecks, and what to build next.",[],{"downloads":257},{"classifiedAt":360,"discoverAt":361,"extractAt":362,"githubAt":362,"npmAt":363,"updatedAt":360},1778697905258,1778697898982,1778697901159,1778697903726,[227,229,231,232,230,228,225,226],{"evaluatedAt":366,"extractAt":367,"updatedAt":262},1778697943694,1778697905439,[],[370,398,425,452,483,511],{"_creationTime":371,"_id":372,"community":373,"display":374,"identity":380,"providers":384,"relations":391,"tags":394,"workflow":395},1778675056600.2134,"k176he2eqq4px8bpjsh3azaqkd86ndex",{"reviewCount":8},{"description":375,"installMethods":376,"name":378,"sourceUrl":379},"/cs:cpo-review \u003Cplan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus.",{"claudeCode":377},"alirezarezvani/claude-skills","cpo-review","https://github.com/alirezarezvani/claude-skills",{"basePath":381,"githubOwner":382,"githubRepo":383,"locale":339,"slug":378,"type":267},"c-level-advisor/c-level-agents/skills/cpo-review","alirezarezvani","claude-skills",{"evaluate":385,"extract":390},{"promptVersionExtension":218,"promptVersionScoring":219,"score":222,"tags":386,"targetMarket":272,"tier":389},[387,388,226,232,228],"product-management","roadmap","verified",{"commitSha":274},{"parentExtensionId":392,"repoId":393},"k172bm0n7hp1thk5xp6n6rwyj986mym4","kd7ff9s1w43mfyy1n7hf87816186m6px",[232,228,387,388,226],{"evaluatedAt":396,"extractAt":397,"updatedAt":396},1778676501430,1778675056600,{"_creationTime":399,"_id":400,"community":401,"display":402,"identity":408,"providers":412,"relations":418,"tags":421,"workflow":422},1778686037155.627,"k170cqya1d6rhcbs6k25bycb5186nmme",{"reviewCount":8},{"description":403,"installMethods":404,"name":406,"sourceUrl":407},"Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.",{"claudeCode":405},"deanpeters/Product-Manager-Skills","prioritization-advisor","https://github.com/deanpeters/Product-Manager-Skills",{"basePath":409,"githubOwner":410,"githubRepo":411,"locale":339,"slug":406,"type":267},"skills/prioritization-advisor","deanpeters","Product-Manager-Skills",{"evaluate":413,"extract":417},{"promptVersionExtension":218,"promptVersionScoring":219,"score":414,"tags":415,"targetMarket":272,"tier":389},98,[387,228,229,416,226],"decision-making",{"commitSha":274},{"parentExtensionId":419,"repoId":420},"k17f16tjazbj49a2ber3mr5f6s86nfkm","kd79w54je3w4zrhk2stxg9246186nbp1",[416,229,228,387,226],{"evaluatedAt":423,"extractAt":424,"updatedAt":423},1778687938277,1778686037155,{"_creationTime":426,"_id":427,"community":428,"display":429,"identity":435,"providers":440,"relations":446,"tags":448,"workflow":449},1778694240519.739,"k17bekm6y9dr7tmn30374vwksx86npt8",{"reviewCount":8},{"description":430,"installMethods":431,"name":433,"sourceUrl":434},"Feature and initiative prioritization using 7 frameworks (RICE, ICE, WSJF, MoSCoW, Value/Effort, Kano, Weighted Scoring). Auto-detects mode: stack rank, scoring, opportunity assessment, trade-off analysis, or scope cut. Triggers on: \"prioritize\", \"rank these features\", \"RICE score\", \"what should we build next\", \"scope cut\", \"trade-off\".\n",{"claudeCode":432},"mshadmanrahman/pm-pilot","PM Pilot Prioritize","https://github.com/mshadmanrahman/pm-pilot",{"basePath":436,"githubOwner":437,"githubRepo":438,"locale":339,"slug":439,"type":267},"skills/pm-core/prioritize","mshadmanrahman","pm-pilot","prioritize",{"evaluate":441,"extract":445},{"promptVersionExtension":218,"promptVersionScoring":219,"score":442,"tags":443,"targetMarket":272,"tier":233},91,[228,387,229,444,226],"scoring",{"commitSha":274,"license":275},{"repoId":447},"kd728wqst6vwd95ymycxb97nrx86mnsn",[229,228,387,444,226],{"evaluatedAt":450,"extractAt":451,"updatedAt":450},1778694528283,1778694240519,{"_creationTime":453,"_id":454,"community":455,"display":456,"identity":462,"providers":466,"relations":476,"tags":479,"workflow":480},1778695548458.4048,"k17e5nn93syzxrybh3he9fz5eh86nbme",{"reviewCount":8},{"description":457,"installMethods":458,"name":460,"sourceUrl":461},"Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.\n",{"claudeCode":459},"pjt222/agent-almanac","teach-guidance","https://github.com/pjt222/agent-almanac",{"basePath":463,"githubOwner":464,"githubRepo":465,"locale":339,"slug":460,"type":267},"skills/teach-guidance","pjt222","agent-almanac",{"evaluate":467,"extract":475},{"promptVersionExtension":218,"promptVersionScoring":219,"score":468,"tags":469,"targetMarket":272,"tier":389},100,[470,227,471,472,473,474],"teaching","presentation","documentation","explanation","guidance",{"commitSha":274},{"parentExtensionId":477,"repoId":478},"k170h0janaa9kwn7cfgfz2ykss86mmh9","kd7aryv63z61j39n2td1aeqkvh86mh12",[227,472,473,474,471,470],{"evaluatedAt":481,"extractAt":482,"updatedAt":481},1778701952682,1778695548458,{"_creationTime":484,"_id":485,"community":486,"display":487,"identity":493,"providers":497,"relations":505,"tags":507,"workflow":508},1778688112811.7483,"k178nypfqdsjragsjfa30tedw986mfsq",{"reviewCount":8},{"description":488,"installMethods":489,"name":491,"sourceUrl":492},"Design and run effective 1:1 meetings that build trust, develop people, and surface problems early. Covers cadence setup, agenda ownership, conversation frameworks, question banks, and handling difficult topics. Use when: a new manager learning to run 1:1s, resetting unproductive 1:1s that became status updates, onboarding a new direct report, preparing for a difficult performance conversation, building trust with a new team, or coaching through career development discussions.",{"claudeCode":490},"guia-matthieu/clawfu-skills","one-on-ones","https://github.com/guia-matthieu/clawfu-skills",{"basePath":494,"githubOwner":495,"githubRepo":496,"locale":339,"slug":491,"type":267},"skills/leadership/one-on-ones","guia-matthieu","clawfu-skills",{"evaluate":498,"extract":504},{"promptVersionExtension":218,"promptVersionScoring":219,"score":468,"tags":499,"targetMarket":272,"tier":389},[500,501,502,227,503],"management","leadership","1-on-1s","performance",{"commitSha":274},{"repoId":506},"kd72qvzyvm658ya7pbyh5ey47h86md53",[502,227,501,500,503],{"evaluatedAt":509,"extractAt":510,"updatedAt":509},1778690060639,1778688112811,{"_creationTime":512,"_id":513,"community":514,"display":515,"identity":519,"providers":521,"relations":531,"tags":532,"workflow":533},1778688112811.7388,"k174kb1xw6gjba17pk5eyty60s86nv32",{"reviewCount":8},{"description":516,"installMethods":517,"name":518,"sourceUrl":492},"Apply Russell Brunson's Expert Secrets framework to build a mass movement around expertise — create a charismatic leader persona, design a new-opportunity offer, craft belief-breaking stories, and structure a Perfect Webinar that converts. Use when: positioning as an expert to monetize knowledge, creating an online course or coaching program, designing a webinar sales presentation, building a tribe with an identity and cause, crafting an Epiphany Bridge origin story, or packaging expertise into a value ladder.",{"claudeCode":490},"expert-secrets",{"basePath":520,"githubOwner":495,"githubRepo":496,"locale":339,"slug":518,"type":267},"skills/content/expert-secrets",{"evaluate":522,"extract":530},{"promptVersionExtension":218,"promptVersionScoring":219,"score":468,"tags":523,"targetMarket":272,"tier":389},[524,525,526,527,528,227,529],"marketing","sales","expert-positioning","framework","webinar","online-course",{"commitSha":274},{"repoId":506},[227,526,527,524,529,525,528],{"evaluatedAt":534,"extractAt":510,"updatedAt":534},1778689263469]