Skills: Add latest API updates#1
Merged
Merged
Conversation
📝 WalkthroughWalkthroughThis PR adds ecommerce and horizons as new supported skills to the Hostinger Agent Skills platform. It includes marketplace and routing configuration, complete documentation for both new skills, and expansions to existing domains, billing, hosting, and reach skill guides. ChangesNew Skills Platform Expansion
🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (4)
skills/hosting/SKILL.md (4)
62-64: 💤 Low valueClarify WordPress polling filters in Core Concepts.
Line 64 mentions polling to "confirm readiness" but the actual endpoint at line 357 shows required filters (
username,domain). Explicitly mention these in the Core Concepts section so readers know upfront what parameters to filter by.Suggested revision for line 64:
Installation is asynchronous; poll `GET /api/hosting/v1/wordpress/installations` (filtering by `username` and `domain`) to confirm readiness.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/hosting/SKILL.md` around lines 62 - 64, Update the Core Concepts WordPress paragraph to explicitly state the required polling filters: change the sentence about polling `GET /api/hosting/v1/wordpress/installations` to note that you must filter by `username` and `domain` (matching the endpoint's required parameters) so readers know which query params to supply when confirming readiness of an installation.
511-514: 💤 Low valueClarify the WordPress
overwriteparameter.Line 514 mentions setting
overwrite: truewhen replacing existing files, but this parameter is not shown in the WordPress installation example (lines 340-354). Readers may wonder if this parameter is optional, required, or available.Consider either:
- Adding
"overwrite": falseto the install example to show it's an available option, or- Clarifying in the Troubleshooting note that this is an optional parameter for advanced scenarios.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/hosting/SKILL.md` around lines 511 - 514, The documentation mentions the "overwrite" parameter but the WordPress installation example (the JSON payload used in the install example and the section referencing GET /wordpress/installations) doesn't show it; add "overwrite": false to the example install payload to demonstrate the option is available (and optional), and update the troubleshooting note to state "overwrite" is optional and should be set to true only for intentional replacements of existing site files.
419-425: ⚡ Quick winFix inconsistent endpoint placeholder in Parked Domains API reference.
Line 425 shows the delete endpoint with
/parkedDomainas the path parameter placeholder, but the actual example at line 306 shows/example.net(the actual domain). This inconsistency creates ambiguity about what to substitute.Suggested revision for line 425:
| `DELETE` | `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parked_domain}` | Delete a parked domain |(Use
{parked_domain}to match the pattern shown in the example at line 306 whereexample.netis substituted.)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/hosting/SKILL.md` around lines 419 - 425, The DELETE endpoint placeholder in the Parked Domains section is inconsistent; update the path parameter in the table row for the DELETE method from `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parkedDomain}` to use the snake_case placeholder `/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parked_domain}` so it matches the example usage (`example.net`) and the project's placeholder naming convention.
330-333: 💤 Low valueClarify UUID placeholder in Node.js logs example.
Line 331 shows the build UUID as
3f9a...with an ellipsis, which could mislead readers about the actual format. Explicitly label this as a placeholder to avoid confusion.Suggested revision:
# Stream build logs while running (poll with from_line = previously returned line count) # Replace {uuid} with the actual build UUID from the creation response curl -X GET "https://developers.hostinger.com/api/hosting/v1/accounts/u123456789/websites/example.com/nodejs/builds/{uuid}/logs?from_line=0" \🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/hosting/SKILL.md` around lines 330 - 333, Replace the ambiguous "3f9a..." build identifier in the Node.js logs curl example with an explicit placeholder and a short inline note; update the URL segment "builds/3f9a.../logs" to "builds/{uuid}/logs" and add a preceding comment like "Replace {uuid} with the actual build UUID from the creation response" so readers know it's a placeholder (update the example in SKILL.md where the logs curl request appears).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@skills/hosting/SKILL.md`:
- Around line 62-64: Update the Core Concepts WordPress paragraph to explicitly
state the required polling filters: change the sentence about polling `GET
/api/hosting/v1/wordpress/installations` to note that you must filter by
`username` and `domain` (matching the endpoint's required parameters) so readers
know which query params to supply when confirming readiness of an installation.
- Around line 511-514: The documentation mentions the "overwrite" parameter but
the WordPress installation example (the JSON payload used in the install example
and the section referencing GET /wordpress/installations) doesn't show it; add
"overwrite": false to the example install payload to demonstrate the option is
available (and optional), and update the troubleshooting note to state
"overwrite" is optional and should be set to true only for intentional
replacements of existing site files.
- Around line 419-425: The DELETE endpoint placeholder in the Parked Domains
section is inconsistent; update the path parameter in the table row for the
DELETE method from
`/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parkedDomain}`
to use the snake_case placeholder
`/api/hosting/v1/accounts/{username}/websites/{domain}/parked-domains/{parked_domain}`
so it matches the example usage (`example.net`) and the project's placeholder
naming convention.
- Around line 330-333: Replace the ambiguous "3f9a..." build identifier in the
Node.js logs curl example with an explicit placeholder and a short inline note;
update the URL segment "builds/3f9a.../logs" to "builds/{uuid}/logs" and add a
preceding comment like "Replace {uuid} with the actual build UUID from the
creation response" so readers know it's a placeholder (update the example in
SKILL.md where the logs curl request appears).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3e0e1cb1-c5a0-4550-9491-7c93494ab2d2
📒 Files selected for processing (9)
.claude-plugin/marketplace.jsonREFERENCES.mdscripts/check-api-updates.pyskills/billing/SKILL.mdskills/domains/SKILL.mdskills/ecommerce/SKILL.mdskills/horizons/SKILL.mdskills/hosting/SKILL.mdskills/reach/SKILL.md
fizikiukas
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated skills to match the newest API version
Summary by CodeRabbit
Release Notes
New Features
Documentation