2,688 件 ・ 関連度順
概要と使いどころ
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
日本語の概要は準備中です。原文の説明を表示しています。
Independently review a CUMCM computation package before its claims enter validation or paper writing. Use only inside a generated independent-review package.
日本語の概要は準備中です。原文の説明を表示しています。
Build or resume mathematical-modeling competition work, including CUMCM, MCM/ICM, graduate and regional contests, data challenges, and open-topic statistical modeling. Guide problem framing, modeling, computation, validation, Chinese or English LaTeX writing, and reviewed PDF/source delivery using current official requirements. Not for ordinary paper polishing.
日本語の概要は準備中です。原文の説明を表示しています。
Deep technical SEO auditing covering crawlability, indexation, Core Web Vitals, site architecture, canonicalization, structured data validation, and performance optimization. Use when the user asks about technical SEO, site audits, crawl issues, indexation problems, Core Web Vitals, page speed, or site architecture optimization. For content-focused SEO, see the seo-content-writer skill.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic analysis of Google Ads and Meta advertising spend to identify wasted budget. Produces actionable exclusion lists with thematic categorization and statistical validation. Use when onboarding new accounts, performing monthly hygiene, or preparing for budget optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Build high-performance APIs with Elysia on Bun. Use when someone asks to "create an API with Bun", "build a REST API with Elysia", "set up WebSocket server on Bun", "type-safe API with Eden Treaty", "Elysia plugin", or "fastest TypeScript HTTP framework". Covers REST routes, WebSocket, validation with TypeBox, Eden Treaty type-safe client, plugins, auth guards, and OpenAPI/Swagger generation.
日本語の概要は準備中です。原文の説明を表示しています。
Builds command-line tools in Go with Cobra, the library behind kubectl, Hugo and the GitHub CLI: subcommands, flags, argument validation, generated help and shell completions. Use when a user asks to create a Go CLI, add subcommands or flags, validate arguments, bind flags to config files and environment variables with Viper, or generate bash, zsh, fish or PowerShell completions.
日本語の概要は準備中です。原文の説明を表示しています。
Implement safety guardrails for AI systems — content filtering, prompt injection detection, output validation, bias mitigation, and responsible AI practices. Use when tasks involve adding safety layers to LLM applications, detecting prompt injection attacks, filtering harmful content, implementing rate limiting for AI APIs, validating LLM outputs against schemas, building moderation pipelines, or ensuring AI systems comply with safety policies.
日本語の概要は準備中です。原文の説明を表示しています。
Test REST and GraphQL API endpoints with structured assertions and reporting. Use when a user asks to test an API, hit an endpoint, check if an API works, validate a response, debug an API call, test authentication flows, or verify API contracts. Supports GET, POST, PUT, PATCH, DELETE with headers, body, auth, and response validation.
日本語の概要は準備中です。原文の説明を表示しています。
Ant Design (antd) is a React component library of 70+ enterprise UI components (tables, forms, date pickers, modals, menus) with design-token theming through ConfigProvider. Use it to build admin panels, back-office tools and data-heavy dashboards: server-paginated tables with filters and bulk actions, validated forms, dark or branded themes, and antd inside Next.js without a flash of unstyled content. Triggers: "antd table", "Ant Design form validation", "customize antd theme", "antd dark mode", "antd with Next.js App Router", "upgrade antd 5 to 6".
日本語の概要は準備中です。原文の説明を表示しています。
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when "micro saas, indie hacker, small saas, side project, saas mvp, ship fast, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Data pipeline specialist for ETL design, data quality, CDC patterns, and batch/stream processingUse when "data pipeline, etl, cdc, data quality, batch processing, stream processing, data transformation, data warehouse, data lake, data validation, data-engineering, etl, cdc, batch, streaming, data-quality, dbt, airflow, dagster, data-pipeline, ml-memory" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementations. The LLM never sees your code - it only sees the schema and description. Use when "agent tool, function calling, tool schema, tool design, mcp server, mcp tool, tool use, build tool for agent, define function, input_schema, tool_use, tool_result, agents, tools, function-calling, mcp, json-schema, anthropic, openai, llm-tools" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Implement comprehensive safety guardrails for LLM applications including content moderation (OpenAI Moderation API), jailbreak prevention, prompt injection defense, PII detection, topic guardrails, and output validation. Essential for production AI applications handling user-generated content. Use when ", guardrails, content-moderation, prompt-injection, jailbreak-prevention, pii-detection, nemo-guardrails, openai-moderation, llama-guard, safety" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Use before declaring a production feature done.
日本語の概要は準備中です。原文の説明を表示しています。
API Security Best Practices workflow skill. Use this skill when the user needs Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Market Research workflow skill. Use this skill when the user needs Analyze market conditions, geographic opportunities, pricing, consumer behavior, and product validation across Google Maps, Facebook, Instagram, Booking.com, and TripAdvisor and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Market Research workflow skill. Use this skill when the user needs Analyze market conditions, geographic opportunities, pricing, consumer behavior, and product validation across Google Maps, Facebook, Instagram, Booking.com, and TripAdvisor and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
API Security Best Practices workflow skill. Use this skill when the user needs Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
API Security Best Practices workflow skill. Use this skill when the user needs Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
API Security Testing Workflow workflow skill. Use this skill when the user needs API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
API Security Testing Workflow workflow skill. Use this skill when the user needs API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
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 客户认知, 「像老师挑战客户的既有想法」) ⇄
日本語の概要は準備中です。原文の説明を表示しています。