インフラ・DevOpsのスキル

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for `kicad`, `emc`, `spice`, and `thermal` analyzers. Use this skill whenever the user asks to extract, verify, or read specs from a component datasheet; when analyzers need verified IC knowledge (EN pin thresholds, PG presence, USB peripheral speed); or when a review mentions datasheet coverage, extraction quality, or per-MPN specifications. Also triggers on "extract this datasheet", "what are the specs for MPN X", "verify datasheet extraction", or "check pin functions for part Y".

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

Use when asked to deploy, release, publish, or ship OpenMeld to production — workers, Web, CLI, or local components. Routes to `pnpm run deploy`; never deploy raw.

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

Use when creating new skills, editing existing skills, or verifying skills work before deployment

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

Inspect Vercel projects and deployments: your account, project list, recent deploys. Trigger phrases: vercel, vercel project, vercel deployment.

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

Inspect Render services and deploys: list services, list recent deploys. Trigger phrases: render, render service, render deploy.

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

Read Prusa Connect cloud state for Prusa 3D printers: printers, jobs, files, cameras, stats, plus file upload. Trigger phrases: prusa connect, prusa printer, prusa job, prusa camera.

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

Read and write Railway: list projects and deployments, set environment variables, redeploy. Trigger phrases: railway, deploy.

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

Inspect Netlify sites and deploys: list sites, list recent deploys. Trigger phrases: netlify, netlify site, netlify deploy.

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

Read and write Langfuse: browse traces and observations, list prompts and datasets, score traces, add dataset items. Trigger phrases: langfuse, llm observability.

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

Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows. Trigger phrases: homey, homey pro, homey flow, athom.

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

Manage Cloudinary media: upload images and videos, list and inspect assets, update metadata, delete assets, and check plan usage. Trigger phrases: cloudinary, upload image, cloudinary usage.

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

Read Cloudflare zones and DNS records: list zones, list DNS records for a zone. Trigger phrases: cloudflare, dns records, cloudflare zone.

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

Backend infrastructure for a project via Cohesivity (cohesivity.ai). Provisions Postgres, Redis, object storage, vector database, hosting, auth, realtime, email inbox, and AI model APIs through one HTTP API. No account or API keys required to start. Trigger phrases: cohesivity, provision backend, need a database, need hosting, need storage, deploy backend, on-the-fly infrastructure.

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

Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.

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

Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.

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

Create or review Terraform infrastructure and plans. Use for cloud resources, IAM, networking, state management, and infrastructure changes.

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

Intent-based observability + traceability router across layers, boundaries, and signals. Routes to vendor-specific skills via category taxonomy; owns transport tuning, meta-observability, incident forensics. Use for observability, traceability, telemetry, APM, RUM, metrics, logs, traces, profiles, SLO, incident forensics, tracing architecture work.

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

Ask for missing deployment settings and summarize the requested configuration without deploying it.

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

Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.

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

Write and publish a post to your own static blog: TL;DR, ASCII art, markdown twin for agents, deploy, and social distribution

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

Release communication pipeline for your product: turn a deployment runsheet and a GitHub milestone into a customer-facing release note with real screenshots and videos, docs updates (including retrofits of articles the release makes stale), a Slack announcement draft, and a lightweight marketing package. Use when you say "cover today's release", "write the release note", or "/release-comms".

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

Turn a deployment runsheet and a GitHub milestone into a customer release note with real media, docs updates, and a Slack announcement draft

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

Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.

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

Use when organizing appendices and supplementary material for an ACL paper under ACL Rolling Review, covering the mandatory Limitations and optional ethics sections, appendices after references, anonymized software and data archives, the no-cloud-links rule, and deciding what must stay in the 8-page or 4-page body.

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