2,224 件 ・ 関連度順
概要と使いどころ
MLOps across model deployment, ML pipelines, monitoring, and feature stores. Use when deploying models to production, building training pipelines, setting up drift detection, configuring feature stores, or automating ML CI/CD workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor keyword rankings with drop alerts and SERP features. Two-snapshot compare → seo-drift. "track our keyword rankings"
日本語の概要は準備中です。原文の説明を表示しています。
Monitor GEO visibility over time across six AI answer engines, with a 0-100 trend. "is ChatGPT mentioning us"
日本語の概要は準備中です。原文の説明を表示しています。
Monitor competitors over time: baseline sites, pricing and ads by script, flag changes. "track our competitors over time"
日本語の概要は準備中です。原文の説明を表示しています。
The canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end external local counsel lifecycle management for multi-jurisdiction legal matters. LC selection criteria and capability assessment, engagement setup and instruction design, performance monitoring and check-in cadence, scope enforcement, and relationship escalation. Use when selecting local counsel for a jurisdiction, designing LC instructions, managing the LC check-in rhythm, enforcing scope boundaries when LC signals overreach, or escalating a performance or relationship issue beyond the matter team. Trigger on: 'which LC should we use', 'LC instruction', 'brief the local counsel', 'LC hasn't responded', 'LC is going off scope', 'LC scope dispute', 'confirm scope with LC', 'LC check-in', 'LC is slow', 'monitor the LC network', 'LC engagement letter', 'LC selection', 'what should we tell the local counsel', 'LC onboarding', 'LC performance issue', 'LC relationship problem'.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document types: SSP, SAP, SAR, POA&M, CIS/CRM workbooks. Also trigger for questions about FedRAMP Certification Classes (A, B, C, D — new baseline labels: A = pilot/transitional, B = LI-SaaS/Low, C = Moderate, D = High, per NTC-0004), FedRAMP 20x (now the primary authorization pathway), OSCAL mandate (September 2026), 3PAO assessments, continuous monitoring (ConMon), gap assessments, system boundary definition, or architecture reviews for federal cloud. FedRAMP Ready retires July 28, 2026. When in doubt, use this skill — it covers the full FedRAMP lifecycle from readiness through continuous monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
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 a library of metacognitive prompts targeting planning, monitoring, or evaluation for a specific task. Use when developing students' thinking-about-thinking during independent work.
日本語の概要は準備中です。原文の説明を表示しています。
Expert debugging and profiling for leaks, GPU/Visual Profiler, headless CI QA, orphan nodes, thread-safe logs, and custom Debugger monitors — not print/breakpoint tutorials. Trigger on OBJECT_ORPHAN_NODE_COUNT, ObjectDB growth, Visual Profiler GPU spikes, flaky headless exits, or remote device consoles. Keywords: orphan nodes, Performance.get_monitor, Visual Profiler, Time.get_ticks_usec, EditorDebuggerPlugin, headless QA, push_error, backtrace.
日本語の概要は準備中です。原文の説明を表示しています。
Expert debugging and profiling for leaks, GPU/Visual Profiler, headless CI QA, orphan nodes, thread-safe logs, and custom Debugger monitors — not print/breakpoint tutorials. Trigger on OBJECT_ORPHAN_NODE_COUNT, ObjectDB growth, Visual Profiler GPU spikes, flaky headless exits, or remote device consoles. Keywords: orphan nodes, Performance.get_monitor, Visual Profiler, Time.get_ticks_usec, EditorDebuggerPlugin, headless QA, push_error, backtrace.
日本語の概要は準備中です。原文の説明を表示しています。
Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals performance metrics. Use when the user wants to: (1) Add analytics to a React app (Next.js App Router, Next.js Pages Router, Vite, Create React App, or Remix), (2) Track user events or interactions, (3) Monitor scroll depth or element visibility, (4) Add session recording/replay, (5) Track Web Vitals or performance metrics, (6) Measure user engagement or time on page, (7) Set up product analytics or telemetry. Triggers: "add analytics", "track events", "session recording", "web vitals", "user tracking", "temps analytics", "react analytics".
日本語の概要は準備中です。原文の説明を表示しています。
SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO — baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Resiliency development including security, configuration, and deployment. Use when configuring resiliency drills, backup/replication policies, Recovery Plans RBAC, or Infra Resiliency Manager coverage, and other Azure Resiliency related development tasks. Not for Azure Reliability (use azure-reliability), Azure Site Recovery (use azure-site-recovery), Azure Backup (use azure-backup), Azure Monitor (use azure-monitor).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Update Manager development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when onboarding VMs/Arc servers, configuring patch schedules/ESU, using SDK/REST APIs, or integrating runbooks/webhooks, and other Azure Update Manager related development tasks. Not for Azure Automation (use azure-automation), Azure Policy (use azure-policy), Azure Monitor (use azure-monitor), Azure Site Recovery (use azure-site-recovery).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Sentinel development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring data connectors, KQL analytics rules, Logic Apps playbooks, data lake jobs, or SAP integration, and other Azure Sentinel related development tasks. Not for Azure Defender For Cloud (use azure-defender-for-cloud), Azure Security (use azure-security), Azure Monitor (use azure-monitor), Azure External Attack Surface Management (use azure-external-attack-surface-management).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Resource Graph development including troubleshooting, best practices, decision making, limits & quotas, configuration, and integrations & coding patterns. Use when querying via CLI/PowerShell/REST, using GET/LIST vs Query, handling paging/quotas, or Power BI ARG reports, and other Azure Resource Graph related development tasks. Not for Azure Monitor (use azure-monitor), Azure Policy (use azure-policy), Cost Management (use azure-cost-management), Azure Resource Manager (use azure-resource-manager).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Service Health development including troubleshooting, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when handling Service Health APIs, Resource Graph queries, webhooks, VM Resource Health, or retirement alerts, and other Azure Service Health related development tasks. Not for Azure Monitor (use azure-monitor), Azure Reliability (use azure-reliability), Azure Resiliency (use azure-resiliency).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Reliability development including best practices, decision making, architecture & design patterns, limits & quotas, and deployment. Use when choosing Azure regions, availability zones, geo-paired deployments, Queue Storage limits, or Web PubSub apps, and other Azure Reliability related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Service Health (use azure-service-health), Azure Sre Agent (use azure-sre-agent).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Quotas development including limits & quotas. Use when requesting per-region Storage account quota increases, checking limits, or filing Azure support requests, and other Azure Quotas related development tasks. Not for Azure Cost Management (use azure-cost-management), Azure Monitor (use azure-monitor), Azure Policy (use azure-policy), Azure Resource Manager (use azure-resource-manager).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Sre Agent development including troubleshooting, best practices, decision making, architecture & design patterns, security, configuration, integrations & coding patterns, and deployment. Use when wiring SRE Agent to DevOps/GitHub, KQL telemetry, AKS Java apps, IaC deployments, or DR architectures, and other Azure Sre Agent related development tasks. Not for Azure Monitor (use azure-monitor), Azure Reliability (use azure-reliability), Azure Resiliency (use azure-resiliency), Azure Service Health (use azure-service-health).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Microsoft Opentelemetry development including configuration. Use when setting sampling, exporters, resource attributes, env vars, or tuning tracing/metrics behavior, and other Azure Microsoft Opentelemetry related development tasks. Not for Azure Monitor (use azure-monitor).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Microsoft Discovery development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building Discovery shared sessions, Bookshelf indexes, secure RBAC/CMK setups, REST jobs, or Docker-based tools, and other Azure Microsoft Discovery related development tasks. Not for Azure Portal (use azure-portal), Azure Resource Graph (use azure-resource-graph), Azure Monitor (use azure-monitor), Azure Cost Management (use azure-cost-management).
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure AI Metrics Advisor development including decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when configuring data feeds, tuning anomaly detection, managing alerts/hooks, or calling Metrics Advisor REST/SDKs, and other Azure AI Metrics Advisor related development tasks. Not for Azure AI Anomaly Detector (use azure-anomaly-detector), Azure Monitor (use azure-monitor), Azure Stream Analytics (use azure-stream-analytics).
日本語の概要は準備中です。原文の説明を表示しています。