「poi」の検索結果

Use when a task needs the judgment of a Crushing/Grinding Machine Operator — recognizing that classifier cut point, not mill residence time alone, determines what reports to finished product in a closed-circuit grinding operation, monitoring circulating load as a distinct diagnostic variable, matching grinding media size to the target size reduction, or verifying product size via actual sieve/laser analysis rather than mill parameters.

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

Use when a task needs the judgment of a credit authorizer, checker, or clerk — deciding a real-time point-of-sale credit authorization against available credit, verifying a credit application's income/employment documentation, issuing an adverse-action notice on a declined application, or intaking a chargeback/dispute within its filing window. Distinct from a credit analyst, who underwrites commercial credit with a multi-year financial spread and a risk rating — this role runs a high-volume rules engine against a preset limit, it does not assess creditworthiness from first principles.

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

Use when a task needs the judgment of a crop, nursery, or greenhouse farmworker — judging harvest timing/ripeness by crop, reconciling piece-rate earnings against the minimum-wage or AEWR floor, deciding whether it's safe to re-enter a pesticide-treated field or greenhouse, managing heat-illness risk during peak-season labor, or running greenhouse IPM scouting and climate setpoint checks.

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

Use when a task needs the judgment of a Document Management Specialist — designing or auditing a records retention schedule, planning a content migration between DMS platforms (SharePoint, OpenText, Documentum, M-Files), reconciling migrated vs. source document counts, resolving a version-control or legal-hold conflict, or scoping a defensible-disposal (ROT) cleanup.

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

Use when a task needs the judgment of a Digital Forensics Analyst — capturing volatile evidence before it's lost, creating and hash-verifying a forensic disk image, documenting chain of custody from point of seizure, correcting for clock skew and timezone mismatches when building a cross-source timeline, or identifying anti-forensic activity (log wiping, timestomping) in an investigation.

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

Use when a task needs the judgment of a Coating/Painting/Spraying Machine Operator — calculating wet film thickness from a target dry film thickness and the coating's percent volume solids, deciding whether flash-off time can be shortened to increase throughput, verifying cure by actual part temperature rather than oven setpoint, or tracing an adhesion failure back to surface prep rather than the coating application.

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

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 Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.

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

Use when a task needs the judgment of a chiropractor — screening a spinal or musculoskeletal complaint for red flags before manipulation, choosing a manipulation technique given a patient's risk profile, designing a care plan with a defined reassessment checkpoint, or deciding whether to continue, modify, or discharge a course of care.

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

Use when a task needs the judgment of a Biomass Plant Technician — adjusting combustion parameters in response to actual measured fuel moisture content rather than a fixed setpoint, diagnosing a fuel feed interruption as mechanical bridging rather than a combustion issue, adjusting soot-blowing frequency to actual observed slagging conditions rather than a fixed calendar schedule, or monitoring emissions more actively given fuel batch variability rather than a "set and monitor occasionally" approach appropriate for consistent fossil fuel.

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

Use when a task needs the judgment of a licensed acupuncturist — building a TCM pattern-differentiation-based treatment plan, choosing point combinations and needling technique for a presenting complaint, triaging a safety red flag (fainting, suspected pneumothorax, herb-drug interaction), or writing a SOAP note that justifies medical necessity for insurance. US scope-of-practice default (NCCAOM/state licensure). A reasoning aid, not medical advice.

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

Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an FEA-predicted margin, selecting and executing an NDI method against a defect type and material, reducing a wind-tunnel test point's dynamic-pressure and Reynolds-number data, or ballooning and dispositioning an AS9102 first article inspection. Distinct from an aerospace-engineer (owns the design, structural analysis, and certification basis) — this role builds, instruments, tests, and inspects the hardware the engineer specified, closing the loop with measurement rather than deriving a new analysis.

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

Use when a task needs the judgment of an Adhesive Bonding Machine Operator — distinguishing an open-time violation from a pot-life check, controlling bond line thickness with calibrated spacers rather than clamping pressure alone, verifying surface prep with a test rather than visual cleanliness, or confirming actual part temperature reached full cure rather than trusting chamber setpoint and elapsed time.

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

Use when a task needs the judgment of an Area, Ethnic, or Cultural Studies Professor — designing a joint-appointment course load across two departments, prepping a tenure or mid-tenure review file for interdisciplinary scholarship, deciding whether a course survives an enrollment or political-pressure threat, evaluating community-engaged research for a merit case, or writing a Title VI/FLAS-adjacent grant narrative.

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

Use when a task needs the judgment of a tenure-track or tenured Agricultural Sciences faculty member at a land-grant university — deciding whether to submit a grant this cycle versus wait, allocating time across the teaching/research/extension appointment split, diagnosing a stalled graduate student or field trial, or drafting a tenure-and-promotion dossier narrative.

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

