1,583 件 ・ 関連度順
概要と使いどころ
Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying.
日本語の概要は準備中です。原文の説明を表示しています。
Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/). Encodes why the long tail of control-plane capabilities is deliberately NOT wrapped as MCP/CLI tools, the API-first admission test for whether a capability deserves a recipe, the negative and positive lists, the fixed recipe structure, the writing rules distilled from writing-for-agents, the user-facing copy red lines, and the product regeneration/verification pipeline. Also routes contributors (and their agents) to the contribution flow and the pre-PR self-test protocol in references/contributing.md. Use when adding a recipe, judging whether a scenario belongs in the recipe set, updating the recipes index, re-checking existing recipes against the admission test, or onboarding someone who wants to submit one.
日本語の概要は準備中です。原文の説明を表示しています。
Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.
日本語の概要は準備中です。原文の説明を表示しています。
24/7 autonomous business operations orchestrator with business health scoring, canary monitoring, and safety guardrails. Schedules and runs all business functions automatically — content publishing, social media posting, outreach sequences, ad monitoring, financial reporting, health checks, and post-deploy verification. Use when the user wants to automate operations, schedule tasks, set up autonomous workflows, or says 'automate this', '24/7', 'run automatically', 'schedule', 'cron', 'autonomous', or 'set and forget'.
日本語の概要は準備中です。原文の説明を表示しています。
kubectl operations for applying, patching, deleting, and executing commands on Kubernetes resources. Use when modifying resources, running commands in pods, or managing resource lifecycle.
日本語の概要は準備中です。原文の説明を表示しています。
Deal desk: reviews, approves, and structures non-standard sales deals. Use when standing up a deal desk, building approval-threshold matrices, designing deal-review packets, routing deals, or auditing deals for compliance.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' or 'data hygiene.' For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure IoT Edge development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring EFLOW devices, DPS/X.509 provisioning, gateway/nested topologies, CI/CD deployments, or IoT Edge metrics/logs, and other Azure IoT Edge related development tasks. Not for Azure IoT Hub (use azure-iot-hub), Azure IoT (use azure-iot), Azure IoT Operations (use azure-iot-operations), Azure Stack Edge (use azure-stack-edge).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure IoT Hub development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring IoT Hub/DPS routing, device twins, MQTT/AMQP clients, Device Update, or Cosmos DB event storage, and other Azure IoT Hub related development tasks. Not for Azure IoT (use azure-iot), Azure IoT Central (use azure-iot-central), Azure IoT Edge (use azure-iot-edge), Azure IoT Operations (use azure-iot-operations).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure IoT Central development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when designing device templates, data exports, IoT Edge gateways, REST/CLI automation, or IoT Central migrations, and other Azure IoT Central related development tasks. Not for Azure IoT Hub (use azure-iot-hub), Azure IoT (use azure-iot), Azure IoT Edge (use azure-iot-edge), Azure IoT Operations (use azure-iot-operations).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Digital Twins development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when modeling DTDL graphs, integrating IoT Hub/ADx, configuring endpoints/routes, securing access, or tuning query units, and other Azure Digital Twins related development tasks. Not for Azure IoT Hub (use azure-iot-hub), Azure IoT Central (use azure-iot-central), Azure IoT Operations (use azure-iot-operations).
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
日本語の概要は準備中です。原文の説明を表示しています。
SOC alert triage, incident playbook automation, escalation workflows, shift reporting, and SOC KPI tracking
日本語の概要は準備中です。原文の説明を表示しています。
Business operations: strategy, technology, growth, competitive intelligence, support, finance, HR, legal, operations, sales, productivity, product management.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user requests Mac automation via AppleScript, including: Mail operations, Reminders/Calendar management, Safari control, Finder operations, system controls (volume, brightness, notifications, app launching), third-party apps (development tools, task management, media players), or mentions "AppleScript" or "automate Mac".
日本語の概要は準備中です。原文の説明を表示しています。
Enhanced git operations using lazygit, gh (GitHub CLI), and delta. Triggers on: stage changes, create PR, review PR, check issues, git diff, commit interactively, GitHub operations, rebase, stash, bisect.
日本語の概要は準備中です。原文の説明を表示しています。
Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch. Generates bulk operation scripts, automates cross-service workflows, validates security configurations, and executes JMESPath queries for complex filtering. Triggers on "aws cli help", "aws command line", "aws scripting", "aws automation", "aws batch operations", "aws bulk operations", "aws cli pagination", "aws multi-region", "aws profiles", "aws cli troubleshooting".
日本語の概要は準備中です。原文の説明を表示しています。
Provides Amazon DynamoDB patterns using AWS SDK for Java 2.x. Use when creating, querying, scanning, or performing CRUD operations on DynamoDB tables, working with indexes, batch operations, transactions, or integrating with Spring Boot applications.
日本語の概要は準備中です。原文の説明を表示しています。
Fix NDK (Nostr Dev Kit) operations hanging indefinitely when relay connections stall. Use when: (1) App freezes during fetchEvents or publish calls, (2) No timeout errors despite network issues, (3) Relay connection appears stuck, (4) Using NDK with unstable or slow relays. NDK operations have no built-in timeout - wrap with Promise.race.
日本語の概要は準備中です。原文の説明を表示しています。
Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments authentication, authorization, and input-handling code paths to monitor security-relevant events and states at runtime. Use this skill when developers need to add security monitoring and logging to their code, including tracking authentication attempts (login/logout), authorization decisions (access control checks), input validation failures, session management events, and other security-critical operations. Supports Python, JavaScript/TypeScript, and Java with structured logging patterns. Triggers when users ask to add security instrumentation, monitor security events, log authentication/authorization, track security-sensitive operations, or add security observability to their codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Create or review revenue operations deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for revenue operations planning or analysis.
日本語の概要は準備中です。原文の説明を表示しています。
供应链与生产运营 (供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后 just-in-case、多源、近岸/友岸的回摆;精益派反驳崩的是『假精益』——单一来源+砍库存不砍变异) ⇄ 服务水平 vs 库存成本(安全库存/报童模型/ABC-XYZ 的经典取舍,牛鞭效应放大上游波动) ⇄ 成本导向压价 vs 供应商共生开发(Kraljic 分级、丰田供应商协会式长期共生 vs 年降指标与竞价) ⇄ 一个数 vs 各部门各算各的(S&OP/IBP 的本质是跨职能对齐到一套数字与一份产销计划))**; (b) 工具栈(此行的工具是『系统+方法』的混合) — ERP/MRP(SAP S/4HANA PP·MM、Oracle、用友·金蝶、Odoo、NetSuite)、APS 高级计划排程(Kinaxis RapidResponse、o9、Blue Yonder、SAP IBP、OMP、Siemens Opcenter APS)、MES/车间执行(Siemens Opcenter、Rockwell FactoryTalk、黑湖智造)、WMS/TMS、需求预测(统计模型 + Nixtla StatsForecast/Prophet、FVA 预测增值分析)、运筹优化与仿真(OR-Tools、Gurobi、Pyomo、AnyLogic、FlexSim、SimPy)、供应链风险与多级可视(Resilinc、Everstream、Interos)、分析层(SQL/Python pandas/Power BI)、以及纸笔工具(价值流图 VSM、A3、看板、标准作业票)—— 选型决策树的关键分岔是 MTS/MTO/ATO/ETO 履行模式与需求变异度,而非厂商功能清单; (c) 心智模型层 — 利特尔法则(在制品 = 产出率 × 流动时间)、瓶颈与非瓶颈、缓冲三态(库存/时间/产能缓冲)、解耦点(客户订单渗透点 CODP)、牛鞭效应、takt time 节拍与产线平衡、OEE 与六大损失、muda·mura·muri 三种浪费、自働化 jidoka 与安灯、防错 poka-yoke、SMED 快速换模换出小批量、平准化 heijunka、PDCA 与丰田改善型 Toyota Kata、DMAIC 与 Cpk 过程能力、报童模型与安全库存公式、ABC-XYZ 分级; (d) 工作流/SOP — 跑一轮月度 S&OP(需求评审→供应评审→预 S&OP→执行 S&OP)、做需求预测与预测误差复盘(MAPE/WMAPE/bias/FVA)、设定库存分级与安全库存、MRP 跑批与例外消息处理(缺料齐套与 MRP 神经质)、瓶颈识别与 DBR 排产、价值流图现状图→未来图→改善计划、新品导入 NPI 与多级 BOM/ECN 工程变更、供应商选择与开发(RFQ→审厂→APQP/PPAP→量产→年度绩效)、断料应急与交期承诺(ATP/CTP)、循环盘点与库存准确率; (e) 知识正典(en/ja 一手极厚,中译齐全) — 《目标 The Goal》Goldratt(TOC 小说体奠基)、《丰田生产方式》大野耐一、《改变世界的机器》Womack·Jones·Roos(MIT IMVP 研究)、《精益思想 Lean Thinking》Womack & Jones、《丰田模式 The Toyota Way》Liker、《工厂物理学 Factory Physics》Hopp & Spearman(排队论视角的运营科学)、《学习观察 Learning to See》Rother & Shook(VSM)、《丰田套路 Toyota Kata》Rother、Spear & Bowen 的 HBR 1999《Decoding the DNA of the Toyota Production System》、Lee/Padmanabhan/Whang 1997《The Bullwhip Effect in Supply Chains》、Ptak & Smith 的 DDMRP、Orlicky 的 MRP、Chopra & Meindl 的供应链管理教材、Deming《转危为安 Out of the Crisis》、Sheffi《The Resilient Enterprise》、ASCM/APICS 的 SCOR 参考模型与 CPIM/CSCP 知识体系; (f) 行业大佬/figures — 大野耐一(TPS 立法者)、新乡重夫(SMED/防错)、Eliyahu Goldratt(TOC 创立者)、W. Edwards Deming(变异与系统观)、James Womack & Daniel Jones(把 TPS 译成西方可学的『精益』)、Jeffrey Liker(丰田模式学术化)、Mike Rother(VSM 与改善型)、Wallace Hopp & Mark Spearman(工厂物理学)、Hau Lee(斯坦福,牛鞭效应与 Triple-A 供应链)、Yossi Sheffi(MIT,韧性)、Carol Ptak & Chad Smith(DDMRP)、David Simchi-Levi(MIT,风险敞口指数)、Steven Spear(TPS 的 DNA)、以及中文圈的供应链实务作者(刘宝红等); (g) 争议/批判(必须保留不洗白) — JIT 是不是 2021 全球断链的元凶(精益派反驳:崩的是单一来源+砍库存不砍变异的『假精益』);西方学精益的高失败率(只搬工具不搬思维,精益在很多工厂沦为裁员的代号);六西格玛黑带官僚化与扼杀创新之争;TOC 派与精益派互相攻击(Goldratt 讽刺精益是等浪费自己浮现);预测无用论(需求驱动派说预测必然错、要靠缓冲吸收)vs 统计预测派;控制塔/数字孪生/AI 预测的过度承诺与高项目失败率;中国制造的年降与内卷式压价 vs 供应商共生;近岸·友岸外包是真实产能转移还是政治叙事; (h) 流派/思想谱系 — **精益/TPS 派(丰田血统:大野-新乡→Womack/Jones/Liker/Rother,信全局消除浪费与人的改善能力)** vs **约束理论 TOC 派(Goldratt:系统产出只由瓶颈决定,聚焦五步、DBR、缓冲管理)** vs **统计质量/六西格玛派(Deming-Juran-Shewhart→GE/Motorola,信减少变异与过程能力)** vs **运营科学/工厂物理学派(Hopp & Spearman:用排队论与数学定律解释,认为精益与 TOC 都是特例)** vs **需求驱动/DDMRP 派(Ptak & Smith:预测不可靠,靠战略解耦缓冲)** vs **韧性/风险派(Sheffi、Simchi-Levi:效率之外必须为断链设计)**。不含: 跨境电商卖家的发货与头程物流(已由 cross-border-ecommerce 覆盖)、纯采购的商务谈判技巧、企业级 ERP 的代码实施与二次开发、通用项目管理。) Master OS — automated mastery of 供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
日本語の概要は準備中です。原文の説明を表示しています。