「schedule」の検索結果

Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.

日本語の概要は準備中です。原文の説明を表示しています。

Test application performance with k6 load/stress/soak/spike scripts and k6 scenarios, Lighthouse CI for Web Vitals, and performance budgets as CI gates. Covers load profiles, custom metrics, bottleneck identification, and Core Web Vitals (LCP, INP, CLS). Use when: "performance test," "load test," "stress test," "soak test," "spike test," "k6," "k6 scenarios," "Lighthouse," "Web Vitals," "Core Web Vitals," "performance budget." Not for: scheduled production probes — use synthetic-monitoring; pixel-diff regressions — use visual-testing; designing tests from prod telemetry — use observability-driven-testing. Related: ci-cd-integration, qa-metrics, release-readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose and fix a failing scheduled (or standalone) TMDb Integration workflow run — re-run transients, or fix real drift on a branch off main, then PR and (optionally) merge. Use for the weekly Sunday Integration cron failure, or any red Integration run not tied to an open PR.

日本語の概要は準備中です。原文の説明を表示しています。

Review and assess every issue in the TMDb project board's Backlog column — re-verify each against current main with a read-only fan-out, close the mechanically dead, promote the actionable to Ready with priority, size and execution order, and leave the rest in Backlog naming the decision they need. Use to groom the backlog, before planning a release, or on a schedule. Runs headless: it decides for itself within the rules below.

日本語の概要は準備中です。原文の説明を表示しています。

Dokku is an open-source, single-server platform-as-a-service: it builds an app from a git push (buildpacks or a Dockerfile), runs it in Docker containers behind nginx, and manages domains, TLS, config and datastores through one CLI. Use when a user asks to "self-host a Heroku alternative", "set up git push deploys on a VPS", "deploy my app with Dokku", "add Postgres or Redis to a Dokku app", "get Let's Encrypt on Dokku", or "fix ports for a Dockerfile app on Dokku". Covers installation from the apt repository, deploys, environment variables, plugins, zero-downtime checks, storage and the k3s scheduler.

日本語の概要は準備中です。原文の説明を表示しています。

Build robust TypeScript applications with Effect — type-safe error handling, concurrency, dependency injection, and streaming. Use when someone asks to "handle errors without try-catch", "type-safe error handling in TypeScript", "dependency injection without classes", "concurrent TypeScript", "Effect library", "replace try-catch with typed errors", or "functional programming in TypeScript". Covers Effect, Layer, Schedule, Stream, and Schema.

日本語の概要は準備中です。原文の説明を表示しています。

Assists with building real-time reactive backends using Convex. Use when creating databases with automatic client sync, reactive queries, file storage, scheduled functions, or full-text and vector search. Trigger words: convex, reactive backend, real-time database, useQuery, useMutation, convex functions, convex schema.

日本語の概要は準備中です。原文の説明を表示しています。

Sets up automated database backup, restore, and disaster recovery procedures for PostgreSQL, MySQL, MongoDB, and Redis. Use when you need to implement backup schedules, point-in-time recovery, cross-region replication, backup verification, or disaster recovery runbooks. Trigger words: database backup, pg_dump, mysqldump, mongodump, disaster recovery, point-in-time recovery, WAL archiving, backup rotation, restore database, RTO, RPO, backup verification.

日本語の概要は準備中です。原文の説明を表示しています。

Dagster is a data pipeline orchestrator built around the concept of software-defined assets. Learn to define assets, ops, jobs, schedules, sensors, and resources for building maintainable data platforms.

日本語の概要は準備中です。原文の説明を表示しています。

Run background tasks in Python with Celery. Use when a user asks to process tasks asynchronously, schedule periodic jobs, run background workers, build task queues in Python, or offload heavy processing from web requests.

日本語の概要は準備中です。原文の説明を表示しています。

Integrate with Google Calendar and Microsoft Outlook Calendar for scheduling, event management, and availability tracking. Use when someone asks to "create calendar events", "check availability", "schedule meetings", "sync calendars", "Google Calendar API", "Outlook Calendar API", "booking system", "find free slots", or "manage recurring events". Covers Google Calendar API v3, Microsoft Graph Calendar API, event CRUD, availability/free-busy queries, recurring events, and building scheduling features.

日本語の概要は準備中です。原文の説明を表示しています。

You are an expert in AWS Lambda, Amazon's serverless compute service. You help developers build event-driven applications using Lambda functions triggered by API Gateway, S3 events, SQS queues, DynamoDB streams, and scheduled events — with support for Node.js, Python, Go, Rust, Java, and container images, automatic scaling from zero to thousands of concurrent executions, and pay-per-invocation pricing.

