「inspector」の検索結果

Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.

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

Keeps CopilotKit docs pointing at shipped Inspector panes so readers open the overlay. Use when adding, changing, renaming, or removing an Inspector pane, tab, or overlay action in @copilotkit/web-inspector, or when editing docs that mention Inspector. Don't use for Inspector UI polish that does not add a pane, for CLI or agent-prompt copy, or for unshipped Inspector ideas.

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

Create or repair a project-local Inspector profile after INSPECTOR_PROFILE_REQUIRED, INSPECTOR_PROFILE_INCOMPLETE, INSPECTOR_PROFILE_INVALID, or PROFILE_AUTHORING_REQUIRED, using Unity component source, custom Inspector evidence, serialized surfaces, and validation diagnostics.

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

Use when working with Aws Inspector — aWS Inspector vulnerability management and finding analysis. Covers Inspector v2 coverage, vulnerability findings, finding summaries, scan configurations, suppression rules, and coverage statistics. Use when auditing vulnerability posture, reviewing Inspector findings, checking scan coverage, or analyzing security vulnerabilities across EC2, ECR, and Lambda resources.

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

Use when analyzing how Plugin Inspector rule, warning, deprecation, or compatibility changes affect the ClawHub plugin corpus. Guides agents to export plugins from ClawHub, run `plugin-inspector batch`, and summarize affected plugins and finding frequency.

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

Set up MCP Inspector for debugging and testing MCP servers with request logging, response inspection, and protocol validation.

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

App Store プレビュー動画を Remotion (React) で生成する Agent Team スキル。 video-director が構成を設計し、script-writer がナレーション台本を作成し、 motion-designer が Remotion コードを実装し、preview-reviewer がコードレビューし、 frame-inspector がレンダリング結果を目視検証する。 Use when: App Store プレビュー動画を作りたい、アプリのプロモーション動画を作りたい、 Remotion で動画を生成したい。 Triggers: "プレビュー動画", "App Store 動画", "アプリ動画", "preview movie", "Remotion", "動画作成", "app preview"

Generate custom editor tooling including Custom Inspectors, PropertyDrawers, EditorWindows, Gizmos, and Handles. Use when building designer-facing tools, spatial visualization, batch operations, or custom component UIs. Triggers on requests like "create a custom inspector", "add gizmos", "build an editor window", "make this component designer-friendly", "add a debug visualization", "create a level editor tool", "add a property drawer", "make a batch rename tool", or any editor tooling work. Always uses SerializedProperty and Undo for safety.

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

Use when a task needs the judgment of an Environmental Compliance Inspector — reviewing discharge monitoring reports or emissions data against permit limits, classifying a facility's hazardous waste generator status, calculating a penalty for a documented violation, deciding whether an exceedance warrants a Notice of Violation versus informal correction, or scoping a multimedia (air/water/waste) inspection.

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

Use when a task needs the judgment of a Construction and Building Inspector — deciding whether a phase of work passes a hold-point inspection (foundation, framing, rough-in, insulation, final) or gets red-tagged, writing a correction notice that will hold up on appeal, resolving a conflict between the approved plans and field conditions, applying a specific IRC/IBC section to a borderline condition (egress, smoke/CO detector placement, GFCI/AFCI locations), or deciding whether schedule pressure from a contractor changes the call.

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

Use when a task needs the judgment of a Cargo Inspector — reconciling a vessel draft survey against a shore tally within IMO tolerance, calculating outturn quantity from tank ullage and temperature readings under API MPMS, verifying dangerous-goods segregation against the IMDG Code, checking a load's height and width against a route's bridge and tunnel clearances before departure, or documenting cargo condition and filing a letter of protest before custody transfers.

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

Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs. civil penalty vs. certificate action), auditing a Safety Management System for a functioning safety-assurance loop rather than paperwork completeness, scoping a records-sampling strategy across a fleet under surveillance, or deciding whether to ground an aircraft pending an AD compliance finding.

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

Use when a task needs the judgment of an Agricultural Inspector — grading a lot of produce against a USDA grade standard's defect tolerances, evaluating agricultural water test results against FSMA microbial thresholds, checking a pesticide residue result against the commodity-specific EPA tolerance, deciding whether a finding warrants a stop-sale order versus a corrective-action letter, or verifying a facility's traceability records against a recall deadline.

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

Design desktop window systems that feel native on macOS and Windows: split views, inspectors, auxiliary windows, tiling, snap-safe sizes, default placement, and chrome density. Use when a Tauri/Electron/WinUI/SwiftUI app feels awkward, overlapping, over-chromed, or generic, or when you need a real geometry contract for multiple surfaces. NOT for mobile layouts, marketing pages, or CSS-only component styling without multi-window or multi-pane behavior.

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

Use when designing, reviewing, or implementing an Inspector panel for an Apple-platform app — contextual selected-item details and safe editable properties, grouped sections, ⌘I toggle, and a compact-width fallback.

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

在授权测试中核验 Node.js 权限模型（--permission / --experimental-permission，及旧 policy.json）能否被内部 API 绕过。当目标依赖 Node.js Permission Model 做沙箱隔离、需要判断给定 Node 版本下是否存在已知逃逸（inspector 断点、process.binding、fs.statfs/openAsBlob、process.mainModule.require、Module._load、path.resolve 覆盖、Uint8Array 路径、符号链接重命名）时使用。适用目标类型 Node.js 运行时 / 依赖权限模型的服务或 CLI。触发场景包括用户说"这个 Node 权限模型靠谱吗""--permission 能被绕过吗""测下 policy.json 沙箱逃逸""inspector/process.binding 能突破权限吗"。输出：给定 Node 版本下各绕过原语的命中矩阵 + 建议升级版本（含 killed 记录）。

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

Use this skill to understand the value and limits of CVSA decals. Covers when they apply, what they signal, and inspector discretion.

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

Design desktop window systems that feel native on macOS and Windows: split views, inspectors, auxiliary windows, tiling, snap-safe sizes, default placement, and chrome density. Use when a Tauri/Electron/WinUI/SwiftUI app feels awkward, overlapping, over-chromed, or generic, or when you need a real geometry contract for multiple surfaces. NOT for mobile layouts, marketing pages, or CSS-only component styling without multi-window or multi-pane behavior.

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

Converts neuroscience acquisition data to Neurodata Without Borders files with NeuroConv and PyNWB, preserves metadata and timebases, checks evidence-based clock alignment, and produces schema validation, NWB Inspector findings and round-trip checks. Use for NWB conversion and synchronization of planar single-channel two-photon TIFF imaging plus timestamped behavioral position CSV; this skill does not perform spike sorting or claim tested support for arbitrary acquisition formats.

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

Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing snippets/shared/intelligence/overview.mdx. Don't use for OSS-only frontend docs, Inspector pane callouts, or marketing-site copy.

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

Review AI agent skills before installation using NVIDIA SkillSpector and source-aware semantic review. Use when asked whether a skill or downloaded skill folder is safe, trustworthy, installable, over-permissioned, or malicious.

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

Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include "add devtools", "debug json-render", "inspect the spec", "why is this element not rendering", "see the state at runtime", or requests to tap streams / capture action logs for `@json-render/devtools`.

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

Vue adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-vue in a Vue json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.

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

SolidJS adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-solid in a SolidJS json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.

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