531 件 ・ 関連度順
概要と使いどころ
Draft and register project proposals, protect issued terms, and record explicitly evidenced commercial lifecycle changes. Sending messages is separate authorization.
日本語の概要は準備中です。原文の説明を表示しています。
When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Turn whatever the agent just produced — a conversation, an analysis, an artifact, a markdown file — into a live shareable URL in seconds, published as-is via ReportRoom. Use when the user says "share this", "give me a link", "put this online", "make this a page", "send this to someone". This is the fast, verbatim path — for a restructured, designed report use report-publisher; for a view-tracked proposal use proposal-tracker.
日本語の概要は準備中です。原文の説明を表示しています。
Guides God Committee members through consensus-building for collective decisions. Use for proposals, voting, and disagreement resolution. Triggers on: consensus, voting, proposal, committee decision.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive expertise in decentralized autonomous organization governance systems, including Snapshot off-chain voting, OpenZeppelin Governor on-chain execution, treasury multi-sigs, proposal lifecycles, delegation, and governance attack prevention. Use when "DAO governance, on-chain voting, Snapshot, Governor contract, governance proposal, treasury management, multi-sig, token voting, delegation, quorum, timelock, governance attack, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
B2B 大客户销售 (B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄ 资格审查纪律 (MEDDIC/MEDDPICC: 先严格 qualify/disqualify, 「no deal 好过 bad deal」)**; 三派不是非此即彼, 资深人混用, 但底层世界观分歧真实(问 vs 教 vs 筛); 更深层张力 — 「过程/方法论纪律 (process rigor: 预测准确、deal inspection、qualify) ⇄ 关系/信任 (relationship: champion 培养、高管关系、人情)」, 「卖结果/业务价值 (business outcome/ROI、卖给经济决策人) ⇄ 卖产品/功能 (feature selling)」, 「多线程触达买方委员会 (multithreading buying committee) ⇄ 单一 champion 依赖」; (b) 方法论正典 (最标准化、最易蒸出高质量+CLI 化) — MEDDIC/MEDDPICC (Metrics 量化指标/Economic buyer 经济决策人/Decision Criteria 决策标准/Decision Process 决策流程/Identify Pain 痛点/Champion 内部拥护者 + Paper process 签约流程/Competition 竞争), SPIN (Situation/Problem/Implication/Need-payoff 提问序列), Challenger (商业洞见 commercial insight + reframe + 建设性张力 constructive tension + Mobilizer 调动者), Solution Selling (痛点链 pain chain/愿景创建/buying vision), Sandler (前置合约 up-front contract/痛苦漏斗 pain funnel/潜艇七步), Command of the Message (Force Management: 业务价值框架/before-after/decision criteria), Gap Selling (Keenan: 现状 current state → 期望 future state → 差距 the gap/问题中心), Miller Heiman Strategic Selling (蓝表 blue sheet/buying influences: 经济/用户/技术买家 + coach), Value Selling, BANT (老式资格框架, 多被 MEDDIC 取代); (c) 行业结构与角色 — SDR/BDR (开发/约见) → AE/客户经理 (成交) → SE/售前/Solutions Engineer (技术验证/POC/demo) → CSM (客户成功/续约扩张) → Sales Manager/VP Sales/CRO; RevOps (收入运营), Sales Enablement (赋能); land and expand (先落地再扩张)、量化指标 quota/OTE(目标总收入)/配额达成率/pipeline coverage(管道覆盖率 ~3x 业内经验法则)/win rate(赢率)/sales velocity(销售速度)/ramp time(爬坡期)/ACV·ARR·NRR(年合同额/年经常性收入/净收入留存); (d) 销售周期 (the deal/opportunity lifecycle) — prospecting 开发 → discovery 需求挖掘 → qualification 资格审查(MEDDIC) → demo/technical validation/POC 技术验证 → business case/value 业务价值与 ROI → proposal 提案 → negotiation 谈判(procurement 采购/法务/security review) → close 成交 → onboarding/expansion 交付与扩张; 干系人: champion 拥护者 vs coach 线人 vs economic buyer 经济决策人 vs blocker 阻碍者; mutual action plan/close plan(双向行动计划/成交计划); (e) 产出物与节奏 — discovery call(需求电话)、demo、business case、proposal/SOW、MAP(mutual action plan)、forecast(预测: commit/best case/pipeline 类别)、pipeline review/deal review/QBR(季度业务回顾)/account plan(客户计划); (f) 职业/招聘/薪酬 — quota/OTE/comp plan(底薪+提成)/accelerator(加速器)/SPIFF/clawback、ramp、President's Club(顶尖销售俱乐部)、SDR→AE→管理 晋升路径、rep turnover(销售流失率高); (g) 争议/批判 — Challenger 是否过誉(CEB 原始数据被质疑、insight selling 批评)、MEDDIC 沦为填表剧场(box-checking theater, 填字段不真 qualify)、活动指标 vs 质量(spray-and-pray 群发/冷电话存废之争)、AI SDR/自动化淹没收件箱(2024-2025 AI BDR 泡沫 + 邮件送达率崩溃 backlash)、SDR 军团模式是否将死(Winning by Design/signal-based GTM 取代)、配额虚高与销售 burnout、季末打折促单、销售方法论的「宗教化」与培训-认证产业链、最大竞争对手其实是「no decision/维持现状」而非对手; (h) 流派/思想谱系 — 提问诊断派(Rackham SPIN/Bosworth&Eades Solution Selling/Keenan Gap Selling) vs 挑战教学派(Dixon&Adamson Challenger/Force Management Command of the Message) vs 资格纪律派(MEDDIC: Napoli&Dunkel 起源/John McMahon/MEDDICC Andy Whyte) vs 关系战略派(Miller Heiman Strategic/Large Account) vs SaaS 现代收入架构派(Aaron Ross Predictable Revenue/Mark Roberge Sales Acceleration Formula/Jacco van der Kooij Winning by Design bowtie/David Skok 指标) vs 开发-心态派(Jeb Blount Fanatical Prospecting/Sales EQ、Anthony Iannarino、Josh Braun) vs 谈判(Chris Voss Never Split the Difference 战术同理心)。不含: B2C/零售/电商导购销售、纯电话客服/客户支持、纯渠道/分销管理(channel 虽相关但聚焦直销复杂销售)、纯 marketing/需求生成(demand gen 虽上游但本 skill 聚焦销售执行)、纯 CSM 客户成功(虽相关但聚焦 new logo + expansion 的销售动作)。) Master OS — automated mastery of B2B 大客户销售 / 企业级复杂销售 (Enterprise B2B Sales / Complex Selling) — 面向企业客户的高价值、长周期、多干系人复杂销售的职业认知操作系统，从业者(AE/客户经理/SE 售前/销售负责人 VP Sales/CRO)、想入行者、以及服务这行(销售咨询/enablement/RevOps)的视角。覆盖: (a) 第一性张力 — 三大方法论流派之争: **买方主导的诊断式提问 (consultative/discovery-led: SPIN 提问 → 痛点 → 方案, 「像医生先诊断再开方」) ⇄ 卖方主导的教学式挑战 (Challenger: Teach-Tailor-Take control, 用商业洞见 reframe 客户认知, 「像老师挑战客户的既有想法」) ⇄
日本語の概要は準備中です。原文の説明を表示しています。
Unified Agency Proposal Generator — builds a three-tier service proposal with ROI projections from all available audit data
日本語の概要は準備中です。原文の説明を表示しています。
Use when a researcher, maintainer, or contributor found or suspects a malicious skill on ClawHub and needs a private reporting workflow: opening a GitHub private vulnerability report, preparing a proposal-only PR, creating `proposals/<GHSA-ID>/clawscan.yml`, running ClawScan against the malicious skill, and explaining what evidence belongs in private versus public channels.
日本語の概要は準備中です。原文の説明を表示しています。
The single config quality skill. Two modes: (1) Default — review/wire pending self-improvement proposals. (2) Audit — analyzes skills, rules, CLAUDE.md, project refs, hooks, and agents against the actual codebase to find inaccuracies, trigger overlaps, stale references, and weak rules, then fixes them. Trigger on 'self-evolve', 'evolve', 'config health check', 'audit config', 'check claude setup', 'apply this rule', 'reorganize rules', 'ok' (when proposals are pending). NOT for improving individual skills (use skill-creator), diagnosing code bugs (use diagnose), or fixing broken code (use fix).
日本語の概要は準備中です。原文の説明を表示しています。
Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".
日本語の概要は準備中です。原文の説明を表示しています。
Produce a professional, send-ready deliverable on the user's behalf — in the correct file format (never raw markdown), in the user's voice, structured to lead with the strongest material, and free of document-level AI tells. Runs a gated pipeline with a fresh-context verification policeman and a Stop-hook that won't let the session finish without a verified PASS. Use when producing a job take-home, client report, executive one-pager, slide deck, proposal, or anything going out under the user's name.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating grant ideas, diagnosing proposal logic, framing fundable projects, strengthening reviewer-aware arguments, or preparing to write any section of a research proposal.
日本語の概要は準備中です。原文の説明を表示しています。
Audit the reasoning of a document or argument (memo, proposal, investment analysis, board paper, article, the user's own draft): claims, evidence, unstated assumptions, logical gaps, fallacies, and what would falsify it, each anchored to quoted text. Use whenever the user wants reasoning examined, in any language ("audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft"; Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "góp ý bản nháp của tôi"), even when they never say "critical thinking". Also use when the user drops a document and asks whether to trust or act on it, or asks to see their reasoning profile. Not for company-level strategic bets (strategy-board) or learning a topic through dialogue (socratic-questor).
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator skill that takes a warp-apply receipts directory and proposes each batch to its corresponding multisig signer — Safe Transaction Service via `safes/propose-warp-batch.ts` for EVM batches (auto-detects governance context: AW / Foundation / Regular / etc. per filename), Squads via `squads/propose-warp-batch.ts` for SVM batches. Persists a per-ticket proposal summary at `~/.hyperlane/proposals/ticket-id.yaml` so the human can track signing progress in Heimdall or Squads.
日本語の概要は準備中です。原文の説明を表示しています。
Close a specific deal — diagnose why a deal is stalling, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", or "help me get to yes".
日本語の概要は準備中です。原文の説明を表示しています。
The Relic of one afternoon — a proposal on a cold beach — kept as a moment rather than a story, with the parts nobody remembers marked as missing. 一个下午的 Relic：冷风海滩上的求婚，作为「时刻」而不是故事保存——没人记得清楚的部分就标成空缺。
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Better proposals, faster closes. Use when creating AI agent pricing, automation proposals, ROI calculations, or sales materials. Generates professional pricing pages, case studies, and closing scripts for AI automation services.
日本語の概要は準備中です。原文の説明を表示しています。
Design system that makes HTML output look like a professional consulting deliverable instead of default AI styling. Use WHENEVER generating any HTML document — report, analysis memo, proposal, research summary, dashboard, artifact — and when the user says 「HTMLで資料」「HTMLでまとめて」「レポートにして」「コンサル風に」「資料っぽく」「デザインがダサい」 or asks to restyle existing AI-generated HTML. Replaces boxes, borders, gradients, emoji and rainbow colors with whitespace-driven, typography-first, print-ready (A4) design.
Identifies governance-related catalysts with board refreshment, compensation reform, and shareholder proposal analysis. Use when analyzing governance catalysts, evaluating shareholder proposals, or assessing governance improvement potential.
日本語の概要は準備中です。原文の説明を表示しています。
Collaborative document creation via a structured three-stage workflow. Use for writing specs, PRDs, design docs, proposals, RFCs, and any long-form document where quality and clarity matter. Brainstorms 5-20 options per section, builds iteratively, and tests with reader sub-agents.
日本語の概要は準備中です。原文の説明を表示しています。