日本語の概要は準備中です。原文の説明を表示しています。

Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when "inngest, serverless background job, event-driven workflow, step function, durable execution, vercel background job, scheduled function, fan out, inngest, serverless, background-jobs, event-driven, workflows, step-functions, durable-execution, vercel, nextjs" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Kubernetes is the operating system for the cloud. It schedules containers, handles networking, manages storage, and keeps your apps running. But K8s has a steep learning curve - abstractions on abstractions on abstractions. This skill covers the core concepts (Pods, Deployments, Services), production patterns (health checks, resource limits, HPA), and the gotchas that catch everyone (namespace confusion, service discovery, secret management). 2025 reality: You probably don't need to run your own cluster. Use managed K8s (EKS, GKE, AKS) unless you have a very good reason not to. Focus on writing good manifests, not managing etcd. Use when "kubernetes, k8s, kubectl, deployment manifest, helm chart, kustomize, pod, service yaml, ingress, horizontal pod autoscaler, hpa, kubernetes, k8s, containers, orchestration, devops, cloud-native, helm, kustomize" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Founders face unique challenges in how they work. Maker vs manager schedule conflicts. Default alive vs dead math. Time and money slowly leaking away. Effective founders develop systems for navigating these challenges. This skill synthesizes PG's essays on founder productivity and decision-making into an operating system for founder effectiveness. Use when "keywords, contexts, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Manage Buffer content via the GraphQL API. Use when creating, scheduling, editing, or deleting posts, saving ideas, reading scheduled queues, or pulling post analytics. Not for general API debugging.

日本語の概要は準備中です。原文の説明を表示しています。

