「check」の検索結果

Inspects and visualises a ROS-2-enabled CARLA server from Docker containers, with no local ROS 2 install — list/echo/rate-check topics (the "are the topics actually on the wire" check), run the bundled map-and-lidar demo stack (hero vehicle with camera/lidar/GNSS/IMU on autopilot), and open RViz2 with the lane-network preset. Use when the user asks to "check the ROS topics", "echo /carla/map", "is CARLA publishing to ROS", "visualise the lidar in RViz", "open rviz", or "run the ROS 2 demo".

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

Pre-production security checklist for Agentforce deployments: permission scope, data exposure, authentication, logging. NOT for general Salesforce security review (see security-health-check).

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

Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"

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

Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check.

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

[Design System] Quantitative accessibility audit for UI - contrast ratios, font sizes, tap targets, heading hierarchy. Use when (1) checking WCAG color contrast compliance, (2) auditing text sizes for readability, (3) validating touch/click target sizes, (4) reviewing heading structure and landmarks, (5) user asks to 'check accessibility', 'audit contrast', 'WCAG compliance', or 'a11y check'.

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

Self-review, audit, or verify CS/AI/ML paper drafts as a critical peer reviewer. Three-round review (evidence→argument→style) with Verification Status and debt tracking. Use when: reviewing a paper draft before submission, checking evidence compliance of claims, simulating peer reviewer feedback, verifying citation closure and evidence debts, performing cross-section consistency checks. Triggers on: 审修, self review, 自查, verification, revise, 修订, check draft, 审稿, evidence compliance, peer review, 论文审查, draft audit, 验证论文, 检查引用, cross-section review.

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

This skill should be used when the user asks for an accessibility review, accessibility audit, a11y check, WCAG compliance review, screen reader audit, "is this accessible?", "does my site meet WCAG?", "check my component for accessibility", "accessibility overview of this page", "review accessibility of", "check for a11y issues", "fix accessibility issues", or any request to audit a web page, component, or codebase for WCAG 2.2 AA compliance.

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

Execute Abridge production readiness checklist for clinical AI deployment. Use when launching Abridge in a healthcare org, preparing for go-live, or validating HIPAA compliance before production deployment. Trigger: "abridge production checklist", "abridge go-live", "abridge launch readiness", "abridge prod deploy".

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

Build kokoro-js-jp and run its real-browser e2e suite (Worker + WASM openjtalkjs g2p + ONNX kokoro-js synthesis, English and Japanese). Use when asked to verify this package actually works in a browser, to check whether a change broke synthesis, or to add browser-level regression coverage for a bug in the g2p/synthesis pipeline that vitest's pure-function tests can't catch. Not for typecheck/lint/unit-test requests — use npm run typecheck / npm test for those.

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

タスク進行中に、続行・即出荷・方向転換のどれが妥当かを、fresh なサブエージェント1体に状況サマリだけ渡して裁定させる。/gal-check 実行時、「ずれてない？」「このまま続けていい？」「ギャルに聞いて」等の方向確認の依頼時、外部レビューループの打ち切り条件に達した時に使用。成果物の中身は読まない。境界: 成果物のレビューは pr-review、計画の穴の対話検証は grilling。

研究概要・中間発表予稿の「当てどころの深さ」を評価し、より深い框(フレーム)への付け替えを提案するスキル。鎖が繋がっているか(→framing-check)ではなく、狙いが浅くないか(道具の実装で終わっていないか)・題材固有の強みを活かしてもっと深い研究課題に貼り替えられるかを見る。深い框が実在するときだけ提案し、無ければ黙る。研究の面白さ・野心・当てどころ・框の付け替えを見てほしい、と言われたとき、または research-review から内部呼び出しされる。教員向け(率直・野心を上げてよい)。

論文・研究概要の体裁・形式を自動チェック。LaTeX(.tex)・Word(.docx)・PDF(.pdf)に対応。表記ゆれ・参考文献体裁・相互参照整合性・未記入セクション等を検出。1〜2ページの概要・梗概・アブストラクト（固定尺）は --fixed（またはページ数で自動判定）で紙面配分（参考文献が本文を圧迫していないか等）も診断する。提出直前の最終確認に使用。卒論・研究論文・学会投稿論文・研究概要すべてに対応。旧 abstract-format-check を統合。

Detect articulation gaps in documents using 5W analysis and provide concrete improvement suggestions. Identifies what's missing in explanation, not what's wrong. Default runs detection + improvement; use --check-only for detection only. 旧名 check-articulation。

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

Read a liarjs fingerprint report and attribute each failing check to the component that produced it - what the check id measures, whether the signal comes from the launch configuration, the page-modifying layer, the network path or the machine image, and which failures are inherent to headless or datacenter environments. Use when a fingerprint scan came back with a low score, or when a check id such as webdriver, worker-consistency, gpu-triad, native-integrity or tz needs explaining.

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

Read-only sanity-check of EcoSIM plant_trait.*.desc parameter values for the first grid. Use when validating plant trait description files, enforcing clean C3/C4 physiological parameterization, reviewing photosynthetic kinetics, active leaf/root protein allocation, and root hydraulics such as RSRR, RVSR, and ARSRA, or checking ranges, units, and woody/herbaceous block consistency before running EcoSIM. Never edit or replace the `.desc` file.

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

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)

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

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

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

Detect and resolve naming collisions, overlapping intent triggers, and insufficient intent diversity across the skill library. Load when a new skill is created (called by universal-skill-creator), during improvement passes (called by improve-skills), or when the user asks to deconflict skills, check for naming collisions, audit trigger overlap, review intent coverage, find duplicate triggers, check skill names, or says "are any skills too similar", "which skills overlap", "deconflict the library", "check for confusing skill names", "intent audit".

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

Security checks for repository ingestion — scans repos for poisoned examples, dependency and supply-chain attacks, file/path traversal, format-based attacks, and enforces quarantine-before-commit. Load as part of the secure-* skill sequence whenever an agent reads, ingests, or learns from a GitHub repository. Also load when the user asks to check a repo for poisoned code, scan dependencies, verify supply chain safety, check for path traversal, scan repo files for attacks, or audit a repo before ingestion. Covers Issues 3, 4, 7, 8 from the agent security threat model: poisoned training data, dependency attacks, file/path attacks, and format-based attacks.

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

Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.

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

Validates agent outputs against schemas and quality criteria, scores confidence, detects hallucinations, monitors convergence, decides when to iterate, and synthesizes actionable feedback. Use when checking if a node's output is acceptable, scoring confidence, detecting fabricated content, deciding whether to re-execute, or generating improvement feedback. Activate on "validate output", "check quality", "confidence score", "hallucination check", "should we iterate", "improvement feedback". NOT for executing DAGs (use dag-runtime), planning DAGs (use dag-planner), or matching skills (use dag-skills-matcher).

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

Performs claim-evidence verification for agent outputs, recording supported, contradicted, or insufficient-evidence results alongside source accessibility. Activate on 'detect hallucination', 'fact check', 'verify claims', 'check accuracy', 'find fabrications'. NOT for validation (use dag-output-validator) or confidence scoring (use dag-confidence-scorer).

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

Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.

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

Design and implement systematic checklists that reduce errors by 30-50% in complex, high-stakes domains (medicine, aviation, construction, finance). NOT for simple tasks or when comprehensive instruction is needed.

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