6,413 件 ・ 関連度順
概要と使いどころ
Automatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.
日本語の概要は準備中です。原文の説明を表示しています。
Safe deployment workflow for Drupal 10/11 sites: pre-flight checks, backup, the correct update sequence (composer install, database updates, config import, cache rebuild), verification, and rollback plan. Use when deploying to any environment, releasing to production, or when the user asks to "push changes live", "update the server", or run a release. Also use for multisite releases where each site needs its own database update pass.
日本語の概要は準備中です。原文の説明を表示しています。
How to fetch the latest github/gh-aw release binary — either as the gh CLI extension (gh aw ...) or as a raw platform binary downloaded from GitHub Releases — including how to resolve the latest tag, pick the right asset, and verify its checksum.
日本語の概要は準備中です。原文の説明を表示しています。
Publish and verify a released GEODE version across GitHub Release and PyPI/uv. Use for uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.
日本語の概要は準備中です。原文の説明を表示しています。
Mandatory 3-phase explore-reason-act workflow before code modification. Enforces read-before-write, root cause hypothesis formulation, minimal change application. Triggered by "explore" ("탐색"), "reason" ("추론"), "read before write", "root cause" ("근본 원인") keywords.
日本語の概要は準備中です。原文の説明を表示しています。
Validates and summarizes the four required authorization forms in a personal injury matter (retainer, HIPAA release, insurance authorization, employment record release). Confirms signatures, dates, scope, and completeness to determine readiness for the investigation phase. Use when reviewing client onboarding packets, verifying authorization forms before discovery, or checking HIPAA and record-release compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Naturalistic causal reasoning for failures and disputed attribution. Use when postmortems or root-cause debates need reframing. NOT for causal inference, fault trees, or fully observed failures.
日本語の概要は準備中です。原文の説明を表示しています。
Expert causal reasoning and mental model construction for diagnosis and prediction in complex domains
日本語の概要は準備中です。原文の説明を表示しています。
Use for bounded reasoning, partial planning, commitment policy, deliberation cost, and reconsideration-threshold design instead of assuming free deliberation. NOT for exhaustive planning, static optimization, or domains where reconsideration cost is irrelevant.
日本語の概要は準備中です。原文の説明を表示しています。
Identify and counteract cognitive biases in medical decision-making through systematic error analysis and contextual algorithm application. For diagnostic reasoning, treatment decisions, and clinical judgment improvement. NOT for basic medical knowledge, technical procedures, or non-clinical healthcare domains.
日本語の概要は準備中です。原文の説明を表示しています。
What you can build and do with an always-on AI agent that has episodic memory. Covers concrete product ideas, workflows, emergent capabilities from persistence plus memory, and real-world examples of deployed persistent agents. Helps you go from "I have the architecture" to "here's what it actually does for me." Activate on: "what can an always-on agent do", "persistent agent use cases", "agent applications", "proactive agent ideas", "what to build with episodic memory", "always-on agent product", "personal AI assistant ideas", "/always-on-agent-applications". NOT for: building the architecture (use always-on-agent-architecture), designing inputs (use always-on-agent-inputs), safety and privacy (use always-on-agent-safety).
日本語の概要は準備中です。原文の説明を表示しています。
Structured second-pass reasoning after code review or plan evaluation. Offers named reasoning methods (pre-mortem, inversion, red team, Socratic, etc.) to re-examine findings through a specific lens. Use after /mk:review verdict or any time deeper analysis is needed on an existing output. NOT for initial review (see mk:review); NOT for creating implementation plans (see mk:plan-creator).
日本語の概要は準備中です。原文の説明を表示しています。
Prioritizes rare-disease variants from trio/quad WES/WGS with de novo (DeNovoGear, Triodenovo), compound-heterozygous phasing (WhatsHap), mosaic VAF tiering, phenotype-driven ranking (Exomiser, Phen2Gene, AMELIE), ClinGen gene-disease validity gating, and ACMG SF v3.2 secondary findings reporting. Use when running diagnostic exome / genome pipelines, identifying candidate Mendelian disease genes, screening for incidental findings, or auditing VUS reclassification cycles. The ACMG/AMP classification framework (PVS1 decision tree, Pejaver PP3/BP4 calibration, Tavtigian point system) is in clinical-databases/acmg-classification.
日本語の概要は準備中です。原文の説明を表示しています。
Guides timing of breast surgery for transgender males based on physical and mental health status. Triggers include transgender male considering breast surgery or requesting mastectomy.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends measuring late-night salivary or serum cortisol to screen for Cushing's disease recurrence in patients with eucortisolism after transsphenoidal surgery, including cases where eucortisolism was established by medical treatment prior to surgery. Use when postoperative follow-up shows eucortisolism (normal morning cortisol/UFC) but concern for recurrence exists.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether a kidney from a brain-dead deceased donor (DBD) with diabetes mellitus and/or hypertension is suitable for transplantation, using the ISOT 2025 Delphi consensus and Table 4 eligibility checklist. Trigger when a clinician asks "can I use a kidney from a diabetic deceased donor", "is this DBD with HTN/DM acceptable", "ECD donor with diabetes — accept or decline", "DBD eligibility for hypertensive donor", or shares a deceased donor with diabetes or hypertension and needs an accept/borderline/decline decision.
日本語の概要は準備中です。原文の説明を表示しています。
Order and interpret lipoprotein(a) [Lp(a)] measurement at least once in a lifetime, apply the risk-enhancer threshold (≥125 nmol/L or ≥50 mg/dL), and run cascade screening of first-degree relatives for premature ASCVD, familial hypercholesterolaemia, or elevated Lp(a) per the 2026 ACC/AHA multisociety dyslipidaemia guideline. Covers the Class 1 lifetime measurement, how elevated Lp(a) affects LLT initiation and intensification, the cascade screening indications, the interaction of Lp(a) with ASCVD risk estimation, and current therapeutic limitations. Use when a clinician asks when to check Lp(a), how often to repeat Lp(a), elevated Lp(a) what next, treatment for high Lp(a), should I screen my patient's family, Lp(a) and statins, cascade screening indications. Grounded in the 2026 ACC/AHA multisociety dyslipidaemia guideline.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.
日本語の概要は準備中です。原文の説明を表示しています。
npm 릴리스 운영. release 브랜치 선택 커밋 반영, 검증, publish, tag, GitHub Release, main 동기화 진행
日本語の概要は準備中です。原文の説明を表示しています。
NoteDeck のリリース作業（バージョンバンプ → PR → タグ push → Release 確認）を手順どおり実行
Handles public relations, media outreach, press releases, and earned media strategy for SMEs. Creates press releases, media pitches, spokesperson briefings, crisis communication plans, and event communications. Use when user asks about PR, press releases, media relations, journalist outreach, crisis communication, or public-facing communications.
日本語の概要は準備中です。原文の説明を表示しています。
Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces. Triggers on 'announce the release', 'write changelog post'.
日本語の概要は準備中です。原文の説明を表示しています。