投行并购 (投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (relationship banking、长期 coverage、reputational capital)」, 「叙事/包装 (the story, equity story, positioning) ⇄ 数字/尽调 (the numbers, diligence, quality of earnings)」, 「估值的科学外衣 (DCF/comps 的伪精确) ⇄ 谈判的真实定价 (价格由 leverage、竞争、时机决定)」; (b) 估值与分析正典 (最标准化、最易蒸出高质量+CLI 化) — DCF (折现现金流: FCF 预测/WACC 折现率/terminal value 终值/Gordon growth vs exit multiple), Comparable Companies (可比公司/trading comps: EV/EBITDA, EV/Revenue, P/E), Precedent Transactions (先例交易/deal comps: control premium 控制权溢价), LBO (杠杆收购模型: IRR/MOIC/debt schedule/sources & uses), Accretion/Dilution (增厚/摊薄分析: EPS 影响、pro forma), Sum-of-the-Parts (分部估值/SOTP), Football Field (估值区间图), Merger Model (合并模型: synergies 协同/purchase accounting/goodwill), Sensitivity/scenario; (c) 交易流程与产出物 — 卖方流程 (sell-side: teaser 简介 → NDA → CIM/IM 信息备忘录 → management presentation → IOI 意向函 → data room 数据室 → LOI/term sheet → confirmatory diligence → SPA 买卖协议 → signing → closing), 买方流程 (buy-side: thesis/sourcing → outreach → valuation → bid → exclusivity → diligence → financing → close), auction 类型 (broad/targeted/negotiated/preemptive bid); 产出物: pitchbook 推介材料、CIM、fairness opinion 公平意见、board presentation、fee letter、engagement letter; (d) 交易结构与条款 — consideration (cash/stock/mix/earnout 对赌)、deal protections (breakup fee 分手费/go-shop/no-shop/MAC 重大不利变化条款)、representations & warranties 陈述与保证、escrow 托管、working capital adjustment 营运资金调整、reverse termination fee、collar 价格区间、tender offer vs merger、hostile vs friendly、defensive tactics (poison pill 毒丸/white knight 白衣骑士/staggered board); (e) 行业结构与角色 — bulge bracket (高盛/摩根士丹利/JPM/BofA/花旗) vs elite boutique (Centerview/Evercore/Moelis/Lazard/PJT/Perella) vs middle market (Houlihan Lokey/William Blair/Harris Williams) vs regional/independent; analyst→associate→VP→director→MD 晋升金字塔; coverage (行业组) vs product (M&A/ECM/DCM/leveraged finance/restructuring); sponsors group (服务 PE); 买方包括 PE/strategic acquirer/corp dev; (f) 量化指标与节奏 — deal fee (success fee 业内通常约 1-2% 视规模递减/retainer/Lehman formula)、league table 排行榜、pitch→mandate 转化、deal velocity、hours culture (analyst 80-100h/week 文化批判)、bonus/comp 结构、deal sheet (简历上的成交清单); (g) 争议/批判 — fairness opinion 是否橡皮图章 (利益冲突: 出意见的 banker 也收成交费)、estimate 的伪精确 (DCF garbage in garbage out、假设驱动结论)、banker 永远建议成交 (deal 偏见、empire building 助推 CEO 自利并购)、协同效应系统性高估 (大量并购毁灭价值、winner's curse 赢家诅咒)、analyst 血汗工厂文化 (2021 高盛 13 人 deck 事件、过劳死争议)、advisory 价值 vs 中介寻租之争、bulge vs boutique 的利益独立性叙事 (boutique 标榜「无承销利益冲突」)、SPAC 泡沫与 de-SPAC 教训; (h) 流派/思想谱系 — 估值学派 (Aswath Damodaran 估值教父/纽大、Tim Koller McKinsey《Valuation》、McKinsey valuation 体系) vs 公司金融教科书派 (Rosenbaum & Pearl《Investment Banking》行业圣经、Brealey Myers Allen、CFI/WSP/BIWS 培训体系) vs 交易实战派 (Bruce Wasserstein《Big Deal》、Joseph Perella/Felix Rohatyn 老派 dealmaker、现代 boutique 创始人) vs 行为/批判派 (并购毁灭价值的学术证据、Damodaran 对协同/控制权溢价的批判、Matt Levine《Money Stuff》解构华尔街逻辑) vs PE/buy-side 视角 (LBO 数学、value creation 杠杆/运营/multiple expansion)。不含: 二级市场股票交易/卖方研究 (equity research)、零售财富管理/private banking、纯 ECM/IPO 承销执行 (虽相关但聚焦 M&A advisory)、纯 PE 投后运营、量化交易/对冲基金策略、纯公司财务报表会计。) Master OS — automated mastery of 投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (rela

日本語の概要は準備中です。原文の説明を表示しています。

Draws an activity flow / system architecture diagram as ONE self-contained, INTERACTIVE HTML+SVG page (2-pane app layout — left: diagram, default fit-to-view with zoom/pan; right: sidebar with explainer cards), styled like a real hand-drawn enterprise doc (Stripe/AWS-docs style — real brand logos for MongoDB/Odoo/n8n/etc. from a bundled Simple Icons library, neutral white boxes, sans-serif, no "AI neon" look), scroll-to-zoom, auto light/dark with a toggle button — clicking a flow (a legend chip, a line, or a step badge) highlights that flow with traveling dots along the arrows in their direction, a ping at the destination box, and a sidebar panel that slides out, while everything else dims; two-way arrows (OUT = solid blue / RETURN = dashed green) carry numbered step badges, colored by semantic meaning (red = auth checkpoint, purple = scheduled flow, amber = data pipeline), a small "hop" arc where two lines are forced to cross, dashed group regions, one explainer card per flow in the right sidebar. Use this skill ANY TIME the user wants to "draw a diagram", "draw a flow", "draw a system diagram", "redraw this so it's easier to follow", "interactive diagram", "two-way diagram", "request/response flow", "make a free-form HTML diagram" — even if they never say the word HTML. Especially good when both the request direction AND the response direction need to be shown, or when a templated tool (archify, mermaid) is too rigid. Do NOT use for data charts (bar/line/pie), and do not use when the user asks specifically for archify or mermaid.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/pause/resume/delete/run, and always pass --agent-id explicitly.

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned SMS and MMS marketing discipline. Use when evaluating SMS as a channel, designing consent-aware sequences, drafting messages, setting cadence, comparing number types or platforms, or defining measurement (TCPA consent, A2P 10DLC, quiet hours, cart-recovery and win-back texts. NOT FOR: email campaigns (use suede-emails), phone capture UX (use suede-site-alchemy), or legal certification) this skill does not give legal advice and never sends, schedules, imports, or registers.

日本語の概要は準備中です。原文の説明を表示しています。

Suede-owned editorial pipeline for agent-run content: six roles with written contracts, one inspectable record that travels between them, and a distribution stage that gives every asset its own argument instead of a shorter draft. Use when content agents return generic, duplicated, or unsourced work, when one flagship piece has to carry a week of distribution, when someone asks to build an AI content team or one-person media company, or when a founder wants a weekly interview-led content system across personal and company accounts. NOT FOR: choosing which topics, pillars, or clusters to cover (use suede-content-strategy); platform mix, cadence, calendars, or listening (use suede-social); an Instagram-specific program (use suede-instagram-growth); running a stage on a schedule with state and stop conditions (use suede-marketing-loops); lane ownership for agents changing code (use suede-agent-teams); writing the flagship piece itself (use suede-ship-copy).

日本語の概要は準備中です。原文の説明を表示しています。

Drive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment. Use when a CI failure, a review comment, a merge conflict, or a scheduled check-in arrives on a PR you opened or were asked to drive.

日本語の概要は準備中です。原文の説明を表示しています。

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

日本語の概要は準備中です。原文の説明を表示しています。

CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.

日本語の概要は準備中です。原文の説明を表示しています。