「source」の検索結果

List, find, and show Azure resources across subscriptions or resource groups. Handles prompts like "list the websites in my subscription", "list my web apps", "show my app services", "list virtual machines", "list my VMs", "show storage accounts", "find container apps", and "what resources do I have". USE FOR: list websites, list web apps, list app services, show websites in subscription, resource inventory, find resources by tag, tag analysis, orphaned resource discovery (not for cost analysis), unattached disks, count resources by type, cross-subscription lookup, and Azure Resource Graph queries. DO NOT USE FOR: deploying/changing resources (use azure-deploy), cost optimization (use cost-optimization from the optional azure-cost plugin), or non-Azure clouds.

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

List, find, and show Azure resources across subscriptions or resource groups. Handles prompts like "list the websites in my subscription", "list my web apps", "show my app services", "list virtual machines", "list my VMs", "show storage accounts", "find container apps", and "what resources do I have". USE FOR: list websites, list web apps, list app services, show websites in subscription, resource inventory, find resources by tag, tag analysis, orphaned resource discovery (not for cost analysis), unattached disks, count resources by type, cross-subscription lookup, and Azure Resource Graph queries. DO NOT USE FOR: deploying/changing resources (use azure-deploy), cost optimization (use cost-optimization from the optional azure-cost plugin), or non-Azure clouds.

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

When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.

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

Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import support, resource design principles, and required acceptance test coverage. Use when adding or changing a resource or data source, deciding whether an API concept should be a resource, wiring a resource to the provider's configured client, handling drift or resource-not-found, or reviewing a resource implementation before submission.

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

Create and validate Earth2Studio data source wrappers (DataSource, ForecastSource, DataFrameSource, ForecastFrameSource) from remote stores. Do NOT use for fetching data with existing sources, model inference, or installation tasks.

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

Given a Japanese NLP GitHub repo/model/dataset (URL / owner/repo / tool name) OR a topic, find what's already in awesome-japanese-nlp-resources and discover related resources NOT yet listed (contribution candidates). Mines the bundled dataset, then expands via web research across GitHub and Hugging Face. Use when the user names a SPECIFIC repository, model, or tool and wants alternatives/equivalents, OR wants to discover Japanese NLP resources for a topic that are NOT yet in the list, OR wants to prepare a contribution. Trigger phrases include 'mecabに似たツール', 'fugashiの代替', 'alternatives to fugashi', 'repos like manga-ocr', 'what else is like sudachi', 'リストに無い新しい日本語NLP', 'awesome-japanese-nlpに追加できそうな', '最近公開された日本語NLPツール', 'find unlisted Japanese NLP repos', 'new Japanese models on Hugging Face', 'contribute a new resource'. For a simple lookup of what already exists, use the search skill instead.

Use this skill to configure Field Service Lightning service resources — including ServiceResource types, skill assignments via ServiceResourceSkill, capacity-based resource setup, and ResourcePreference rules. NOT for territory-level WorkCapacityLimit throttling or capacity-vs-utilization reporting — use admin/fsl-capacity-planning. NOT for service territory setup — use admin/fsl-service-territory-setup. NOT for work rules and service objectives — use admin/fsl-scheduling-policies.

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

非公開プロジェクトを公開用に複製し、秘密情報や個人情報の除去・検証から、READMEやセットアップ手順、ライセンスの整備まで進めるスキル。

• 非公開プロジェクトを公開したいとき
• 秘密情報や個人情報の残存確認
• 利用者向けの説明と導入手順の整備

Use this skill to ingest external materials into the current project-scoped Obsidian KB as source notes under Sources/Papers, Sources/Web, Sources/Docs, Sources/Data, Sources/Interviews, or Sources/Notes.

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

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.

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

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.

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

Design data-driven Godot 4.7 games with custom Resource classes: define typed data with class_name + @export, save/load .tres/.res files, instance and duplicate resources, and load on demand with ResourceLoader (incl. threaded loading). Use when modeling items/stats/configs as data in a Godot project, creating .tres resources, or working with custom Resource subclasses and ResourceLoader/ResourceSaver.

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

Investigate Azure incidents and service degradations with a read-only workflow using Azure CLI, Resource Health, Activity Log, metrics, resource logs, and official Microsoft docs. Use when troubleshooting Azure outages, Resource Health alerts, Azure Firewall or DNS failures, ExpressRoute or BGP instability, VM availability problems, AKS incidents, App Service failures, database connectivity issues, Entra ID sign-in problems, load balancer issues, platform-vs-workload cutover, or drafting a troubleshooting report. Triggers on 'Azure トラブルシューティング', '障害調査', '切り分け', 'Resource Health', '復旧確認', 'Azure Firewall', 'DNS', 'ExpressRoute', 'VPN Gateway', 'BGP', 'AKS', 'App Service', 'SQL', 'PostgreSQL', 'Cosmos DB', 'Entra ID', 'incident', 'degraded', 'unavailable'.

[omh] Gathering candidate papers, datasets, or repos: source candidate inventory - prepare typed source candidates and acquisition status before downstream work; use ulw-research to fetch and cite them, or research-brief to turn them into a decision-ready brief. Use when the user says: source-finder, source finder, source acquisition, source intake, find papers and datasets, find datasets and repos, find papers, find arxiv link.

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

