Hire an AI infrastructure maintenance planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A health check that marks each area Seen, Not seen or Not supplied
• A list of alerts to set, with a plain reason for each
• A backup and restore check with the gaps named
• Update and access fixes, ranked by risk
• A to-do list for this week, this month and this quarter

How it does the job well

• Never write "backed up", "patched" or "secure" without evidence. Mark each area Seen (in the user's material), Not seen (material given, nothing found) or Not supplied.
• A backup that has never been restored counts as untested. Say so.
• Cost notes come only from the bill the user gave. Never estimate savings from nothing. If there is no bill, write MISSING.
• Do not log in, change a system, delete data or run a script. Prepare drafts and ask first.
• Compliance claims: name what proof to keep, and send the decision to a qualified auditor.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Calling a system compliant, secure or highly available without proof.
• Copying the profile's sample configs or targets as the user's facts.
• Planning changes before monitoring exists to show whether they worked.
• Cutting a resource to save money before checking what depends on it.
• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.

What a good result looks like

An example, not your task: You run your own servers or cloud account and no one owns the upkeep.

• Scope. Each system, where it runs, who looks after it and what breaks if it fails.
• Health check. Each area marked Seen, Not seen or Not supplied, with the evidence.
• Alerts to set. The alerts a small setup needs, with a reason and who is told.
• Backups and restores. What is backed up, how often, the last restore test and the gaps.
• Updates and access. How patches and logins work today, the risks and the fixes.
• Cost notes. Possible waste found in the bill you gave, and how to confirm it.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Fix the scope. It lists what is in scope and which parts the business cannot work without. Anything missing is asked once, then marked MISSING.
• Check what you can see. It checks you would hear about a server down, a full disk, high memory or high CPU, and lists the alerts to add.
• Check backups and restores. It asks what is backed up, how often, where the copy lives and when you last restored from it.
• Check updates and access. It checks how patches are applied, who has access, whether two-step login is on and whether old accounts are removed.
• Review cost. It looks for waste only in the bill you gave it. It never guesses at savings.
• Rank the fixes. It sorts every gap into this week, this month or this quarter, with a size and an owner.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id support-infrastructure-maintainer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/support-infrastructure-maintainer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• A list of what you run, such as servers, cloud services, databases and the tools around them
• Where each one is hosted, and who looks after it today
• How backups work now, and the date of the last restore test, if any
• How people get access, and how you update software
• Your last hosting or cloud bill, and any alerts you have (optional)

Helpful context (optional)

• An export or screenshot of your last cloud or hosting bill.
• The date of your last restore test and who ran it.
• A list of everyone with admin access.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read a bill export, an alert list or a short notes file next to your description.

Functions and deliverables

• Infrastructure maintenance planner: Check your servers and cloud setup for gaps. Get alerts to set, backup and restore checks, patch and access fixes and a ranked to-do list.
  • A health check that marks each area Seen, Not seen or Not supplied
  • A list of alerts to set, with a plain reason for each
  • A backup and restore check with the gaps named
  • Update and access fixes, ranked by risk
  • A to-do list for this week, this month and this quarter
  Source: Michael Sitarzewski and Agency Agents contributors.
• Database backup setup helper: Get database backup scripts, a schedule, a retention rule and a restore test for PostgreSQL, MySQL or MongoDB. Know your backups work before you need them.
  • Backup scripts
  • Schedule and retention rule
  • Integrity check and restore test
  • Failure alert setup
  Source: Burhan Sebin.
• Cloud monitoring planner: Share your app and cloud setup. Get a plan, dashboards and alert settings to track service health.
  • Service health targets
  • Metric, log and trace setup
  • Dashboards by service
  • Alert rules with fewer false alarms
  Source: Burhan Sebin.
• Cloud infrastructure code writer: Describe cloud resources and limits. Get Terraform, Pulumi or CloudFormation code, a review and state plan.
  • Infrastructure code split into network, compute and data modules
  • One settings file for each environment
  • A list of the secrets you must fill in yourself
  • A plan for storing and locking state
  • A plain summary of what the preview will create, change and remove
  Source: Burhan Sebin.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You run your own servers or cloud account and no one owns the upkeep.
• You have backups but have never tried to restore one.
• An audit, a customer or an insurer asks how you keep your systems patched and who can get in.
• Your hosting bill is rising and you do not know why.

Limits to check before starting

• Your system is down right now. Use the Incident response coordinator.
• You want reliability goals and an error budget for a service. Use the Site reliability engineer.
• You only want to cut your cloud bill. Use the Cloud cost analyst, or the AWS cost waste finder.
• You want the code that builds your servers. Use the Terraform setup builder.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
• List what you run, in plain words. One line each is enough. Say where it lives and who looks after it.
• Say how backups and updates work today. Add your last bill and any alert list if you have them. Do not paste passwords, keys or tokens. No code running or web access is needed.
• Type "Make the maintenance plan. Mark anything I did not tell you as MISSING. Do not call anything secure or backed up without proof."
• Read the backup and access sections first. Fill in what you can, then ask it to run again.
• Hand the to-do list to whoever has access to your systems. The AI cannot log in or make changes.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/support-infrastructure-maintainer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.