Analyze fleet maintenance programs for preventive maintenance scheduling effectiveness, parts inventory forecasting, vehicle downtime minimization, total cost of ownership modeling, and telematics integration.
日本語の概要は準備中です。原文の説明を表示しています。
5,765 件 ・ 関連度順
概要と使いどころ
Analyze fleet maintenance programs for preventive maintenance scheduling effectiveness, parts inventory forecasting, vehicle downtime minimization, total cost of ownership modeling, and telematics integration.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 when setting up, customizing, or troubleshooting the Salesforce Path component on Opportunity, Lead, Case, or custom objects. Triggers: 'add guidance to stages', 'key fields on path', 'celebrate closed won', 'path not showing', 'configure path steps', 'confetti on stage change'. NOT for creating the stage picklist — use admin/opportunity-management. NOT for in-app prompts — use admin/in-app-guidance-and-walkthroughs. Metadata: PathAssistant, PathAssistantStep, PathAssistantSettings, pathAssistantEnabled, canOverrideAutoPathCollapseWithUserPref, runtime_sales_pathassistant:pathAssistant, picklistValueName, recordTypeName, BusinessProcess.
日本語の概要は準備中です。原文の説明を表示しています。
Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.
日本語の概要は準備中です。原文の説明を表示しています。
Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".
日本語の概要は準備中です。原文の説明を表示しています。
Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification.
日本語の概要は準備中です。原文の説明を表示しています。
Iterate on a GenAI notebook against the self-hosted stack via the genai-stack CLI (config dirs, auth, subdomains, quantization, GPU/VRAM). Arguments: <notebook|service> [--service comfyui|forge|vllm] [--quant int4|fp8] [--validate] [--bg]
日本語の概要は準備中です。原文の説明を表示しています。
Use when wrangler deploys silently fail or produce wrong artifacts, secrets upload as empty strings, custom domain DNS is not resolving, route assignment broke after rename, observability/tail logs are needed, D1/KV/R2 bindings are missing, OAuth scope errors block a command, cookies on a redirect are not attaching, or the worker exceeds CPU time. Triggers: "Tenant or user not found", "Authentication error" on wrangler d1 push, secret length is 0 after upload, route returns origin not worker, "compatibility_date too old", 1101 errors, custom_domain assignment lost on script rename. NOT for AWS Lambda / Vercel Edge / Deno Deploy (different runtimes), Cloudflare Zero Trust, or R2-specific tuning.
日本語の概要は準備中です。原文の説明を表示しています。
Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).
日本語の概要は準備中です。原文の説明を表示しています。
Selects spironolactone as first-line mineralocorticoid receptor antagonist for bilateral primary aldosteronism, with eplerenone as an alternative when spironolactone–related adverse effects are problematic. Trigger phrases include 'confirmed bilateral PA on AVS', 'idiopathic adrenal hyperplasia', 'bilateral adrenal hyperplasia', 'glucocorticoid-remediable aldosteronism', and 'initiating medical therapy for bilateral adrenal disease'.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies young patients with classic primary aldosteronism features who may proceed directly to unilateral adrenalectomy without adrenal venous sampling based on high probability of unilateral disease. Triggered when a clinician sees a patient <35 years with hypokalemia, unilateral adrenal tumor on CT, and high plasma aldosterone concentration and asks whether AVS can be bypassed.
日本語の概要は準備中です。原文の説明を表示しています。
Adjusts intravenous bisphosphonate dosing and infusion duration for patients with hypercalcemia of malignancy and renal insufficiency (creatinine clearance <60 mL/min). Triggered when a clinician encounters renal impairment and asks how to modify zoledronic acid or pamidronate infusion rates.
日本語の概要は準備中です。原文の説明を表示しています。
This skill outlines the emergency management of suspected adrenal crisis, recommending immediate parenteral hydrocortisone (100 mg adult, 50 mg/m² pediatric) plus fluid resuscitation, then 200 mg/24 h (50–100 mg/m²/24 h pediatric) hydrocortisone. Trigger when patient presents with hypotension, hyponatremia, hyperkalemia, or unexplained shock suggestive of adrenal insufficiency.
日本語の概要は準備中です。原文の説明を表示しています。
Applies serum cortisol cutoffs (<3 μg/dL indicates central adrenal insufficiency; >15 μg/dL likely excludes it) when evaluating morning cortisol for suspected adrenal insufficiency. Triggers include morning cortisol measurement in suspected AI and use when interpreting morning cortisol levels for adrenal insufficiency workup.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends measuring serum cortisol levels at 8–9 AM as the first-line test for diagnosing central adrenal insufficiency. Use when starting diagnostic workup for suspected adrenal insufficiency; triggers include suspected adrenal insufficiency requiring initial cortisol testing.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends against using fludrocortisone for mineralocorticoid replacement in patients with secondary adrenal insufficiency. Trigger phrases include: considering mineralocorticoid replacement for secondary adrenal insufficiency and secondary adrenal insufficiency patient needing mineralocorticoid replacement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when constructing base / upside / downside scenarios — three-statement modeling, sensitivity analysis, optionality reasoning. Triggers on 'model the scenarios', 'what if growth halves'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when documenting APIs — OpenAPI/Swagger, PHP attributes, Redocly validation, versioned specs — even when the user just says 'document this endpoint' without naming OpenAPI.
日本語の概要は準備中です。原文の説明を表示しています。
Memória é a base de agentes inteligentes. Sem ela, cada interação começa do zero. Esta skill cobre a arquitetura de memória de agentes: curto prazo (janela de contexto), longo prazo (vector stores), e as arquiteturas cognitivas que as organizam. Insight-chave: Memória não é apenas armazenamento - é recuperação. Um milhão de fatos armazenados não significam nada se você não conseguir encontrar o certo. Estratégias de chunking, embedding e recuperação determinam se seu agente se lembra ou esquece. O campo é fragm
日本語の概要は準備中です。原文の説明を表示しています。
Author a complete both-seats coaching lesson for a BBA-NATIVE bidding scenario and produce all served artifacts in one consistent pass: curate the pool → tokenized coaching-curated/<scn>.pbn → gated promote to served coaching/<scn>.pbn → resolve to South=student coaching-non-rotated/<scn>.pbn (bridge-classroom) → update both toc.json files. Invoke as `/coach-lesson <Scenario>` (e.g. `/coach-lesson Fourth_Suit_Forcing`). Use ONLY for conventions BBA bids natively (its bba/<scn>.pbn [Auction] is the answer key — Basics, New_Minor_Forcing, Fourth_Suit_Forcing). For conventions BBA CANNOT bid (Spiral Raises), use the py/spiral_auction.py substitution path instead — not this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Write acceptance criteria for a Jira story using Given/When/Then scenarios. Use this skill when the user asks to write AC, acceptance criteria, write scenarios, improve a story, add AC to a ticket, or mentions a Jira ticket and wants better requirements. Also triggers on "write better AC", "this story needs AC", "add scenarios to this ticket", or when reviewing a Jira story for completeness.
日本語の概要は準備中です。原文の説明を表示しています。
Create a language-agnostic ghost package (spec + portable tests) from an existing repo by extracting SPEC.md, exhaustive tests.yaml (operations and/or scenarios), INSTALL.md, README.md, VERIFY.md, and upstream LICENSE files with provenance and regeneration instructions. Use when prompts say "/tw-ghost", "ghostify this repo", "spec-ify/spec-package this library", "ghost library", or ask to extract portable spec/tests for libraries or tool-using agent loops (scenario testing); do not use for implementation work or editing skills.
日本語の概要は準備中です。原文の説明を表示しています。
Sweep every external pointer to you (profiles, READMEs, bios, link pages) after a rename of a repo, org, domain, handle or account, and fix the dead ones. Use right after any public rename and once a quarter as hygiene. Triggers: /link-rot, /lr, check links, broken profile links, after the rename, link rot.
日本語の概要は準備中です。原文の説明を表示しています。