「indicator」の検索結果

Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.

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

Malware reverse engineering and suspicious artifact analysis skill for defensive triage, static analysis, dynamic analysis planning, unpacking strategy, indicators of compromise, behavior summaries, YARA/Sigma ideas, and remediation guidance. Use for suspicious binaries, scripts, documents, logs, memory artifacts, sandbox reports, and malware family analysis in isolated environments.

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

Use when a task needs the judgment of an eligibility interviewer for government benefit programs — calculating household income against a means-tested program's limits, determining household composition for benefit purposes, judging whether submitted verification documents are sufficient, or distinguishing a documentation gap from a fraud indicator.

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

Use when a task needs the judgment of a dental assistant — sequencing instrument transfer during a procedure, troubleshooting a retake-worthy radiograph before re-exposing the patient, tracing a failed sterilization-cycle indicator back to the affected instrument batches, or timing a chairside material mix against its working-time window across multiple prepped teeth.

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

Spring Boot 4 observability with Actuator, Micrometer, and OpenTelemetry. Use when configuring health indicators, health checks, custom metrics, distributed tracing, production endpoint exposure, Kubernetes probes, Cloud Run probes, logging, or monitoring. Covers Actuator endpoint security, Micrometer Timer/Counter/Gauge patterns, OpenTelemetry span customization, liveness/readiness probe setup, and metric tag best practices.

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

Comprehensive K-12 or higher-ed system analysis: predict student dropout risk with early warning indicators, optimize curriculum alignment and pacing, personalize learning paths for at-risk and diverse populations, and audit school operations for resource efficiency..

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

Audit rehabilitation setback prediction systems for clinical risk modeling and early intervention. Triggers: you need to evaluate risk factor models (Charlson, Elixhauser), early warning indicators for functional decline.

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

Audit a mineral resource estimation system -- evaluate drillhole database integrity and QA/QC (CRMs, blanks, duplicates, umpire checks), geological and domain modeling quality, variogram analysis and grade interpolation methods (ordinary kriging, indicator kriging, IDW.

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

Audit a real estate analytics platform -- evaluate comparable sales and rental engines, automated valuation models (AVM), demographic and economic indicator pipelines, submarket scoring, gentrification detection, price forecasting accuracy, market cycle analysis, and risk modeling.

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

Analyze program impact measurement software for logic model completeness, indicator tracking rigor, data collection methodology, causal attribution modeling, cost-effectiveness analysis, beneficiary feedback integration, and funder reporting accuracy..

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

Analyze a workplace safety incident tracking system for incident classification accuracy, root cause analysis depth, OSHA 300 log recordkeeping compliance, trend analysis capabilities, and leading indicator identification..

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

Audit a student information system for dropout risk prediction. Analyzes attendance patterns, grade trajectories, behavioral indicators, early warning model accuracy, intervention tracking, equity in risk scoring, and socioeconomic factor integration..

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

Analyze flow metrics to identify delivery bottlenecks and improve throughput. Use when the user says "flow metrics", "why is delivery slow", "cycle time analysis", "WIP analysis", "throughput review", "what's our lead time", "DORA metrics", "where is work getting stuck", "Kanban metrics", or wants to diagnose delivery performance using data - even if they don't explicitly say "flow metrics review". Based on "Making Work Visible" by Dominica DeGrandis (WIP limits, flow blockers, time thieves) and "Accelerate" by Forsgren, Humble & Kim (DORA metrics, delivery performance indicators).

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

Expert guidance for proactive threat hunting in Google SecOps. Use when proactively hunting for threats, retroactively analyzing indicators of compromise (IoCs), performing prevalence searches across enterprise events, hunting for MITRE ATT&CK techniques, or detecting behavioral and statistical outliers using UDM queries. Don't use for incoming alert triage (use secops-triage), active incident response and timeline deep-dives on a known breach (use secops-investigate), or detection rule authoring (use secops-detection-engineering).

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

Design guidance for program outcome measurement in Salesforce nonprofit orgs: logic model structure, indicator taxonomy, impact reporting design, and grant compliance reporting using NPSP Program Management Module (PMM) or Nonprofit Cloud (NPC) Outcome Management. NOT for configuring PMM programs, cohorts and service deliveries - use admin/npsp-program-management. NOT for setting up grant tracking, funding awards and disbursements - use admin/grant-management-setup.

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

Configuring or troubleshooting the Nonprofit Success Pack Program Management Module (PMM) - program delivery, cohort setup, service scheduling, service delivery recording, and attendance tracking for beneficiaries. Trigger keywords: program management module, PMM, Program__c, ProgramEngagement__c, ServiceDelivery__c, cohort setup, bulk service delivery, service schedule, service participant. NOT for designing which outcomes and indicators to measure - use admin/program-outcome-tracking-design. NOT for NPSP donor, household and giving-rollup data - use data/nonprofit-data-architecture.

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

Detects unsafe safe-area overrides and hardcoded inset values that hide content behind the Dynamic Island, notch, or home indicator, violating Apple's Human Interface Guidelines for adaptive layout.

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

Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.

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

Audit designs, color palettes, and UI components for WCAG 2.1 accessibility compliance, providing specific fixes for contrast, touch targets, focus indicators, and screen reader support. NOT for color harmony aesthetics or design system creation.

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

Expert in making CLI tools visually stunning and delightful — not just functional. Covers ANSI color systems (16/256/truecolor with graceful degradation), Unicode box drawing, progress indicators, tables, animated output, ASCII art, rich text, interactive prompts, and full TUI frameworks (Ink, Bubble Tea, Ratatui, Rich, Clack). Activate on: "make this CLI beautiful", "terminal UI", "CLI design", "pretty output", "progress bar", "spinner", "CLI table", "terminal colors", "TUI framework", "interactive prompts", "command line aesthetics", "CLI polish", "terminal styling". NOT for: web UI design (use web-design-expert), GUI desktop apps (use rust-tauri-development), API design (use api-architect), general shell scripting (use devops-expert).

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

This skill determines whether testicular volume should be used as the primary or sole indicator of sexual development in male childhood cancer survivors who have received gonadotoxic treatments such as alkylating agents or testicular radiotherapy. Triggers include clinician questions like “Can I use testicular volume to assess puberty in this male survivor after chemotherapy?” or “Is testis size reliable for sexual maturity evaluation post‑radiation?”

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

Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links. Under no circumstances omit accessible anchor-link requirements when such links exist. Ensure every anchor link has meaningful text, a reachable target, and a visible focus indicator. Apply these rules when creating or reviewing any in-page navigation.

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

Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.

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

Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.

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