「maturity」の検索結果

Evaluates target company operations with management assessment, systems review, process maturity, and improvement opportunity identification. Use when conducting ops DD, assessing operational risk, or identifying value creation levers.

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

Evaluates IG bond market conditions with spread analysis, maturity curve optimization, and investor demand assessment. Use when advising IG issuers, analyzing credit spreads, or timing IG bond offerings.

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

Design and execute chaos engineering experiments using Litmus or Chaos Mesh. Test system resilience through controlled fault injection, validate hypothesis-driven tests, and improve failure recovery. Use before major product launches, after architecture changes to validate resilience, during GameDays or disaster recovery drills, to validate assumptions about failure modes, or as part of an SRE maturity program.

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

"Apply the three-level framework of digital transformation — Digitization, Digitalization, and Digital Transformation — to diagnose and plan organizational change enabled by digital technologies. Use this skill when the user needs to assess an organization's digital maturity, distinguish between automating processes versus transforming business models, plan a DX roadmap, or when they ask 'where are we on digital transformation', 'is this digitization or real transformation', or 'how do we build a DX strategy'.".

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

Facilitate and document Sprint Retrospectives per Scrum Guide 2020. Choose format by team maturity, structure the session, capture action items, and track improvement across sprints. Use after every sprint. Do not use for individual performance reviews, blame sessions, or annual assessments.

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

Identify gaps between current and desired state. Use when the user says "gap analysis", "what's missing", "current vs future state", "where are the gaps", "capability gap", "maturity assessment", "fit-gap analysis", "what needs to change", "compare current to target", "readiness assessment" - even if they don't explicitly say "gap analysis".

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

Validate Claude Ads contracts, scoring inputs, run bundles, capabilities, source freshness, safety, installation, uninstall, or release readiness. Use for ads validate, ads status, ads next, stale claims with missing tool access, maturity checks, ownership-manifest uninstall, preserving unrelated ads-* skills, checksum verification, preflight, QA, or release audits. Missing access must demote stale evidence for the run and block dependent release-current claims before recovery guidance.

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

Audit whether a product is ready for enterprise sales. Use when you need to assess SSO/SAML/SCIM support, RBAC maturity, multi-tenancy data isolation, audit logging coverage, public API quality, SLA operational readiness, SOC2/ISO27001 certification gaps, GDPR data residency controls.

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

Audit a codebase for product-market fit readiness -- evaluate startup PMF signals, core value loop tightness, feature scatter vs focus ratio, user activation funnel friction, retention hook infrastructure, pricing flexibility, analytics event coverage, CI/CD iteration speed, and growth-stage maturity for pre-seed through Series A products.

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

Analyze an incident response program for playbook coverage, MTTR optimization opportunities, evidence collection readiness, root cause analysis quality, and post-incident review effectiveness. Triggers: building a SOC, assessing IR maturity, optimizing detection-to-recovery timelines.

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

Analyze an HR operations system for headcount planning effectiveness, attrition pattern detection, compensation benchmarking accuracy, workforce analytics maturity, and onboarding process optimization..

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

Select and implement the right Azure compute platform for a workload. Decision tree guides choice based on workload characteristics, scaling needs, and operational maturity. Covers serverless, PaaS, containers, Kubernetes, and IaaS patterns.

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

This skill determines whether testicular volume should be used as the primary or sole indicator of sexual development in male childhood cancer survivors who have received gonadotoxic treatments such as alkylating agents or testicular radiotherapy. Triggers include clinician questions like “Can I use testicular volume to assess puberty in this male survivor after chemotherapy?” or “Is testis size reliable for sexual maturity evaluation post‑radiation?”

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

Groups companies by industry, business model, size, maturity, market, or strategic fit. Use when the user provides company records and wants consistent segment assignments with definitions and confidence.

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

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

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

Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.

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

This skill should be used when providing ITIL 4-based IT service management consulting. Use this when organizations need guidance on implementing ITIL 4 practices, improving service management maturity, optimizing IT operations, or aligning IT services with business objectives. Provides tailored recommendations based on department, scenario, and organizational context using comprehensive ITIL 4 knowledge.

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

Knowledge base from NASA NPR 7123.1D — Systems Engineering Processes and Requirements. Use for the 17 common SE processes (SE Engine), life-cycle reviews and entrance/success criteria, SEMP structure and content, ETA roles and tailoring/customizing rules, Technology Readiness Levels (TRL 1–9), SE work product maturity terminology, contracted project oversight, and MOE/MOP/TPM measurement frameworks. Does not cover NASA programme financial management, human spaceflight medical standards, or software engineering requirements in depth (see NPR 7150.2 for the latter).

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

Use when the user asks to "audit our social presence" or "is this batch safe to publish"; runs either the typed ECHO asset gate or a separate program-maturity profile, with channel-truth, claim, disclosure, manipulation, UGC-rights, and denominator checks. Not for creator deliverables — use creator-content-auditor; not for launch readiness — use launch-readiness-auditor. 社媒资产门/运营成熟度/发布前放行

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

Validate Claude Ads contracts, scoring inputs, run bundles, capabilities, source freshness, safety, installation, uninstall, or release readiness. Use for ads validate, ads status, ads next, stale claims with missing tool access, maturity checks, ownership-manifest uninstall, preserving unrelated ads-* skills, checksum verification, preflight, QA, or release audits. Missing access must demote stale evidence for the run and block dependent release-current claims before recovery guidance.

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

Read a designer's taste through their typography decisions alone. Type is the fastest taste signal in any design. Use when evaluating design maturity, assessing portfolio quality, or understanding what typography reveals about design thinking.

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

Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.

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

Use this skill when the user asks how to build, measure, or improve safety culture in a motor carrier — leading vs lagging safety indicators, blame-free reporting, near-miss programs, safety committee structure, monthly safety meetings, ATA Safety Management Program guidance, and how to evaluate cultural maturity. Reference ATA SMP + DOT safety culture research.

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

Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.

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