hostinger-dns-autonomy

Community

Keep DNS changes API-driven, not hPanel.

Authorwagnerra23
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill prevents unsafe or inefficient escalation by blocking requests to perform Hostinger DNS changes via the hPanel UI and instead enforcing the documented API/CLI-first procedure using the correct Hostinger DNS API token and guardrails.

Core Features & Use Cases

  • Tier A blocking policy: Stops agents from asking Wagner to edit DNS records through Hostinger UI whenever an API/CLI path exists.
  • Secret-first retrieval (Path 0 memory index): Forces the agent to consult the canonical secret index and only fall back to other known token locations if the index lacks an entry.
  • Token validity handling: Differentiates between inaccessible tokens (Tier 0 gap) and stale/expired tokens (secret rotation), including explicit validation via Hostinger DNS API and safe next actions.
  • Canonical A-record workflow: Provides the production-ready curl recipe that sets DNS records with overwrite protection (overwrite: false) and includes propagation validation steps.

Quick Start

Ask the agent to create the needed Hostinger DNS A record using the documented Hostinger DNS API token without involving hPanel, and let the Skill enforce token lookup, rotation rules, and propagation validation.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: hostinger-dns-autonomy
Download link: https://github.com/wagnerra23/oimpresso.com/archive/main.zip#hostinger-dns-autonomy

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.