Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Legacy Banking Infrastructure Support Skill

    2

    Creates structured troubleshooting runbooks for legacy banking systems with incident classification, dependency mapping, log review checklists, escalation paths, rollback guidance, and post-incident summaries.

    $50

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Legacy Banking Infrastructure Support Skill

    Legacy Banking Infrastructure Support Skill

    Example session with this skill installed

    Create a runbook for a recurring overnight batch job failure in a legacy core banking environment. Include severity classification, dependency mapping, evidence collection, log review checklist, decision tree, escalation path, rollback/rerun guidance, data integrity checks, communication templates, post-resolution checks, and post-incident summary template. Do not include commands or unauthorized production actions.

    • Read your context and instructions
    • Compiled the legacy banking infrastructure

    === LEGACY BANKING INCIDENT RUNBOOK ===

    Runbook title
    Overnight Core Banking Batch Job Failure Runbook

    System/capability
    Core banking batch processing

    Purpose
    Provide structured triage for recurring overnight batch failures that may affect account updates, downstream reconciliation, reporting, and start-of-day operations.

    Scope

    Included

    • batch failure classification
    • predecessor and successor job review
    • input/output file checks
    • log review checklist
    • escalation path
    • rerun decision support
    • downstream impact checks
    • post-incident summary

    Out of scope

    • unauthorized reruns
    • direct database edits
    • ledger corrections
    • production changes without approval
    • final decision to rerun or rollback

    Severity model
    SEV-1:
    Batch failure affects core ledger, account balances, settlement, or regulatory deadline.

    SEV-2:
    Batch failure threatens start-of-day operations or downstream reconciliation deadline.

    SEV-3:
    Batch failure is isolated and can be corrected within SLA.

    Incident triggers

    • job fails with non-zero return code
    • job exceeds runtime threshold
    • predecessor job missing
    • input file missing
    • output control totals mismatch
    • downstream reconciliation job blocked
    • repeated failure across multiple nights

    Initial triage

    1. Confirm job name, job ID, and environment.
    2. Confirm first failure timestamp.
    3. Check predecessor jobs.
    4. Check input file arrival.
    5. Check control totals if applicable.
    6. Check whether downstream settlement/reconciliation/reporting deadlines are at risk.
    7. Check recent changes to batch schedule, job parameters, database, files, or vendor feed.
    8. Preserve logs before retry or rerun.

    Dependency map

    Primary job
    [Batch job name]

    Upstream dependencies

    • source transaction files
    • prior posting jobs
    • vendor file transfer
    • scheduler calendar

    Downstream dependencies

    • reconciliation job
    • general ledger interface
    • regulatory reporting feed
    • customer statement generation
    • start-of-day availability

    Evidence to collect

    • job ID
    • job start/end time
    • return code
    • scheduler log
    • application log
    • file arrival timestamp
    • input file size/control total
    • rejected records summary with sensitive data masked
    • downstream blocked jobs
    • recent change record
    • prior incident reference

    Log review checklist

    Application/batch logs

    • first error
    • repeated error pattern
    • rejected record count
    • file format errors
    • timeout errors
    • dependency unavailable

    Scheduler logs

    • predecessor completion
    • job calendar
    • retry attempts
    • resource constraints

    Database metrics

    • locks
    • connection pool
    • storage
    • deadlocks
    • long-running queries

    Decision tree

    IF input file is missing
    Check file transfer status.
    Check vendor delivery confirmation.
    Escalate to file transfer/vendor owner if not delivered.

    IF input file arrived but job rejected records:
    Review rejection summary.
    Mask sensitive data.
    Identify common rejection pattern.
    Escalate to application owner or source-system owner.

    IF predecessor job failed
    Follow predecessor job runbook.
    Do not rerun current job until dependency is resolved.

    IF downstream deadline is at risk
    Escalate to major incident process and business owner.

    IF rerun is considered
    Confirm approval, data integrity impact, duplicate-processing risk, and downstream communication.

    Escalation path

    Incident commander
    [Major incident lead if SEV-1/SEV-2]

    Batch operations
    [Team/contact]

    Application owner
    [Team/contact]

    Database owner
    [Team/contact]

    File transfer/vendor owner
    [Team/contact]

    Business owner
    [Operations/reconciliation owner]

    Compliance/regulatory contact
    [If deadline or reporting risk exists]

    Rollback/rerun decision guidance
    Rollback or rerun must be approved by authorized operations and application owners. Before rerun, confirm duplicate-processing risk, input file integrity, downstream status, and reconciliation impact.

    Workaround assessment
    Manual processing may require dual control, audit record, business approval, and reconciliation plan.

    Data integrity checks

    • duplicate transactions?
    • missing transactions?
    • partial processing?
    • control totals match?
    • ledger affected?
    • downstream reconciliation affected?

    Communication templates

    Technical update
    Batch job [name] failed at [time] with [return code]. Initial impact assessment: [impact]. Evidence collected: [evidence]. Current owner: [owner]. Next update: [time].

    Business update
    Overnight batch processing for [capability] is delayed. Current known impact: [impact]. Reconciliation/settlement deadline risk: [risk]. Next update: [time].

    Post-resolution checks

    • job completed successfully
    • downstream jobs resumed
    • control totals verified
    • reconciliation checks passed
    • business owner notified
    • incident record updated

    Post-incident summary template

    Incident ID

    Job

    Timeline

    Root cause

    Impact

    Resolution

    Approvals

    Data integrity checks

    Action items

    Runbook updates

    Owner and review cadence
    Batch operations owner. Review quarterly or after any SEV-1/SEV-2 batch incident.

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

    About this skill

    Legacy Banking Infrastructure Support Skill helps banks, fintech vendors, enterprise IT support teams, SRE teams, operations managers, and legacy-system consultants turn scattered operational knowledge into structured support runbooks. It creates incident classification workflows, dependency maps, log review checklists, escalation paths, rollback and rerun decision guidance, workaround assessments, data integrity checks, post-incident review templates, support readiness audits, knowledge-base articles, and recurring ticket pattern analyses for core banking, payments, cards, ATM, settlement, reconciliation, online banking, batch processing, middleware, file transfer, database, vendor, and regulatory reporting environments. The skill is designed to preserve institutional knowledge, reduce support workload, improve incident response consistency, and produce audit-ready support documentation without executing production actions.

    This skill creates support documentation, triage workflows, and operational guidance, but it does not execute commands, access production systems, modify banking data, approve rollbacks, restart services, perform privileged operations, or replace authorized incident commanders, SREs, DBAs, security teams, vendors, compliance officers, or banking operations owners. Legacy banking environments may contain confidential, regulated, fragile, or safety-critical systems that require approved internal procedures, dual control, change management, audit logging, and human authorization before action.

    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 any payment.

    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 5 months ago

    Permissions

    Write Files
    Read Files

    File Scopes

    *.md
    *.txt
    *.docx
    *.pdf
    *.rtf
    *.csv
    *.xlsx
    *.json
    *.yaml
    *.yml
    *.log
    README.md
    runbooks/**
    incidents/**
    tickets/**
    logs/**
    architecture/**
    dependencies/**
    batch/**
    payments/**
    cards/**
    atm/**
    settlement/**
    reconciliation/**
    core-banking/**
    online-banking/**
    vendors/**
    escalations/**
    changes/**
    post-incident/**
    knowledge-base/**
    docs/**

    This skill uses file access to read user-provided runbooks, support tickets, sanitized logs, architecture diagrams, dependency notes, batch schedules, escalation matrices, vendor notes, incident summaries, monitoring summaries, change records, post-incident reviews, and internal documentation. It uses write access to create structured Markdown/text outputs such as legacy banking incident runbooks, triage reports, dependency maps, log review checklists, escalation paths, rollback and rerun decision checklists, workaround assessments, post-incident review summaries, knowledge-base articles, support readiness audits, recurring ticket analyses, and SKILL.md files. Browser access is optional and should only be used for public documentation research when explicitly requested. The default safe setup does not require network access, shell access, environment variable access, direct production access, database access, payment-system access, or secret access.

    Listed5 months ago

    What's inside

    Frequently Asked Questions

    This skill automates the creation of structured runbooks, dependency maps, and incident classification workflows, which helps capture disappearing institutional knowledge from veteran staff and reduces the Mean Time to Resolution (MTTR) for complex mainframe and middleware outages.

    The skill is designed to work with any text-based AI agent or LLM interface; simply provide your raw system notes or incident logs, and the skill will output structured documentation in your preferred format (e.g., Markdown, PDF, or Wiki-compatible text).

    No, this skill is strictly for documentation and decision support; it provides audit-ready guidance and checklists to assist human operators but does not have the capability to execute commands or make changes to your production banking environment.

    Your purchase includes the specialized logic for generating legacy-specific runbooks, templates for recurring ticket analysis, post-incident review frameworks, and lifetime access to any future version updates or optimizations.

    The skill is built to handle specific frameworks common in banking, including ISO 20022 messaging, batch processing cycles (EOD/BOD), middleware like MQSeries, and high-availability database architectures used in settlement and reconciliation.

    New in Technical Documentation