Guides an end-to-end data-warehouse migration to Amazon Redshift — discovery, schema/SQL/stored-procedure/macro/script conversion, data migration, validation, performance comparison, and reporting. Source-routed via `references/<source>/`; Teradata (Vantage) is the supported source; additional sources are added as their own `references/<source>/` sets. Text-only knowledge (no executable code) — the AI generates all execution at runtime. Applies when a user wants to migrate Teradata to Amazon Redshift, convert Teradata DDL/SQL/stored procedures/macros/BTEQ to Redshift/RSQL, or assess Teradata-to-Redshift migration complexity. Applies only to migrations targeting Amazon Redshift; migrations to other platforms (Snowflake, BigQuery, Databricks, etc.) are out of scope regardless of source. Does not cover general Redshift administration, performance tuning, or troubleshooting of existing Redshift clusters (no migration involved), or sources not listed under references/.

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

Research trending topics, collect source articles, and generate a structured research brief for content creation. Stop writing from thin air — write from real sources. Use this skill when the user wants to research a topic before writing, collect sources for an article, create a research-backed content brief, or says "research [topic] for me", "find sources about [keyword]", "content brief for [topic]", "what's the latest on [product]", "research before writing", "collect articles about [keyword]", "trending news about [topic]", "gather sources for my article", "brief me on [topic]", "what are people saying about [product]", "news roundup for [keyword]", "research brief", "source collection", "content research", "prep research for writing".

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

🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"

Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.

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

When you want to monitor known sources on a schedule and feed the good stuff into your second brain. Configure sources once (YouTube, RSS/newsletters, subreddits, Hacker News, Bluesky, Mastodon, X, LinkedIn, keyword searches); each run fetches only what's new, scores it against your stated focus, writes one digest to the vault, and auto-captures high-signal items into raw/. Everything else waits in the digest until you promote it. Modes — run, digest, promote, add / sources / pause, doctor, schedule (daily launchd or systemd job). Triggers on "/radar," "run my radar," "check my sources," "what's new from my sources," "add a source," "monitor this channel," "watch this subreddit," "track this account," "daily digest," "promote item 4," "radar doctor." Complements second-brain (radar fills raw/, second-brain compiles it) and deep-research (standing surveillance vs a one-off dive).

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

Build custom Python data sources for Apache Spark using the PySpark DataSource API — batch and streaming readers/writers for external systems. Use this skill whenever someone wants to connect Spark to an external system (database, API, message queue, custom protocol), build a Spark connector or plugin in Python, implement a DataSourceReader or DataSourceWriter, pull data from or push data to a system via Spark, or work with the PySpark DataSource API in any way. Even if they just say "read from X in Spark" or "write DataFrame to Y" and there's no native connector, this skill applies.

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

Use Nexscope (Search Intelligence Framework) data to analyze ASIN traffic source composition and exposure distribution, covering current period/previous period/newly entered/exited period comparisons. Trigger when the user mentions ASIN traffic sources, traffic structure analysis, organic traffic vs paid traffic share, exposure score breakdown, period comparison, new/exited traffic keywords, competitor traffic analysis, SP ad keyword count, brand ad exposure, Amazon's Choice exposure, editorial recommendation exposure, Top Rated exposure, video ad exposure, organic search exposure ratio, PPC traffic sources, promotional deal traffic sources, recommendation slot structure breakdown, ASIN traffic analysis, traffic sources, organic traffic share, ad traffic share, exposure analysis, traffic structure, period-over-period comparison, keyword churn, Nexscope. Even if the user does not explicitly mention "Nexscope", if their need involves analyzing an ASIN's traffic sources, exposure channel distribution, cross-period comparison, or competitor traffic structure comparison, this skill should also be triggered.

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

Use when verifying information (fact, number, quote, event, statement) against authoritative primary sources, or cross-checking a number via one-level metric decomposition (Z = P × Q). Triggers: "verify X", "is this true", "find the original source", "where is this number from", "two sources disagree", "is it true X never did Y". Covers five scenarios: (1) basic truthfulness check, (2) completeness / out-of-context quoting, (3) one-level reasoning verification, (4) negative-statement handling, (5) multi-source conflict side-by-side output. Dig into whitelisted primary sources only (user-supplied files, official websites & databases, authoritative industry sources); cited reports / charts / datasets must be downloaded and read locally to count as verified — if download is blocked, hand the link to the user. If nothing can be found, plainly state "cannot verify" rather than guessing, patching, or citing secondary paraphrases. Always reply in the user's question language.

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

Performs comprehensive FiveM resource security, performance, and compatibility audits. Detects backdoors, RATs, SQL injection, event exploitation, NUI vulnerabilities, dupes, crash/DoS vectors, npm and build-chain supply chain attacks, and malware patterns across ESX, QBCore, QBox, ox_lib, and ND_Core frameworks, on both GTA V Legacy and Enhanced builds. Use whenever a FiveM/cfx resource is being reviewed — even if not explicitly asked — including: audit FiveM script, review FiveM security, optimize FiveM resource, check FiveM performance, FiveM code review, review Lua script security, audit ESX resource, audit QBCore resource, audit QBox resource, check for exploits, FiveM vulnerability scan, GTA V Enhanced migration check, resmon optimization, or asking whether a leaked, cracked, nulled or unknown-origin script is safe to run.

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

Windows アプリ開発 (WinUI 3 / XAML) の UI 基盤リファレンス。 レイアウトパネル Grid, StackPanel, Canvas, RelativePanel, SplitView, ScrollViewer、 XAML マークアップ x:Bind, x:Name, x:Class, StaticResource, ThemeResource、 添付プロパティ, 依存関係プロパティ、 スタイル・テーマ Style, ControlTemplate, DataTemplate, VisualStateManager, ResourceDictionary, Acrylic, Mica, SystemBackdrop、 データバインディング Binding, INotifyPropertyChanged, ObservableCollection, IValueConverter, DataContext, MVVM、 アニメーション Storyboard, DoubleAnimation, EasingFunction, ThemeTransition, ConnectedAnimation, ImplicitAnimation。