563 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of a Media Technical Director/Manager — calling a live broadcast switcher and owning the technical readiness sign-off, designing router/path redundancy and PTP failover for an IP production, resolving a timecode or loudness compliance defect found in rehearsal, or running the post-incident review after an on-air technical failure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Bioinformatics Scientist — designing a differential-expression or GWAS analysis with correct multiple-testing correction, calling and triaging variants from NGS data using genotype-likelihood confidence rather than raw allele counts, interpreting a BLAST/DIAMOND homology search, choosing or building a genomics pipeline (aligner, caller, normalization method) for a specific data-generating process, or judging whether a computational-biology analysis's statistical design actually supports the biological claim being made. Distinct from a bioinformatics-technician (executes and QC-gates an established pipeline someone else designed) and a data-scientist (general product/experimentation judgment, not genomics-specific statistics) — this role owns which method and statistical model a genomics question requires, and why.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aircraft Cargo Handling Supervisor — verifying a built ULD against its type's certified max gross weight before it's spotted for loading, running a hazmat item through the segregation table against its actual compartment neighbors, reconciling an actual cargo build against the dispatcher's load plan and deciding whether it clears a last-minute-change threshold or needs a reissued loadsheet, calling a ULD's lock/net restraint good or rejecting it, or running ramp FOD and ground-equipment clearance discipline around an aircraft during turn.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Amusement and Recreation Attendant — running ride dispatch and restraint checks, calling a weather or mechanical hold, managing queue throughput and wait-time complaints, operating a game booth or coin-operated attraction, or handling an on-ride evacuation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Agricultural Grader/Sorter — calling a defect grade on a moving packing line, deciding whether a lot with a marginal QC sample gets accepted, hand re-sorted, downgraded, or held, choosing where to station a human grader relative to an optical sorter, or diagnosing why a lot's cull rate or customer chargebacks spiked.
日本語の概要は準備中です。原文の説明を表示しています。
Execute ENCODE DNase-seq pipeline from FASTQ to hotspots and footprints. Child of pipeline-guide. Provides Nextflow execution with Docker and cloud deployment. Use when processing DNase-seq data, calling DNase hypersensitive sites, performing footprinting analysis. Trigger on: DNase-seq pipeline, DNase hypersensitive, DHS, Hotspot2, footprinting, DNase I, chromatin accessibility DNase.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Fast serverless inference on Fireworks AI — open models, fine-tuning, and function-calling optimized endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
DNA methylation analysis — array and bisulfite-seq processing, DMP/DMR calling, and epigenetic clocks.
日本語の概要は準備中です。原文の説明を表示しています。
ChIP-seq analysis — peak calling, differential binding, motif discovery, and QC with phantom-peak metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Build agents on OpenAI's platform patterns — assistants-style threads, function calling, structured outputs, and multi-step tool workflows. Use when working with OpenAI models as the agent engine.
日本語の概要は準備中です。原文の説明を表示しています。
Build LLM applications with chain-style orchestration frameworks — prompts, chains, tool-calling agents, memory, and retrieval pipelines. Use when structuring multi-step LLM programs, adding tools to a model, or composing RAG systems in code.
日本語の概要は準備中です。原文の説明を表示しています。
Required for wearable-originated calls and text messages: resolve recipients for new calls and messages, immediately answer, decline, or cancel calls on the originating wearable instead of silently switching to a paired phone, and refuse an app-based calling route instead of substituting a cellular call.
日本語の概要は準備中です。原文の説明を表示しています。
Turn one approved master still into a character's whole animated sprite set - one image-to-video clip per action (idle, walk, run, attack, jump, hurt, cast and so on), all from that still, generated through generate2dmedia route_media.py (the xAI API when a key is configured, else the local Grok CLI) - then gate each take, key it with a soft matte, register it to the master, pick loops or retime actions, finish (HD by default, pixel on request) and package fixed-canvas frames, alpha WebM, packed MP4 for iPhone and a PNG fallback with engine metadata and a JS runtime. Also processes a supplied clip. Use for character and creature animation, fluid motion and any video-to-sprite work. Not for FX, icon or prop sheets (generate2dsprite), maps or plate loops (generate2dmap), code-drawn animation (codeart2d, only on request) or calling a video API by itself (generate2dmedia).
日本語の概要は準備中です。原文の説明を表示しています。
Plan and build 2D game maps and scenes - top-down and side-scrolling levels, tilemaps, prop packs, parallax backgrounds and HD-2D battle or story plates - with collision, navigation and reachability checks, environment motion, a playable HTML preview and export to Tiled, Godot 4 or LDtk. Map art (terrain, tiles, props, plates, parallax layers) is image generation by default, through generate2dmedia route_media.py (the API when a key is configured, else the local Codex or Grok CLI); map data (layout, collision, exits, spawns) is written as data. Use for any map, level, room, scene, background, terrain or prop-kit request. Not for characters, creatures, items or FX (generate2dsprite), character animation (video2dsprite), code-drawn tiles or maps (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).
日本語の概要は準備中です。原文の説明を表示しています。
Make game-ready 2D characters, creatures, props, icons and FX as master stills, sprite sheets or animation clips. Plan size, motion and finish; generate the art (image generation is the default, through generate2dmedia route_media.py - the API when a key is configured, else the local Codex or Grok CLI); approve one master still per character; then key, slice, register, scale, palette, QA and export frames for a game engine (Aseprite JSON, Godot SpriteFrames or Sprite3D). HD finish by default, pixel finish on request. Character animation is one image-to-video clip per action from the master (video2dsprite); sheets are for FX, icons and props. Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source. Not for maps, tiles or backgrounds (generate2dmap), video clips (video2dsprite), code-drawn art (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).
日本語の概要は準備中です。原文の説明を表示しています。
Presentation/Core/Engine split control plane — the canonical entry point for any work decomposing the Yuzu server into three binaries (presentation · core · engine) per ADR-0031-presentation-core-engine-decomposition / ADR-0032 (the admission interlock) / ADR-0033 (access-control spine). Use when the user says "/split", "/pce-split", "/decomposition", asks to plan or implement a split workstream (WS-A*, WS-B*, WS-X*), asks "what's our gap to the presentation/core split" or "is it safe to extract presentation/the engine yet", asks to audit split readiness, or starts work touching the seam (handlers calling stores directly, the INV-31-4 contract test, the Drogon port, `server/presentation` or `server/engine`, the `uce` DB grants, component service identity, or the ADR-0032 admission/grant/audit substrate — `use_case_run_id`, the release log, the capability-declaration registry).
日本語の概要は準備中です。原文の説明を表示しています。
Guides the usage of Gemini Interactions API on Gemini Enterprise Agent Platform. Use when the user wants to use the stateful, server-managed Interactions API for multi-turn conversations, background execution, streaming, structured output, and function calling on the Agent Platform.
日本語の概要は準備中です。原文の説明を表示しています。
Develop AI-powered applications using Genkit in Go. Use when the user asks to build AI features, agents, flows, or tools in Go using Genkit, or when working with Genkit Go code involving generation, prompts, streaming, tool calling, or model providers.
日本語の概要は準備中です。原文の説明を表示しています。
Connects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemini models and Third-Party OpenMaaS models (Llama, DeepSeek, Qwen, etc.). Use when asked to perform inference, ask a model a question, run a test prompt, execute chat completions, or generate code for calling Gemini or OpenMaaS models, authenticate with GenAI SDK, OpenAI SDK, or legacy Agent Platform SDK, configure base URLs and global/regional endpoints, or troubleshoot 429 Resource Exhausted (DSQ), 400 User Validation, or 404 Not Found errors. Don't use for deploying models to endpoints or for running model evaluations.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when configuring a new or existing Marketing Cloud Account Engagement (MCAE, formerly Pardot) business unit: Salesforce v2 connector activation, connector user permissions, Salesforce User Sync, prospect field sync rules, tracking domain setup, and Account Engagement Lightning App installation. NOT for connecting Marketing Cloud Engagement (email studio, journeys) to Salesforce - use admin/marketing-cloud-connect. NOT for calling the Account Engagement REST API from code - use apex/mcae-pardot-api.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Communications Cloud for the first time: org setup sequence, permission sets, Enterprise Product Catalog (EPC) service catalog, TM Forum-aligned order decomposition setup, Account record-type segmentation, contract lifecycle activation. NOT for designing the commercial-to-technical order process itself - use admin/industries-process-design. NOT for calling TM Forum Open APIs (TMF622, TMF679) - use omnistudio/industries-api-extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Router for the 159 SfSkills `apex` skill packages. Apex and SOQL: triggers, Apex governor limits, async processing, OUTBOUND HTTP callouts, security enforcement, and test patterns. Owns calling an external API FROM Salesforce; salesforce-integration owns inbound. Generic nightly scheduling without naming code belongs to salesforce-flow. Codebase security review belongs to salesforce-security. NOT for SOSL — use salesforce-data. Use when the request mentions Apex, trigger, SOQL, Apex governor limit, batch, queueable, @future, schedulable, test class, CPU time, heap, with sharing, StripInaccessible, callout, HTTP callout, HttpRequest, call an external API, consume a REST API from Apex, Named Credential in Apex, HttpCalloutMock, Apex REST service. Finds and opens the exact skill package to read; it does not contain the guidance itself.
日本語の概要は準備中です。原文の説明を表示しています。
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
日本語の概要は準備中です。原文の説明を表示しています。