9,487 件 ・ 関連度順
Use when a task needs the judgment of a dermatologist — triaging a pigmented lesion for melanoma risk, choosing a biopsy technique and reading the pathology in clinical context, staging a skin cancer to decide margins or Mohs referral, escalating psoriasis/eczema treatment by severity score, or managing isotretinoin risk under REMS/iPLEDGE rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Data Engineer — designing an idempotent pipeline operation so retries and backfills don't corrupt data, choosing event-time over processing-time partitioning for time-series aggregation, enforcing schema compatibility rules before an upstream change propagates downstream, adding automated data quality checks to a pipeline, or deciding between batch and streaming architecture for a specific freshness requirement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a dispensing optician — translating a written prescription into a fitted pair of glasses, resolving frame/lens material tradeoffs, diagnosing why a finished pair doesn't feel or see right, or deciding whether a fit problem is remake, adjustment, or patient-adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a demographer — building a cohort-component population projection, reconciling fertility/mortality rate estimates against ACS or vital-statistics counts, judging whether a population trend is real or sampling/measurement noise, sizing a census undercount adjustment, or advising a public agency on age-structure-driven facility or service demand.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Dispatcher — assigning a new job to the best available driver/technician in real time, managing an ETA slip and deciding who to notify, triaging a coverage gap in a service territory, sequencing a driver's remaining stops after a delay, or deciding whether a job needs to be reassigned versus the customer rescheduled.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Construction Trades Supervisor (foreman) — allocating a crew's daily task assignments against a labor-unit budget, deciding whether today's scope requires a formally designated OSHA competent person, arbitrating a trade-sequencing conflict between crews needing the same physical space, tracking crew productivity variance before it shows up on the master schedule, or logging and acting on a near-miss.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Childcare Worker — checking ratio/headcount compliance across mixed-age groups, deciding whether a fall or minor incident needs a written report versus a verbal mention at pickup, redirecting a behavior problem in an unstructured (non-curriculum) setting, or triaging which of several simultaneous demands (a crying toddler, a fight over a toy, a diaper) gets attention first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Intelligence Analyst — reconciling a metric discrepancy between reports, designing a dimensional model or semantic layer for self-service dashboards, setting a data freshness/latency SLA, or diagnosing why a dashboard's aggregate number is misleading.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an astronomer — calculating exposure time or signal-to-noise for a target, writing the feasibility math for a telescope-time proposal, reducing photometric or spectroscopic data, distinguishing a systematic error floor from statistical noise, or reviewing an observational result for calibration or upper-limit red flags.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an agricultural engineer — sizing a center-pivot or drip irrigation system's peak capacity against crop water demand, computing lateral grain-bin wall pressure with Janssen's equation, sizing a waterway or tile-drainage system with Manning's equation and an NRCS design-storm return period, or building a manure/nutrient first-year availability mass balance against a crop's N requirement.
日本語の概要は準備中です。原文の説明を表示しています。
Validate SEO preservation during site migrations. Checks redirect chains (301 vs 302, hop count), canonical consistency, title/meta preservation, HTTP status codes, content similarity, and schema preservation. Accepts single URL pair or CSV file of URL pairs. Use when user says "migration check", "site migration", "redirect audit", "URL mapping", "domain change", "relaunch", "site move".
日本語の概要は準備中です。原文の説明を表示しています。
Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", "X vs Y", "alternatives page", "versus page", "comparison matrix", or "feature comparison".
日本語の概要は準備中です。原文の説明を表示しています。
Per-type rich result eligibility checker. Given a URL or page type, determine WHICH Google rich results the page is eligible for, validate existing JSON-LD against Google's required/recommended properties per type, and produce a gap report. Use when user says "rich results", "rich snippets", "eligible rich results", "structured data types", or "schema eligibility".
日本語の概要は準備中です。原文の説明を表示しています。
Build an Obsidian knowledge base from a sitemap — bulk-fetch pages via Python, generate Obsidian-optimized MD notes with parallel agents
日本語の概要は準備中です。原文の説明を表示しています。
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Enhanced with live Ahrefs (page authority, referring domains) and GSC (search performance, top keywords) data when MCPs are available. Use when user says "analyze this page", "check page SEO", or provides a single URL for review.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews JUCE audio plugin code for JUCE-specific correctness issues: thread safety, APVTS parameter patterns, MessageManager usage, ValueTree, and MIDI handling. Use when the user asks to review a JUCE plugin, check a processBlock, audit parameter handling, or asks "is this JUCE code safe?". Trigger on phrases like "review my JUCE plugin", "check my AudioProcessor", "is this APVTS usage correct?", or when you see AudioProcessor, AudioProcessorEditor, or AudioProcessorValueTreeState in the code.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic checklist for diagnosing audio artifacts. Use when the user describes a sound quality problem — clicks, pops, crackling, silence, DC offset, aliasing, phase issues, or latency problems. Trigger on phrases like "why do I hear clicks?", "my output has DC offset", "there's aliasing in my oscillator", "phase is wrong in mono", "dropout when CPU spikes". Pairs with audio-dsp-review (realtime safety) and audio-numerics-review (numeric correctness) — use those to fix once the cause is found.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing mathematical, logical, algorithmic, or technical proof from its stated conclusion backward as a bounded AND/OR graph of exact obligations. Use to reconstruct conclusion dependencies, determine whether a proof-supplied route establishes the conclusion, or expose hidden assumptions, unmet side conditions, cycles, overly strong steps, or silent route switches. For a source-mapped Lamport rendering use convert-lamport, and for forward hierarchy, construct, and scope conformance use forward-lamport before this skill. This does not decide full theorem-level entailment by searching for a different proof; do not turn the audit into a linear reversed proof, exhaustive proof search, or replacement proof.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Lamport-style hierarchical mathematical proof forward for validity and whether its hierarchy, scope, dependencies, side conditions, and proof constructs discharge the stated theorem. Use when the central question concerns a top-down proof with numbered levels, subproofs, ASSUME/PROVE, SUFFICES, PICK, CASE, DEFINE, Q.E.D., or prose equivalents. For an ordinary proof that first needs source-preserving hierarchy, use convert-lamport; for conclusion-first AND/OR obligation reconstruction, use reverse-lamport. Do not use to generate or replace a proof, or to audit Lean, Coq, Isabelle, or other proof-assistant source.
日本語の概要は準備中です。原文の説明を表示しています。
Generate accurate Volcengine SDK examples by locating an API through API Explorer search, fetching its swagger, and calling api/common/explorer/make-code with user-provided Params. Use when the user asks how to write Volcengine SDK code, generate SDK samples, or call a Volcengine API in Python, Go, Java, PHP, cURL, Node.js. Supports Chinese and English API names such as "角色扮演", "AssumeRole", or "STS AssumeRole". Also use for explicit SDK configuration questions about retry, timeout, AK/SK, STS, AssumeRole, temporary credentials, proxy, connection pooling, SSL, debug mode, request signing, response parsing, and error handling. If the user only needs API parameters, enum values, required fields, error codes, response schemas, pagination, or API comparisons, hand off to volcengine-api. If they need CLI-based operations, hand off to volcengine-cli.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Volcengine's AI-native BaaS platform (Supabase edition / AIDAP / 火山引擎 AI 原生 BaaS 平台 Supabase 版) — a Volcengine-operated distribution that differs from official Supabase. Use when the user asks to create, inspect, or manage Volcengine Supabase or AIDAP resources — workspaces, branches, computes, SQL queries, schema changes, Auth, Realtime, Edge Functions, Storage buckets, frontend static-site hosting (Pages), API keys, connection info, or TypeScript type generation — or when a Volcengine deployment selects AIDAP as its database provider. Also trigger on Chinese prompts mentioning "火山引擎 Supabase" or "火山 Supabase". Operations run through the byted-supabase-cli command-line tool (installed via `npm i -g @byted-supabase/cli`; this is NOT the official `supabase` CLI). Do NOT use it for general database discussions, non-Supabase services (RDS MySQL, Redis), or pure client-side coding unrelated to Supabase backend management.
日本語の概要は準備中です。原文の説明を表示しています。
对画像系统的维度结构进行增加、删除或修改。当用户需要新增一个画像维度、删除某个维度、或修改某个维度的字段定义时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Automate version bumping following semantic versioning and changelog management. Use when the user wants to bump a version, create a release, update the changelog, or tag a new version in a project using semver conventions and Keep a Changelog format.
日本語の概要は準備中です。原文の説明を表示しています。