1,696 件 ・ 関連度順
概要と使いどころ
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute entire application builds. Generates phased delivery roadmaps, then executes them autonomously — phase by phase, committing at milestones, deploying, testing, and continuing until done or stuck. Modes: plan (generate roadmap), start (begin executing), resume (continue from where you left off), status (show progress). Triggers: 'roadmap', 'start building', 'resume the build', 'keep going', 'build the whole thing', 'execute the roadmap', 'what phase are we on'.
日本語の概要は準備中です。原文の説明を表示しています。
Close out (or revisit) a Claude Managed Agent build — refresh the overview page, recap every primitive the founder now owns, show the run log and live status, suggest 1–2 tailored next upgrades, and sweep hygiene (sessions archived, key only in .env, no literal dates in deployment kickoffs). Use when the founder says "/wrap-up", "wrap up", "close it out", "where do things stand with my agent", or at the end of a /launch-your-agent build.
日本語の概要は準備中です。原文の説明を表示しています。
Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.
日本語の概要は準備中です。原文の説明を表示しています。
SVG generation via DAX measures and extension measures with ImageUrl data category for inline visualizations in PBIR reports, including ready templates for matrix and table cells, new card images and per-button images on the new button slicer. Automatically invoke when the user mentions "SVG visual", "DAX sparkline", "SVG measure", "inline graphics with DAX", "ImageUrl data category", "extension measure", or asks to create any DAX-generated chart (progress bars, bullet charts, KPI indicators, data bars, gauges, donut charts, lollipop charts, dumbbell charts, status pills, overlapping bars, boxplots, IBCS bars, jitter plots, box-and-whisker charts).
日本語の概要は準備中です。原文の説明を表示しています。
Automatically invoke this skill whenever the user asks why a Fabric capacity is busy, throttled, at 90 or 100 percent, or what is consuming CUs; asks for current capacity utilization, carry forward or per-item CU usage; wants to query or repair the Microsoft Fabric Capacity Metrics app or its semantic model; or wants to start, pause or monitor a capacity from a script or status bar.
日本語の概要は準備中です。原文の説明を表示しています。
Check Power Platform environment routing status and understand default environment resolution. Use when the user asks about environment routing, developer environments, or new maker landing. Routing is configured in the admin center, not here. NOT for listing flows or managing connections.
日本語の概要は準備中です。原文の説明を表示しています。
Query journal indexing/inclusion status on CNKI - check which databases include a journal (北大核心, CSSCI, CSCD, SCI, EI, etc.), get impact factors and evaluation data. Use when user asks about a journal's level, indexing, or ranking.
日本語の概要は準備中です。原文の説明を表示しています。
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.
日本語の概要は準備中です。原文の説明を表示しています。
Manage GitOps workflows with Flux and ArgoCD. Use for sync status, reconciliation, app management, source management, and GitOps troubleshooting.
日本語の概要は準備中です。原文の説明を表示しています。
Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
日本語の概要は準備中です。原文の説明を表示しています。
Expert SOX IT General Controls (ITGC) advisor for finance, internal audit and IT compliance teams. Covers the four ITGC domains external auditors test for SOX 404 — access to programs and data, program changes, computer operations, and program development — plus scoping in-scope systems from the financial statements, designing risk-and-control matrices (RCMs), writing control narratives and test scripts, evaluating deficiencies (control deficiency vs significant deficiency vs material weakness under AS 2201 and Reg S-X), drafting remediation plans, SOX 404(a)/404(b) applicability and filer status, IPO readiness timelines, and COSO 2013 alignment. Use this skill whenever a user mentions SOX, ITGC, IT general controls, 404(a)/404(b), ICFR, material weakness, user access reviews, segregation of duties in IT, change management controls for financial systems, SOX testing or walkthroughs, PCAOB audits, or quarterly compliance for financial reporting systems.
日本語の概要は準備中です。原文の説明を表示しています。
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance. Triggers include "add badges", "add shields", "README badges", "npm badge", "GitHub stars badge", "CI badge", "download chart", "README header", "README banner", "contributors grid", "sponsors grid", "build a README", "README Studio", "shieldcn", and requests to make a project README look better.
日本語の概要は準備中です。原文の説明を表示しています。
Senior PM for enterprise software and SaaS — portfolio management, quantitative risk analysis, prioritization, and executive reporting. Use for portfolio health reviews, board-ready status reports, and multi-project risk/capacity analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Program management for multi-project coordination, portfolio governance, dependency tracking, benefits realization, charters, and steering-committee reporting. Use to stand up or run a program and escalate program status.
日本語の概要は準備中です。原文の説明を表示しています。
Audit or generate XML sitemaps: limits, lastmod, status codes, robots conflicts. "audit our sitemap"
日本語の概要は準備中です。原文の説明を表示しています。
Check live performance KPIs from connected analytics: RAG status, trends, actions. "quick performance snapshot"
日本語の概要は準備中です。原文の説明を表示しています。
Show integrations status: connected and available connectors, what each unlocks. "which connectors do I have"
日本語の概要は準備中です。原文の説明を表示しています。
Connect a known MCP integration: check the registry and status, return exact setup steps. "connect Google Ads"
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need Codex to coordinate multiple agents through Agent Relay for peer-to-peer messaging, lead/worker handoffs, or shared status tracking across sub-agents and terminals.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.
日本語の概要は準備中です。原文の説明を表示しています。
No Inference / Source-Locked Verification. Forces Claude to answer ONLY from user-provided materials and/or online sources actually accessed — no inference, no assumptions, no gap-filling. Every factual, legal, numerical, or procedural claim must be anchored to a cited source. Use whenever Claude reviews documents, summarises evidence, checks accuracy, drafts submissions, creates timelines, extracts facts, checks citations, analyses rules, prepares legal arguments, compares documents, verifies claims, produces chronologies, works from uploaded materials, performs legal research, checks case status, or does anything where evidential fidelity matters. Also trigger on: 'source-locked', 'no inference', 'only from the materials', 'don't assume', 'stick to the evidence', 'verify this', 'check this is right', 'work from the documents'. Overrides Claude's default tendency to fill gaps. If evidential accuracy matters, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.
日本語の概要は準備中です。原文の説明を表示しています。