hostinger-headless-connect
Skill from hostinger/claude-plugin
Install
npx skills add hostinger/claude-plugin --skill hostinger-headless-connect
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install hostinger@hostinger
This skill is part of the plugin “hostinger”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the hostinger-headless-connect skill do?
Description from the SKILL.md in the source repository.
Works with Hostinger
Questions about hostinger-headless-connect
What does the hostinger-headless-connect skill do?
Connect step for the Hostinger Headless flow — verify Node, run the bootstrap (reach the Hostinger MCP server + OAuth sign-in), then route to the matching coding-tool skill under tools/ so MCP tools and skills are available before the build steps run. Triggers: connect to Hostinger, set up the Hostinger connector, start a headless build.
How do I install hostinger-headless-connect?
In a terminal: npx skills add hostinger/claude-plugin --skill hostinger-headless-connect. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use hostinger-headless-connect?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is hostinger-headless-connect safe to use?
Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.
Which tool is hostinger-headless-connect for?
hostinger-headless-connect comes from the makers of Hostinger and helps your agent work with it.
More skills from hostinger/claude-plugin
Step 8 (deploy) of the Hostinger Headless flow. Archives the frontend source, then deploys through the connector's one-shot hosting_deploy (type nodejs — it uploads the source, runs npm install and the build …
Step 4 (content model) of the Hostinger Headless flow. Prepare phase: turns brief.md into a content helper (content-model.md) — fixed Title/Description plus a tailored generation prompt per section (Navigation, Pages, Articles) — …
Step 5 (design) of the Hostinger Headless flow. Derives three distinct design directions from brief.md (plus any reference sites and brand assets), lets the user pick one in a single question, checks …
Step 6 (frontend) of the Hostinger Headless flow. Builds the website that renders the backend's content.
Step 7 (validate) of the Hostinger Headless flow. OPTIONAL quick gate before deploy: every prior stage already self-verifies, so this is a fast confirmation (instance live + backend API answers with seeded …
Keep WordPress sites on Hostinger web hosting updated and secure: checks core, plugin and theme versions, known vulnerabilities and install health on one site or every site in the account, reports what …
Diagnose and fix a website on Hostinger web hosting (Shared, Cloud or Agency plans) that is down, slow, erroring, insecure or failing to build.
Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from …
Related skills in Agents & Workflows
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in …
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Teach the user a new skill or concept, within this workspace.
No description in the SKILL.md.
No description in the SKILL.md.
Ask which skill or flow fits your situation. A router over the skills in this repo.
No description in the SKILL.md.
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until …