294 件 ・ 関連度順
概要と使いどころ
Check current Claude usage limits (session and weekly) with ASCII progress bars. Trigger when the user asks about usage, quota, limits, rate limits, how much Claude they've used, remaining capacity, or phrases like "check usage", "usage status", "how much quota left", "am I close to the limit", "用量", "额度", "配额".
日本語の概要は準備中です。原文の説明を表示しています。
火山引擎资源巡检、水位评估、容量建议、趋势判断与预算优化 Skill。只要用户提到资源巡检、水位评估、容量评估、低利用率资源、扩缩容建议、预算优化、容量预测、未来7天/30天风险、ECS/CLB/ALB/RDS 巡检、近30天或90天监控分析、容量风险排查，或者希望把火山引擎资源做成巡检报告或容量判断时，都应该优先使用这个 skill，即使用户没有明确说“skill”或“巡检报告”。
日本語の概要は準備中です。原文の説明を表示しています。
Model-guided autonomous root-cause analysis over a UModel object-graph semantic layer. Use with `umodel-query` when diagnosing service degradation, SLO breach, latency/error spikes, incidents, outages, or questions like why a service is slow, degraded, erroring, or timing out. The skill guides evidence collection across object graph, metrics, logs, topology, runbooks, deployments, config changes, business traffic, and runtime capacity; it is especially useful for ruling out red herrings such as recent but unrelated deployments. Triggers: root cause, RCA, incident, SLO breach, outage, postmortem, latency spike, error spike, timeout, 根因分析, 故障排查, 告警定位, 为什么慢, SLO 击穿.
日本語の概要は準備中です。原文の説明を表示しています。
Process-based discrete-event simulation. Model queues, shared resources, timed events: manufacturing, service ops, network traffic, logistics. Processes are Python generators yielding events. Resources: capacity-limited (Resource/Priority/Preemptive), bulk (Container), objects (Store, FilterStore). For continuous use SciPy ODEs; for agent-based use Mesa.
日本語の概要は準備中です。原文の説明を表示しています。
Provides AWS CloudFormation patterns for DynamoDB tables, GSIs, LSIs, auto-scaling, and streams. Use when creating DynamoDB tables with CloudFormation, configuring primary keys, local/global secondary indexes, capacity modes (on-demand/provisioned), point-in-time recovery, encryption, TTL, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Electricity Maps contrib parser development, capacity updates, zone/exchange configuration maintenance, and focused repo validation workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Manages deletion requests for children's personal data. Covers parental-initiated versus child-initiated requests, age of capacity assessment, identity verification, scope determination, third-party notification obligations, and regulatory timelines under GDPR Art. 17, COPPA Section 312.6, and UK AADC Standard 15. Keywords: deletion, children, right to erasure, parental request, data deletion, COPPA.
日本語の概要は準備中です。原文の説明を表示しています。
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and optimize resource allocation. Trigger with "resource planning", "capacity", "utilization", "staffing plan", "who should work on what", "we're stretched thin", or when the user needs help allocating people, budget, or time across projects and teams.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is transitioning from a completed retro into a weekly plan, choosing weekly outcomes, scheduling a full ISO week, or asking for "план на неделю", "weekly planning", priorities, capacity, or outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Operational KPI tracking, headcount trends, utilization rates, backlog analysis, book-to-bill ratio, operational efficiency metrics, capacity utilization, productivity metrics, operational leverage, same-store sales
日本語の概要は準備中です。原文の説明を表示しています。
Patient-flow market sizing for med products — prevalence → diagnosed → interested → affordable → covered → treated → persistent, priced as price × duration per cohort, with capacity constraints, named historical analog anchoring, and always bull/base/bear named-driver grids. Use to size a therapy area or product market before any valuation or share work.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Fire Protection Engineer. Use when a task calls for Fire Protection Engineer judgment. Reasons from NFPA 13 Hazen-Williams hydraulics (K-factor, remote area, hose stream) and NFPA 101 egress (occupant load, travel distance, capacity factors) through NFPA 92 smoke containment/management, ASET/RSET PBD, and FDS/CFAST/CONTAM/PyroSim modeling while treating breached compartmentation, C-factor/fitting errors, and supply-curve shortfall as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Energy Systems Engineer. Use when a task calls for Energy Systems Engineer judgment. Reasons from exergy, load duration curves, capacity factor, and grid boundary constraints through pinch analysis, hourly dispatch models (PLEXOS, HOMER Pro, SAM, PVsyst), spark-spread CHP screening, and IPMVP M&V while treating nameplate-vs-utilization confusion, average-vs-marginal grid emissions, unrealistic arbitrage spreads, and demand-charge ratchet resets as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Dentist-Scientist. Use when a task calls for Dentist-Scientist judgment. Reasons from oral biofilm-host ecology, tissue healing capacity, and patient-level clinical endpoints (DMFS, PD/CAL, implant survival) through PICO/PROSPERO protocols, CAMBRA and 2017 AAP/EFP staging, ISO 4049/14801 bench tests with thermocycling, and GRADE-rated reviews while treating in-vitro-to-chairside leaps, plaque-index surrogates without caries reduction, and examiner calibration drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Earthquake Engineer. Use when a task calls for Earthquake Engineer judgment. Reasons from ASCE 7 DRS and SDC, capacity design (R, Cd, Ω₀), ELF/MRS/NRHA and ASCE 41 pushover; models in SAP2000/ETABS/OpenSees with PEER NGA-West2 motions; treats liquefaction, soft-story P-delta collapse, and record-scaling artifacts as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Communications Engineer. Use when a task calls for Communications Engineer judgment. Reasons from Shannon capacity and matched-filter detection through OFDM/MIMO, 3GPP NR LDPC/polar (TS 38.212), TR 38.901 link budgets, Keysight 89600 VSA EVM, ns-3 SLS, and berconfint Monte Carlo while treating CFO/IQ/phase-noise coupling, pre- vs post-FEC BER, and AWGN-only optimism as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Automates Azure OpenAI model deployment by checking capacity across regions and deploying to the best available option.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a content strategy a small team can execute: audience needs backed by counted evidence, an audit of what is already published, a topic map with one page per search intent, a scored backlog, a 90-day calendar sized to real capacity, and the numbers that will show whether it worked. Use when someone asks "what should we write about", "plan our blog", "content strategy", "content plan for next quarter", "topic clusters", "content audit", "our blog traffic is falling", or wants a pile of content ideas turned into a prioritised plan.
日本語の概要は準備中です。原文の説明を表示しています。
Your first 10 hires determine your company culture. Your first 50 determine your execution capacity. Hiring is the most leveraged activity a founder does, and the most common source of expensive mistakes. This skill covers when to hire, who to hire first, how to sequence roles, compensation and equity, interviewing and closing, and the many ways hiring goes wrong at startups. Use when "hiring, first hire, when to hire, who to hire, compensation, equity, salary, recruiting, interview process, offer negotiation, team building, engineer hire, sales hire, founding team, hiring, team, compensation, equity, recruiting, interviews, offers, startups, founding-team" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Power systems engineering covering grid modeling, power flow analysis, energy storage dispatch, demand response, and electricity market economics. Spans transmission/distribution planning to real-time operations. Use when "power flow|load flow|grid model, energy storage|battery dispatch|ESS, demand response|load management|peak shaving, electricity market|LMP|locational marginal price, grid stability|frequency|voltage, capacity planning|resource adequacy, unit commitment|economic dispatch, transmission|distribution|power system, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
The intersection of AI generation and performance marketing. This skill covers creating ad creatives at scale using AI tools—from static images to video ads to dynamic creative optimization—while maintaining the conversion focus that performance marketing demands. Traditional creative testing is slow: create 5 variants, wait weeks for data, iterate. AI-powered ad creative is fast: generate 50 variants in an hour, test simultaneously, learn in days, iterate continuously. The constraint is no longer production capacity—it's testing velocity and creative strategy. This skill bridges AI generation capability with advertising effectiveness, ensuring that AI-created ads don't just look good—they convert. Use when "AI ads, ad creative, performance creative, ad generation, creative testing, ad variants, DCO, dynamic creative, Meta ads, Google ads, ad fatigue, conversion creative, advertising, performance-marketing, creative-testing, ai-ads, conversion, paid-media, scale" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He
日本語の概要は準備中です。原文の説明を表示しています。
Suede-affiliated marketing ideation using a structured tactic library scored for stage, audience fit, evidence, capacity, cost, and risk. Use when the user is stuck, wants options, or needs a shortlist of growth tactics before committing to a plan. NOT FOR: a comprehensive roadmap (use suede-marketing-plan), channel execution (use the relevant public Suede skill), or unattended recurring workflows (use suede-marketing-loops).
日本語の概要は準備中です。原文の説明を表示しています。