Use when a task needs the judgment of an Application Security Engineer — checking whether an endpoint verifies object-level authorization (not just authentication), running threat modeling at design time rather than deferring security review to the end, triaging a dependency vulnerability by actual reachability rather than CVSS score alone, combining SAST/DAST/SCA tooling to cover their distinct blind spots, or applying context-specific output encoding to untrusted input. Distinct from an information security analyst — this role works inside the SDLC to prevent vulnerabilities before they ship, not detect and respond to intrusions in production.

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

Spring Security 7 implementation for Spring Boot 4. Use when configuring authentication, authorization, OAuth2/JWT resource servers, method security, or CORS/CSRF. Covers the mandatory Lambda DSL migration, SecurityFilterChain patterns, @PreAuthorize, and password encoding. For testing secured endpoints, see spring-boot-testing skill.

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

Find broken backlinks pointing to a domain using Ahrefs: links targeting 404 pages that can be reclaimed. Prioritizes highest-DR lost links for maximum recovery impact. Use when user says "broken backlinks", "broken links", "link reclamation", "dead backlinks", or "404 backlinks".

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

Flagship comprehensive SEO audit combining Ahrefs and GSC data in sequential waves with checkpoint saves. Use when user says "site audit pro", "full audit", "comprehensive audit", "audit with live data", "deep audit", "pro audit", "complete SEO audit", "run a full site audit", or "audit everything for this domain". Requires domain param. Optional: site param for GSC overlay.

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

Create and manage Volcengine cloud resources using the Volcengine CLI (`ve` command). Supports all Volcengine services including ECS, VPC, CLB, RDS, Redis, and more. Trigger this skill whenever the user asks to create, query, modify, or delete cloud resources on Volcengine, mentions the `ve` command, says "volcengine CLI", or describes infrastructure tasks such as "create an ECS instance", "set up a VPC", "list security groups", "allocate an EIP". Also trigger on Chinese prompts mentioning "火山引擎" or "火山" (e.g., "火山引擎上有哪些 ECS"、"查一下我火山的云服务器"、 "火山引擎创建一个 VPC"、"火山的 Redis 实例列一下"). Also trigger when the user encounters errors from `ve` commands and needs troubleshooting help. Also use for TOS bucket/object operations, tosutil (sometimes written tosutils), Ark CLI / arkcli model discovery, inference, generation, endpoints, fine-tuning, plans, or usage, and TLS (日志服务) / volclog log search, analysis, ingest, export, or LogCollector collection, through `ve tosutil`, `ve arkcli` and `ve volclog`.

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

Generate images via the Stable Diffusion WebUI / Forge HTTP API (AUTOMATIC1111-compatible `/sdapi/v1/*`). Use when the user wants to (1) discover or pick a model / extra module (TE/VAE) / sampler / scheduler / style preset from a running sd-webui server, (2) generate an image with a given prompt (txt2img), (3) check generation progress, (4) cancel/interrupt an in-flight generation, (5) inspect or change a global sd-webui option (e.g. active checkpoint), or (6) test connectivity. This skill talks to a *generic* sd-webui-compatible server (AUTOMATIC1111, Forge, reForge, sd-webui-forge-classic). Do NOT trigger for requests that are purely writing the prompt itself.

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

Invoke a Rubber Duck Reviewer subagent to independently critique plans and implementations before proceeding. Use when the agent is about to implement a non-trivial plan (multi-file changes, architectural decisions, security-sensitive logic, database schema changes), after completing a self-contained unit of work (module, endpoint, feature), when stuck or facing repeated failures (same test fails 2+ times, unexpected results), or when the agent wants independent validation of assumptions and design decisions. Triggers on any non-trivial implementation task where independent critique would catch blind spots before they become costly mistakes.

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

Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and authorization (OAuth2, JWT, API keys, mTLS), (4) configure rate limiting, input validation, or CORS, (5) audit API endpoints for BOLA, BFLA, or mass assignment vulnerabilities, (6) create API security checklists or verification plans, (7) fix API security bugs or harden existing APIs, (8) set up API security testing (OWASP ZAP, Schemathesis, Burp Suite), or (9) handle any API security concern including SSRF prevention, resource consumption limits, business flow protection, API inventory management, and secure third-party API consumption.

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

Prepares Go applications to work effectively with AI coding agents. Use when setting up a new Go project or retrofitting an existing one to ensure: structured JSON logging (slog/Zap/ZeroLog/Logrus), machine-readable command output, thorough golangci-lint configuration, non-interactive CLI design with --yes flags, structured error handling with meaningful exit codes, proper context.Context propagation, graceful shutdown, health check endpoints, and a standardized Makefile. Triggers when a user asks to make their Go app "agent-ready," "AI-friendly," wants to improve agent tooling/observability in a Go project, or needs to audit an existing Go project against agent-readiness best practices.

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