「source」の検索結果

Use when setting up, configuring, or troubleshooting Marketing Cloud Journey Builder — including entry sources, activities, decision splits, wait activities, goals, exit criteria, journey versions, test mode, or journey analytics. Triggers: 'journey builder setup', 'entry source configuration', 'decision split not routing', 'exit criteria not removing contacts', 'goal not tracking conversion', 'journey version publishing', 'journey re-entry settings', 'wait activity date field'. NOT for coding a custom activity or entry source — use apex/marketing-cloud-custom-activities. NOT for business units and sender profiles — use admin/marketing-cloud-engagement-setup.

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

Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.

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

This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source MySQL instance, the resulting resource is a Cloud SQL for MySQL instance that Google Cloud manages. Cloud SQL handles backups, high availability, and secure connectivity for relational database workloads.

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

Use when a decision needs deep multi-source technical research with cited evidence — technology evaluation, ecosystem comparison, standards/spec fact-finding, "how do others solve X". Triggers on "research X", "deep dive on X", "evaluate X vs Y", "find best practices for X". NOT for library/API doc lookup (see mk:docs-finder); NOT for one-shot URL fetch (see mk:web-to-markdown); NOT for internal codebase discovery (see mk:scout); NOT for project-only Q&A (see mk:ask-me); NOT for comparing solution designs (see mk:brainstorming); NOT for root-cause debugging (see mk:investigate); NOT for wiki ingestion of sources (see mk:wiki-research).

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

Cite-or-Block 架构的基石原子 skill。把报告里的 citation 锚点 (例如 [guideline:CSCO-2024-NSCLC:§5.5.2] / [pmid:12345678:abstract]) 解析为源文件片段,并核对事实声明里的关键词是否在引用源原文里出现。 Foundation atomic skill for the Cite-or-Block architecture. Resolves citation anchors (e.g. [guideline:CSCO-2024-NSCLC:§5.5.2] / [pmid:12345678:abstract]) to raw source text fragments, and verifies whether claim keywords actually appear in the cited source. 使用场景 / Use when: 1. 报告生成后要做 fact-check (resolve_citation + verify_claim_against_source) 2. content-verification-layer 要扫全报告锚点 (parse_citations_in_text) 3. drug-citation-verifier / 任何 cross-check skill 需要"锚点 → 源原文" P0 守护:本 skill **绝不维护任何已知字典**。源里没有 = verified=False, 无例外、无 fallback、无"已知答案兜底"。 P0 guard: this skill **never maintains any built-in dictionary**. Not in source = verified=False. No fallback, no built-in answers.

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

Split or contain large source files according to the source-file boundary ADR without changing behavior opportunistically.

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

Turns a set of questions (form exports, helpdesk logs, meeting Q and A, chat threads, a plain list) plus the source documents the user supplies into a DRAFT FAQ grouped by theme: every answer quoted or paraphrased from a named source with a reference, verbatim quotes for dates, figures, eligibility and obligations, UNKNOWN where the sources are silent, a source register with precedence, a conflicts table and a routing list of unanswered questions to owners. Use when the user asks to "build an FAQ from these documents", "answer these questions from the policy", "turn the Q and A into an FAQ page", "group these questions and answer them from the guide" or "what do our documents say about these questions". Do not use for the manager FAQ of a changed HR policy, use policy-change-briefing instead; for checking whether a document's own claims are evidenced, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.

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

Turns a list of KPIs or metrics into a DRAFT definition sheet: one row per KPI with the name as stated, formula quoted from a source, source system, owner, refresh cadence, unit, filters and known caveats, with UNKNOWN in every cell no source fills and a gap list grouped by data owner. Never composes a formula, sets a target or names an owner the sources do not state. Use when the user asks to "define these KPIs", "build a metrics definition sheet", "document how each KPI is calculated", "which of our KPIs have no owner or formula" or "reconcile the two KPI lists". Do not use for the weekly numbers report, use kpi-weekly-report-writer instead; for field-level definitions of a table, use data-dictionary-builder; for logging a wrong figure as a defect, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Use when working with Crossplane — crossplane Kubernetes-native infrastructure management. Covers managed resources, compositions, provider configurations, composite resource definitions (XRDs), claims, and provider health. Use when managing Crossplane resources, debugging provisioning failures, inspecting compositions, or auditing cloud resource status.

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

Use when working with Deepsource — deepSource code analysis management. Covers automated code reviews, issue detection, antipattern analysis, coverage tracking, and analyzer configuration. Use when managing DeepSource projects, reviewing detected issues, configuring analyzers, or tracking code health metrics.

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

Use when working with Gcp Idle Resources — detect unused and idle GCP resources that incur cost without providing value. Covers unattached Persistent Disks, unused external IPs, stopped VMs, idle Cloud NAT, idle load balancers, old snapshots, idle Cloud SQL instances, abandoned GKE node pools, unused VPC connectors, and orphaned Filestore instances. Includes estimated monthly waste per resource and anti-hallucination rules for safe detection.

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

Use when working with Aws Idle Resources — detect unused and idle AWS resources that incur cost without providing value. Covers detached EBS volumes, idle load balancers, unused Elastic IPs, stopped EC2 instances, idle NAT Gateways, old snapshots, and unused ENIs. Includes estimated monthly waste per resource and anti-hallucination rules for safe detection.

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

