More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Azure Blob Lifecycle Prefix Overdelete

    1

    Find a lifecycle rule targeting the wrong blob container prefix.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Azure Blob Lifecycle Prefix Overdelete

    Repair Azure Blob Lifecycle Prefix Overdelete

    Example session with this skill installed

    A retention policy deletes objects from a neighboring archival path.

    Available evidence: storage rule exports (partial). Additional evidence requested: reference policy or configuration, event and change timeline, owner review or test record. Review this case; identify evidence gaps; do not invent a live test or production action.

    • Read your context and instructions
    • Compiled the repair azure blob

    Repair Azure Blob Lifecycle Prefix Overdelete — EVIDENCE-LIMITED REVIEW

    Scenario received

    A retention policy deletes objects from a neighboring archival path.

    Source register

    • S1: storage rule exports — PARTIAL SOURCE PROVIDED.
    • S2: reference policy or configuration — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: event and change timeline — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: owner review or test record — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. Correlate storage rule exports with the authorized baseline — AWAITING CORROBORATING EVIDENCE.
    2. Isolate ambiguous prefix match in lifecycle policy using matching identifiers — AWAITING CORROBORATING EVIDENCE.
    3. Cross-check timestamps, versions and source ownership — AWAITING CORROBORATING EVIDENCE.
    4. Prepare reversible checks for bounded retention rule correction plan — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • storage rule exports traceability map: DRAFT / INCOMPLETE until evidence is validated.
    • ambiguous prefix match in lifecycle policy exception register: DRAFT / INCOMPLETE until evidence is validated.
    • bounded retention rule correction plan validation plan: DRAFT / INCOMPLETE until evidence is validated.

    Decision

    INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.

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

    About this skill

    Repair Azure Blob Lifecycle Prefix Overdelete is a ToolForge Labs Cursor Skill workflow. Find a lifecycle rule targeting the wrong blob container prefix.

    What this skill checks

    1. Correlate storage rule exports with the authorized baseline.
    2. Isolate ambiguous prefix match in lifecycle policy using matching identifiers.
    3. Cross-check timestamps, versions and source ownership.
    4. Prepare reversible checks for bounded retention rule correction plan.

    What to provide

    • storage rule exports.
    • reference policy or configuration.
    • event and change timeline.
    • owner review or test record.

    Deliverables

    • storage rule exports traceability map.
    • ambiguous prefix match in lifecycle policy exception register.
    • bounded retention rule correction plan validation plan.

    Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.

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

    Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.

    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 19 days ago

    Permissions

    Read Files

    Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.

    Listed19 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill identifies overlapping Azure Blob lifecycle management rules where a broad prefix might be inadvertently deleting data intended for a different archival path, providing a structured correction plan to prevent further data loss.

    The skill is compatible with any LLM-based agent capable of processing JSON or text-based exports, such as ChatGPT, Claude, or custom Azure OpenAI agents.

    You will receive the specialized agent instructions (system prompt) and a structured template for providing your Azure ARM or CLI storage rule exports.

    No, this skill operates as an offline audit tool for safety; it analyzes your exported storage rule JSON files and generates a validated correction plan for you to review and apply manually.

    Simply export your storage lifecycle policies via the Azure CLI or Portal in JSON format and paste them into your AI agent along with the skill instructions to begin the audit.

    The skill handles standard Azure Resource Manager (ARM) storage rule exports and Azure CLI JSON outputs, covering both simple prefix filters and complex multi-rule configurations.

    New in LLM Ops