「auditing」の検索結果

Use when a task needs the judgment of a Nutrition and Dietetics Technician, Registered (NDTR/DTR) — translating a physician's diet order into a texture/therapeutic tray specification, triaging a nutrition-screening or intake-decline signal for RDN escalation, auditing a tray line or food-safety log against a threshold, or drawing the line between routine dietetics work and a nutrition-diagnosis call that belongs to the supervising RDN.

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

Use when a task needs the judgment of a Compensation and Benefits Manager — designing or evaluating a pay structure/leveling system, benchmarking compensation against market, deciding on a benefits package tradeoff, or auditing for pay equity issues. Narrower and more specialized than the broader hr-people-manager role's compensation-adjacent heuristics.

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

Use when a task needs the judgment of a Correspondence Clerk — selecting and customizing a template response to a standardized written inquiry, triaging a correspondence queue against SLA deadlines, deciding when a form letter suffices versus needs escalation, or auditing a response-template library for staleness.

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

Use when a task needs the judgment of a Chief Data Officer — resolving conflicting metric definitions across dashboards, deciding whether a dataset should be retained or purged, assigning data ownership for a system feeding regulatory or board reporting, sizing a privacy/breach risk against a proposed data collection, or auditing data readiness before an AI/ML initiative kicks off.

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

Use when a task needs the judgment of a Blockchain Engineer — applying the checks-effects-interactions pattern to prevent a reentrancy exploit, auditing a privileged/administrative function for missing access control, designing a manipulation-resistant oracle for on-chain price data, minimizing gas cost through storage-write design, or deciding whether a smart contract needs an upgradability pattern before deployment.

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

Use when a task needs the judgment of a Biological Technician — troubleshooting a failed assay or contaminated culture, deciding whether a batch of lab data is trustworthy enough to report, auditing a bench's SOP/QC discipline, or diagnosing calibration and reagent-lot problems behind inconsistent results.

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

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 a Bookkeeping, Accounting, and Auditing Clerk — reconciling a bank or credit card account, resolving an AP three-way-match discrepancy before payment, coding an expense to the correct account and department, tracing a general ledger discrepancy to root cause, or running a month-end close checklist.

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

Spring Boot 4 data layer implementation for Domain-Driven Design. Use when implementing JPA or JDBC aggregates, Spring Data repositories, transactional services, projections, or entity auditing. Covers aggregate roots with AbstractAggregateRoot, value object mapping, EntityGraph for N+1 prevention, and Spring Boot 4 specifics (JSpecify null-safety, AOT repositories). For DDD concepts and design decisions, see the domain-driven-design skill.

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

Design backup strategies that survive real disasters: 3-2-1 rule, versioning, testing restores, and covering all devices. Use when setting up backups or auditing whether current backups actually work.

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

Audit patient-facing healthcare software for portal feature completeness, secure messaging, health literacy, telehealth readiness, consent management, and HIPAA compliance. Triggers: evaluating a patient portal, checking PHI exposure in notifications, auditing telehealth flows.

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

Audit feature specs against India's Digital Personal Data Protection (DPDP) Act. Use this skill when: - Writing or reviewing any feature that handles user data (especially children's data) - Auditing a spec's Personal Information section for completeness - Checking a feature against DPDP Act 2023 requirements - Preparing compliance documentation before engineering review - Verifying masking, retention, and consent policies are defined for all PII

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

Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why an SEO effort stalled despite consistent output. NOT for writing an article, keyword expansion mechanics, or auditing a single tactic for penalty risk.

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

Maps intelligence for local SEO: geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification, competitor radius mapping, and LocalBusiness schema generation. Three tiers: free (Overpass + Geoapify), DataForSEO, and DataForSEO + Google. Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", or "SoLV".

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

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill, audit this skill, is this skill safe, vet a skill before installing, what does this skill access. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, spec validation, and security auditing of third-party skills before install.

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

