439 件 ・ 関連度順
概要と使いどころ
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
日本語の概要は準備中です。原文の説明を表示しています。
Write a short, fact-checked reply that answers a colleague's question in one meaning only, ready to copy and paste. The input is their pasted message. Check the claims against the code first, use the project glossary terms, and print only the reply in chat. Read-only — no writes to code, the issue tracker, GitHub, chat or any MCP. Use on "/cortex-communication:answer-buzzkill", "help me answer", "reply to this question", or when the user pastes a colleague's question and asks for an answer in the same manner.
日本語の概要は準備中です。原文の説明を表示しています。
Track every dollar, enforce budgets, spot spending patterns, and build wealth — all through natural conversation with your AI agent.
日本語の概要は準備中です。原文の説明を表示しています。
Generate complete board meeting packages — agenda, financial summary, KPI dashboard, risk register, and action item tracker.
日本語の概要は準備中です。原文の説明を表示しています。
Network-wide ad and tracker blocking at the DNS level. A Pi-hole alternative that runs directly on your machine as an OpenClaw skill. No separate hardware needed.
日本語の概要は準備中です。原文の説明を表示しています。
习惯养成监督技能。帮助用户制定合理目标、拆解可执行计划、每日监督打卡、动态调整难度、可视化追踪进度。支持同时跟进最多5个习惯。
日本語の概要は準備中です。原文の説明を表示しています。
公募の外部締切から学内締切、部局承認、e-Rad承認、資料作成期限を逆算する
研究プロジェクトのマイルストーン、課題、成果、リスク、次アクションを月次で追跡する
Checks the canonical upstream issue tracker, discussion forums, and open pull requests, merge requests, or equivalent change queues for existing reports, discussion, or work on a problem just discussed. Use before diagnosing, fixing, or reporting an apparent open-source problem to avoid duplicate effort and missed context.
日本語の概要は準備中です。原文の説明を表示しています。
OpenLineage, DataHub, Marquez for data lineage tracking and impact analysis. Activate on: data lineage, OpenLineage, DataHub, Marquez, impact analysis, data catalog, column lineage, data discovery. NOT for: data quality validation (use data-quality-guardian), dbt documentation (use dbt-analytics-engineer).
日本語の概要は準備中です。原文の説明を表示しています。
Track real-time API cost accrual during LLM execution. Activate on 'cost tracking', 'token usage', 'API costs', 'budget monitoring', 'usage metrics'. NOT for cost estimation, pricing tiers, or billing systems.
日本語の概要は準備中です。原文の説明を表示しています。
Detects somatic mutations in circulating tumor DNA, treating low-VAF detection as a signal-versus-noise problem set by error suppression and molecules sampled, not by the choice of caller. Distinguishes de novo CALLING (scanning a panel for unknown variants, bounded by per-locus error and multiple testing) from tumor-informed DETECTION (tracking a pre-specified variant set, where panel integration reaches single-ppm). Covers VarDict and Mutect2 for de novo calling, UMI-aware callers, and a pysam-based known-variant VAF tracker, with matched-WBC subtraction as the mandatory defense against clonal hematopoiesis (the dominant false positive). Use when calling or tracking tumor mutations from plasma cfDNA, setting a VAF threshold, or deciding whether a low-VAF call is tumor versus CHIP.
日本語の概要は準備中です。原文の説明を表示しています。
Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
日本語の概要は準備中です。原文の説明を表示しています。
Flight tracking and scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Track flights in real-time with detailed status.
日本語の概要は準備中です。原文の説明を表示しています。
Track flights in real-time.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Shared setup and rules for the report-skills bundle (report-publisher, client-reporter, proposal-tracker, deck-publisher, report-designer). Loaded by the individual skills for the common ReportRoom MCP publish flow, account bootstrap, and safety gates. Not invoked directly — pick the specific skill for the job.
日本語の概要は準備中です。原文の説明を表示しています。