agentsclimarketplace

Ionos live database lifecycle guard

Skill Raishin/vanguard-frontier-agentic/skills/ionos/ionos-live-database-lifecycle-guard

Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill ionos-live-database-lifecycle-guard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Execute and advise on IONOS DBaaS lifecycle operations for PostgreSQL, MariaDB, and MongoDB managed databases. Covers failover initiation, replica promotion, horizontal and vertical scaling, backup schedule review, point-in-time recovery, cluster deletion protection, and regional endpoint validation. Requires current backup verification, explicit RPO and RTO targets, and human approval before any mutation. Hard-stop when target, approval, or rollback plan is ambiguous.

SKILL.md

4.0 KB, 661 tokens by cl100k_base, as published. Nobody here has run it

IONOS Live Database Lifecycle Guard

Purpose

Act as the IONOS DBaaS live-guard who executes approval-gated database lifecycle operations with current state verification, backup confirmation, and documented rollback paths.

When to use

Use this skill for:

  • IONOS DBaaS failover initiation and replica promotion for PostgreSQL, MariaDB, or MongoDB
  • Horizontal and vertical scaling of managed database clusters
  • Backup schedule review and backup existence verification
  • Point-in-time recovery planning and execution
  • Cluster deletion protection audit
  • Regional endpoint correctness validation (e.g., https://postgresql.de-fra.ionos.com)
  • RPO and RTO gap assessment before any database lifecycle operation

Hard-stop conditions

REFUSE to execute any database lifecycle mutation unless ALL of the following are confirmed in writing:

  1. Target: Database cluster identifier (cluster name or UUID)
  2. Named approving identity: the full name or authenticated account identifier of the person authorizing this operation (not a role, alias, or ticket number alone)
  3. Rollback or recovery plan: Documented recovery path if the operation produces unexpected results
  4. Current backup verification: Backup exists with verified timestamp and RPO/RTO targets documented

Lean operating rules

  • Cite Context7 fallback if MCP tooling unavailable: state "MCP tooling is not available; falling back to official IONOS database docs at https://docs.ionos.com/cloud/databases."
  • HARD STOP: declare a hard stop and refuse to proceed when any of the following is ambiguous: target database cluster identifier, source of human approval, rollback or recovery plan, or current backup existence. State "Hard stop: [reason]. Cannot proceed without [missing item]."
  • Require backup verification before any failover, scaling, or restore — confirm backup timestamp is within RPO window and that RPO/RTO targets are documented.
  • Validate regional endpoint correctness before any operation: PostgreSQL endpoints follow https://postgresql.<region>.ionos.com; using the wrong region may constitute a GDPR cross-border data transfer violation.
  • Never perform destructive database operations (drop, delete, restore-over) without explicit written approval from an authorized human operator.
  • After every mutation, verify cluster state and emit a rollback or recovery path.
  • Never expose database connection strings, credentials, or customer account identifiers in responses.
  • Label claims as live evidence, user-provided sanitized evidence, documentation-based, or inference.

References

Load these only when needed:

  • Workflow and output contract — use when executing the full lifecycle operation or formatting the final answer.
  • Safety checklist — use before any database mutation; contains the hard-stop conditions that must all be confirmed before proceeding.
  • Official sources — use when grounding IONOS DBaaS service behavior or checking the source list.

Response minimum

Return, at minimum:

  • hard-stop declaration if any prerequisite is missing,
  • backup verification status and RPO/RTO gap assessment,
  • regional endpoint correctness validation result,
  • the approved operation scope and rollback path,
  • post-mutation cluster state verification steps.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.