Use this skill when designing, generating an MVP blueprint for, auditing, troubleshooting, refactoring, or explaining an agentic harness for any domain. Covers provider-neutral agent architecture for OpenAI, Anthropic, and OpenAI-compatible APIs: agent loops, tool design, record provenance, interactive presentation, user-memory lifecycles, environment-adaptive tools, speculative tool execution, late-bound capabilities, permissions, system prompts, planning, goals, always-on agents and durable runtime, adaptive agent teams, context compaction, memory, skills, MCP/external connectors, public-board communications, hardware agents and board deployment, self-refining recursive harnesses, programmable context, continual refinement, observability, evals, prompt caching, agent-legible environments, feedback loops, and safety.

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

Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.

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

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (`audit_cluster.sh`), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod Security Standards (`restricted` labeling), and mounting Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing cluster security posture, isolating namespaces, applying pod security standards, setting up Workload Identity, or configuring network policies and secret volume mounts. Don't use for cluster-wide control plane security, RBAC hardening, Binary Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security instead).

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

Diagnoses and resolves Google Cloud Filestore client mount failures, permission errors (EACCES), and network timeouts (ETIMEDOUT). Use when an NFS mount hangs or fails from a Compute Engine VM, GKE pod, Cloud Run service, or Vertex AI workload, when `mount.nfs` reports "Connection timed out" or "access denied by server", when checking whether VPC ingress firewall rules or `nfsExportOptions` allow a client IP, or when a previously working Filestore share suddenly stops mounting after an administrative change. Don't use for Cloud Storage (GCS) buckets, Persistent Disk, or Cloud NetApp Volumes, and don't use for Filestore capacity scaling or backup and export-policy auditing.

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

Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing node taints, or configuring workload protection strategies (graceful termination, opportunistic maintenance, PodDisruptionBudgets). Don't use for general GKE cluster creation, network policy configuration, or non-disruption workload deployment.

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

Plans and executes GKE cluster creation, provisioning, and production readiness audits using pre-defined templates (Autopilot, Standard Regional, GPU/AI Inference, AI Hypercompute). Use when creating GKE clusters, provisioning GKE environments, selecting cluster modes, or auditing GKE clusters. Don't use for application onboarding or deployment configuration (use gke-app-onboarding instead).

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

Provides data-retrieval best practices, tool selection guidance, and performant SQL query syntax for BigQuery telemetry across INFORMATION_SCHEMA, Cloud Monitoring, and the REST API. Use when the telemetry to fetch is already known, selecting telemetry tools, writing performant INFORMATION_SCHEMA queries, retrieving telemetry for diagnosing single-job performance bottlenecks, investigating slot contention, job concurrency and queue latency, analyzing reservation capacity, utilization and autoscaling saturation, or auditing capacity-based and on-demand compute and storage resource billable usage. Don't use for root-cause diagnosis or symptom troubleshooting when the cause is unknown (use bigquery-troubleshooting first), or for writing or optimizing business logic SQL (use bigquery-optimization).

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

Use when creating, configuring, auditing, or troubleshooting an Agentforce agent end-to-end: agent definition, agent user setup, channel assignment, system instructions, activation, and lifecycle management. Triggers: 'create agentforce agent', 'agent not appearing to users', 'how to activate agent', 'agent channel setup', 'agent lifecycle', 'deploy agent to production'. NOT for designing what the agent can DO — an agent that looks up an order, checks a case, or creates a record is action design, use agentforce/agent-actions. NOT for topic boundary design — use agentforce/agent-topic-design.

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

Use when writing, auditing, or troubleshooting Salesforce Validation Rules. Triggers: 'validation rule', 'required field formula', 'rule fires unexpectedly', 'integration failing validation', 'data quality', 'errorConditionFormula', 'errorDisplayField', 'errorMessage 255 characters', 'ValidationRule metadata', 'validationRule-meta.xml', 'deploy validation rule inactive', 'bypass custom permission', 'FIELD_CUSTOM_VALIDATION_EXCEPTION', 'validation rule on custom metadata type', 'compound field validation rule', 'require at least one child record before a stage', 'HasOpportunityLineItem'. NOT for Flow-based validation — use admin/flow-for-admins for that.

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