インフラ・DevOpsのスキル

Get a value from the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations

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

Set a key and value in the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations

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

Reference guide for Agentica multi-agent infrastructure APIs

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

Delete a key from the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations

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

Ensure agent safety - guardrails, content filtering, monitoring, and compliance

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

Manage agent fleet through CRUD operations and lifecycle patterns. Use when creating, commanding, monitoring, or deleting agents in multi-agent systems, or implementing proper resource cleanup.

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

Stop AI agents from secretly bypassing your rules. Mechanical enforcement with git hooks, secret detection, deployment verification, and import registries. Born from real production incidents: server crashes, token leaks, code rewrites. Works with Claude Code, Clawdbot, Cursor. Install once, enforce forever.

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

Upload tailored resume to cloud or attach to user session. Handles final formatting and delivery.

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

Create Claude Desktop skills from descriptions, SOPs, or existing agents. Three modes - create from scratch, convert SOPs to skills, or migrate agents to skill format. Outputs ready-to-deploy .zip packages.

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

Add a new AI coding agent to Agent Sandbox. Creates all required files (Dockerfile, templates, CI, docs) and wires the agent into the CLI, proxy, and build system.

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

Market intelligence: strategy screener, popularity rankings, top movers with news correlation, quote anomalies, index/ETF constituent stocks, morning briefings, catalyst monitoring for watchlist, event-driven strategies, ETF fund flows, sector rotation, market microstructure, supply chain analysis, industry overviews, and ARK-style disruptive innovation analysis. Triggers: "筛选", "策略筛选", "排行", "热度", "异动", "成分股", "晨报", "早报", "催化剂", "事件驱动", "ETF资金流", "板块轮动", "产业链", "行业概览", "颠覆式创新", "ARK", "篩選", "排行", "異動", "成分股", "晨報", "ETF資金流", "板塊輪動", "產業鏈", "screener", "rank", "anomaly", "constituent", "morning brief", "catalyst", "event strategy", "ETF flow", "ETF资金流", "ETF申赎", "ETF資金流", "etf flow", "资金申赎", "etf 资金", "sector rotation", "supply chain", "ARK", "disruptive innovation", "板块筛选", "行业筛选", "板塊篩選", "強勢板塊", "弱勢板塊", "top sectors", "催化劑", "事件驅動", "行業概覽", "顛覆式創新", "策略篩選", "熱度"

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

Technical analysis frameworks — candlestick patterns, Ichimoku cloud, technical indicators (RSI/MACD/EMA/Bollinger), harmonic patterns (Gartley/Bat/Butterfly/Crab), Elliott Wave, Chan Theory (缠论 bi/zhongshu/buy-sell points), Smart Money Concepts (BOS/FVG/Order Block), and Turtle Trading signals with ATR/Unit position sizing. Triggers: "技术分析", "K线形态", "蜡烛图", "一目均衡表", "RSI", "MACD", "布林带", "谐波形态", "艾略特波浪", "缠论", "分型", "笔", "中枢", "Smart Money", "BOS", "FVG", "海龟交易", "海龟信号", "K線形態", "蠟燭圖", "一目均衡表", "纏論", "ichimoku", "candlestick pattern", "K线形态识别", "形态识别", "识别K线", "识别形态", "harmonic", "Elliott Wave", "chan theory", "turtle trading", "SMC", "technical indicators", "技術分析", "海龜交易", "海龜信號", "諧波形態"

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

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

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

Draft a new RFC document for the Incan language project. Use when the user asks to write, create, or draft an RFC, or wants to propose a new language feature or infrastructure change for Incan.

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

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

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

Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.

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

Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. Two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude uses for oncall. A workspace can have several such channels; run once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory. Use on "set up oncall", "init oncall", "configure Claude for on-call". Surveys the agent connectors an admin configured for Claude, proves one with a read-only pull so access is verified, explores tools, Slack, repos and docs to learn how oncall works here, then recommends what's missing and walks the team through setup. The result goes into the indexed oncall memory every channel reuses; the other skills (incident init, investigation, handoff) pick it up automatically.

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

Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".

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

Expert FinOps guidance for cloud, AI, and SaaS technology spend. Covers AI cost management, agentic FinOps, GenAI capacity planning, self-hosted vs managed inference, Anthropic billing, open-weight vendor APIs (DeepSeek, Qwen, Kimi, GLM), AWS (EC2, Bedrock, SageMaker, Savings Plans, CUR), Azure (reservations, AHB, OpenAI PTUs), GCP (Vertex AI, BigQuery), OCI, Kubernetes cost allocation, data platforms (Databricks, Fabric F-SKUs, Snowflake), tagging governance, SaaS management (SAM, shadow IT), AI coding tools (Cursor, Claude Code, Copilot, Codex), ITAM, allocation, showback, chargeback, anomaly management, KPIs and benchmarking, waste detection playbooks, workload onboarding and M&A, and GreenOps (cloud carbon, CSRD). Use for any question about technology cost or waste in your estate - expiring commitments or RIs, NAT gateway bills, idle VMs, snapshot sprawl - and for commitment sizing, rightsizing, allocation, SaaS sprawl, AI dev tool spend, or connecting spend to business value. Built by OptimNow.

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

Build and query a local Markdown knowledge base ("vault"). TWO functions — (1) CONVERT raw files (PDF, Word/docx, PowerPoint/pptx, Excel/xlsx, csv/tsv, images, html, md/txt, json/yaml/code, audio/video) into clean Markdown with retrieval-friendly frontmatter; local-first (pandoc / python-pptx / openpyxl / pymupdf4llm / whisper), with cloud OCR (MinerU) only as a fallback. (2) ANSWER questions over the resulting vault with retrieval discipline — self-monitor coverage, flag missing/lossy content, and propose Maps-of-Content (MOCs). Triggers: "build/sync my local knowledge base", "convert these files to markdown for AI", "整理我的资料库", "把文件转成 md 给 AI 读", "本地知识库", "读我的本地 vault 回答", "这个主题我的资料里怎么说". Not for: one-off web research, or files that are already in a single doc you can read directly.

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

VNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.

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

System monitoring, alerting, and observability implementation

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

Read-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.

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

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

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