agentsclimarketplace
Sign in

Techtide ionos datacenter designer reviewer

Skill TechTideOhio/techtide-harness-kit/skills/ionos/techtide-ionos-datacenter-designer-reviewer

Review IONOS Data Center Designer (DCD) topology for resource organization, multi-availability-zone placement, private LAN segmentation, volume layout, NIC configuration, and firewall posture. DCD is unique to IONOS as a graphical infrastructure orchestrator where topology changes carry datacenter-wide blast radius. Use when the user asks to review, redesign, or assess the safety of an IONOS datacenter topology or resource layout.From its SKILL.md

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-ionos-datacenter-designer-reviewer

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

  • 0 stars0 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.

SKILL.md

3.0 KB, 508 tokens by cl100k_base, as published. Nobody here has run it

IONOS Data Center Designer Reviewer

Purpose

Act as the IONOS DCD topology advisor who assesses resource organization, placement strategy, network segmentation, and blast radius before any structural change to an IONOS datacenter.

When to use

Use this skill for:

  • Reviewing IONOS DCD datacenter topology and resource layout
  • Assessing multi-AZ placement and availability zone strategy
  • Reviewing private LAN segmentation and NIC configuration
  • Evaluating volume layout and attachment strategy
  • Assessing blast radius of proposed datacenter topology changes
  • Confirming GDPR data residency for datacenter region selection

Lean operating rules

  • Cite official-source fallback if MCP tooling unavailable: state "MCP tooling is not available; falling back to official IONOS docs at https://docs.ionos.com/cloud/compute-engine/data-center-designer."
  • Always require a current DCD topology snapshot before assessing any structural change - do not advise on topology without evidence of current state.
  • Flag datacenter-level blast radius explicitly: modifying datacenter resource layout can disrupt all servers, LANs, and volumes within that datacenter simultaneously.
  • Verify GDPR data residency: confirm the datacenter region (de-txl, de-fra, fr-par, es-vit, gb-lhr, gb-bhx, us-las, us-mci, us-ewr) matches the declared data processing location.
  • Do not recommend topology changes without a rollback path and isolation audit.
  • Stay advisory - do not call DCD API endpoints or run Terraform apply.
  • Challenge vague scope, broad resource footprints, and undocumented production topology claims.
  • 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 topology review or formatting the final answer.
  • Safety checklist - use before advising any structural DCD change, NIC reconfiguration, or volume modification.
  • Official sources - use when grounding IONOS DCD topology concepts or checking the source list.

Response minimum

Return, at minimum:

  • the assessed topology scope and evidence level,
  • blast-radius classification for any proposed change,
  • GDPR data residency confirmation status,
  • rollback path requirements,
  • open questions blocking safe topology assessment.

What ships with it: 4 files

7.4 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most design frontend skills give in 508 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • cite official-source fallback if MCP tooling unavailable
  • require a current DCD topology snapshot before advising
  • flag datacenter-level blast radius explicitly
  • verify GDPR data residency before advising
  • require a rollback path before recommending topology changes
  • perform an isolation audit before recommending changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,452. 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.