Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    maintenance window and service impact planner

    1

    Planning IT maintenance windows often leads to unforeseen service outages, SLA breaches, and conflicts with business freeze calendars.

    $1.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    maintenance window and service impact planner

    maintenance window and service impact planner

    Example session with this skill installed

    Assess maintenance window CHG-9902 for DB-PROD-01 on 2024-11-15 02:00. Check against the service catalog and the Q4 freeze calendar I've uploaded. Scope is restricted to the 'Infrastructure' group.

    • Read your context and instructions
    • Compiled the maintenance window

    I have assessed the proposed maintenance window for CHG-9902 using the provided service catalogue and freeze calendar.

    Maintenance Window and Service Impact Assessment — CHG-9902, 2024-11-15

    1. Change, sources and assumptions

    • Change ID: CHG-9902
    • Proposed Window: 2024-11-15T02:00 to 2024-11-15T04:00
    • Time Zone: America/New_York
    • Sources: E1 (Change Record), E2 (Service Catalogue), E3 (Q4 Freeze Calendar)
    • Assumptions: All maintenance on DB-PROD-01 results in total service unavailability (E1).

    2. Impacted services

    ServiceEffectDirectDepthViaCriticality
    Core Banking APIOutageNo1DB-PROD-01Tier 1
    Mobile App AuthOutageNo2Banking APITier 1
    Admin PortalOutageNo1DB-PROD-01Tier 3

    Impact Counts: 3 services impacted (2 Tier 1, 1 Tier 3).

    3. Window assessment

    • Verdict: CONFLICT DETECTED
    • Duration: 120 minutes
    • Outage User-Hours: 450.0
    SeverityCodeServiceDetail
    MAJORFREEZE_OVERLAPALLWindow overlaps with 'Q4 Financial Close' freeze (2024-11-14 to 2024-11-16).
    MINORNOTICE_BREACHCore Banking API72h notice required; only 48h provided.

    4. Candidate window ranking

    No candidate windows were supplied.

    5. Exclusions, access scope and approval

    • Access Scope: 2 services outside 'Infrastructure' group were excluded from detailed assessment.
    • Approval Status: Pending (Verified: false).

    6. Information gaps and warnings

    • Warning [W04]: Missing usage profile for 'Admin Portal'; exposure calculated as 0 (Analytical estimate).
    • Gap: Notice lead time for Mobile App Auth not defined in E2.

    7. Draft actions and items for human review

    • Action: Request freeze exception from Finance Steering Committee. (Requires human approval: true)
    • Action: Reschedule window to 2024-11-17 to clear freeze period. (Requires human approval: true)
    • Observation: The overlap with the Q4 Financial Close freeze is a blocking conflict.

    This assessment supports, and does not replace, the judgment and approval of the accountable change authority.

    Next steps

    1. Review the major conflict with the Finance team regarding the Q4 freeze.
    2. Provide a usage profile for the 'Admin Portal' to refine the exposure calculation.
    3. Supply alternative candidate windows to identify a slot without freeze overlaps.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Planning IT maintenance windows often leads to unforeseen service outages, SLA breaches, and conflicts with business freeze calendars. This skill eliminates guesswork by assessing proposed change windows against dependency trees, usage profiles, and notice rules using a deterministic calculation engine.

    What it does

    • Service dependency propagation identifies which upstream services and downstream users are impacted by a CI-level change.
    • Conflict detection flags overlaps with business freeze periods, holidays, and pre-agreed maintenance windows.
    • SLA budget monitoring calculates the impact on downtime budgets and validates notice lead-time requirements.
    • User exposure measurement estimates degraded user-hours based on 24-hour service usage profiles for weekdays and weekends.
    • Candidate window ranking compares multiple potential time slots based on outage duration and user impact.

    How it works

    1. Material registration: You provide the change record, service catalogue extract, and business calendar, which are indexed as evidence sources.
    2. Data validation: The agent checks for required fields like time zones, CI links, and access scopes, asking targeted questions for missing data.
    3. Scripted calculation: The agent generates a structured request and runs a deterministic Python script to compute impacts and conflicts.
    4. Report generation: You receive a structured assessment including impact tables, conflict logs, and ranked window options.

    Frameworks & tools

    This skill utilizes a specialized Python calculation engine (run.py) for deterministic logic. It integrates with ITSM data formats, service catalogues, and business calendars using standard JSON schemas.

    Why this beats prompting it yourself

    Generic prompts often hallucinate dependency chains or fail to calculate complex time-based overlaps accurately. This skill uses a strict logic script to ensure downtime budgets and user-hour exposure are calculated mathematically rather than estimated linguistically.

    Use cases

    • Validating a proposed server maintenance window against a retail peak-season freeze calendar.
    • Identifying which specific business owners must be notified for a core switch upgrade.
    • Comparing three potential weekend windows to find the one with the lowest total user impact.
    • Checking if a short-notice emergency change violates established SLA notice rules.

    Known limitations

    This skill is for decision support only and does not perform scheduling or notifications. It requires manual entry or extracts of service dependency data and usage profiles to function.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    Requires service usage profiles and dependency data to be supplied. Does not interface directly with live ITSM tools. Cannot score change risk or approve windows.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listed2 days ago

    What's inside

    Frequently Asked Questions

    The skill uses a deterministic Python engine to calculate overlaps and downtime budgets mathematically, ensuring precision that standard LLM prompting cannot achieve due to common errors with time-zone math and complex logic.

    You will receive the core logic script, integration schemas for ITSM data, and the agent configuration files required to run the planning logic within your supported AI environment.

    The skill requires a structured extract of your service catalogue and business calendars in JSON or CSV format to accurately map dependencies and identify freeze periods.

    While it performs the complex impact analysis and ranks candidate windows, it does not automatically update your ITSM tool or send notifications; it provides the data needed for a human to finalize those actions.

    Yes, the agent is designed to handle global time zones and differentiates between weekday and weekend usage profiles to calculate user-hour exposure accurately across different regions.