Guide the user through connecting a new data warehouse source — Postgres, MySQL, Stripe, Hubspot, MongoDB, Salesforce, BigQuery, Snowflake, and so on. Use when the user wants to "connect Stripe", "import data from Postgres", "add a new data source", "sync my warehouse tables", or wants to pick sync methods for each table. Walks through source-type discovery, credential validation, table discovery, per-table sync_type selection, and the final create call. Also covers picking a good prefix and what to do right after creation.

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

This skill should be used at the start of any computationally intensive scientific task to detect and report available system resources (CPU cores, GPUs, memory, disk space). It creates a JSON file with resource information and strategic recommendations that inform computational approach decisions such as whether to use parallel processing (joblib, multiprocessing), out-of-core computing (Dask, Zarr), GPU acceleration (PyTorch, JAX), or memory-efficient strategies. Use this skill before running analyses, training models, processing large datasets, or any task where resource constraints matter.

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

Windows アプリ開発 (Win32 / WPF / WinForms 相互運用) の相互運用・近代化リファレンス。 Win32 API, CreateWindowExW, WNDPROC, メッセージループ, COM (IUnknown, CoCreateInstance, ComPtr), CsWin32, windows-rs, C++/WinRT (winrt::com_ptr, IAsyncOperation, IDL, ABI 相互運用), C#/WinRT (cswinrt, ComWrappers, AOT/trimming, WindowNative), XAML Islands (DesktopWindowXamlSource, DesktopChildSiteBridge, WindowsXamlManager), WPF/WinForms 相互運用 (HwndHost, HwndSource, WindowsFormsHost, ElementHost), UWP から Windows App SDK / WinUI 3 への 移行 (namespace mapping, AppWindow, DispatcherQueue, .NET Upgrade Assistant)。

Syncpack (モノレポ依存バージョン同期ツール) リファレンス。 .syncpackrc 設定、lint / fix / update / format コマンド、 versionGroups, semverGroups, updateGroups, customTypes, source, catalog プロトコル, semverRangeOnly, minimumReleaseAge, severity, sourceMode, package.json 整列、依存バージョン揃え、CI 連携。

UIKit iOS/iPadOS UI フレームワークリファレンス。 UIViewController, UINavigationController, UITabBarController, UISplitViewController, UIView, UILabel, UIButton, UITextField, UIScrollView, UIStackView, UITableView, UICollectionView, diffable data source, NSDiffableDataSourceSnapshot, UICollectionViewCompositionalLayout, Auto Layout, NSLayoutConstraint, NSLayoutAnchor, UILayoutGuide, intrinsicContentSize。

AEM Cloud Service expert skill for OSGi Event Admin handlers (non-resource events). Covers migration of javax.jcr.observation.EventListener (residual non-resource cases) and OSGi EventHandler with inline business logic to the lightweight EventHandler + JobConsumer split. Includes routing rules (resource events go to resource-change-listener, external notification goes to AEM Eventing), TopologyEventListener for leader-only execution, replication and workflow event patterns, service-user setup, review checklist, troubleshooting, and common pitfalls.

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

Generate or edit a source-grounded newsletter issue, digest, or briefing from provided or researched sources. Use for weekly/monthly updates, curated links, executive digests, community newsletters, or "turn these sources into a newsletter"; do not use for UI landing pages, marketing campaign design, unsourced news claims, or long-form research reports.

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

Hunt source code and build artifact leakage — JavaScript source maps (.js.map) reconstructing TypeScript/ES6 source, Swagger/OpenAPI JSON endpoint discovery, .env/.git exposure, webpack chunks with hardcoded secrets, robots.txt/security.txt recon, build-info files, asset-manifest.json API route discovery, .DS_Store file listing. Use at the START of every recon session — these findings often unlock the entire attack surface.

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

Analyze any codebase's source code in depth and produce structured analysis documents saved as markdown files. Use this skill whenever the user asks to understand how a codebase works — architecture, module design, call flows, data models, design patterns, performance characteristics, or any implementation detail. Trigger on phrases like "analyze the source", "explain this code", "how does X work", "where is Y implemented", "trace the flow of", "what happens when", "read through the code", "code walkthrough", "源码分析", "代码解读", "实现原理", "架构分析", "调用链路", "模块分析", or any code-exploration request. Works with any programming language: TypeScript/JavaScript, Java, Python, Go, Rust, C/C++, and more. Even if the user's question seems simple (e.g., "这个文件是干什么的"), use this skill — a thorough, source-backed analysis document is always more valuable than a surface-level guess.

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

エージェント向けスキルの新規作成や修正を支援し、呼び出し条件、作業手順、付属ファイルの配置を整理して、設定や参照先、補助スクリプトを検証します。

• 定型作業をスキルにまとめたいとき
• 既存のSKILL.mdを修正したいとき
• 付属資料やスクリプトを整理したいとき

iMessageやSNSのDMを送信者・期間で絞って確認し、要約や最近のワンタイムコードを取り出します。確認した情報源とスレッド、取得結果も明示します。

• 最近のメッセージやDMを確認したいとき
• ワンタイムコードを探したいとき
• 返信前に会話を確認したいとき

Itôのバスケットや予測市場のデータを閲覧・整理し、手元の調査メモとの比較、出典付きの市場概要、人が確認するための計画シートを作成します。

• Itôのバスケット一覧を調べたいとき
• 調査メモやウォッチリストとの比較
• 出典付きの予測市場概要の作成