agentleFS
hostingerhostinger/hostinger-agent-skills/skills/ecommerce/SKILL.md

ecommerce

Skill28 starsChanged 5 months agoMITView on GitHub

Hostinger Ecommerce API for managing online stores. Use when listing the stores on an account or creating a new store (which also provisions a primary sales channel).

  • Sends data out

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. Bria-AI/bria-skill★ 74same name
    2. adoin/video-generation-skills★ 4same name
    3. nek1987/auto-agent-harness★ 4same name
    4. Abdox-menara/guard-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use a monitored company_email — it receives store-related notifications

    line 127
  2. Distinctive:

    Verify your API token is valid and not expired

    line 136
  3. Very specific:

    Check the Authorization: Bearer <token> header format

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hostinger Ecommerce

The Ecommerce API manages online stores associated with your Hostinger account. You can list existing stores and create new ones — creating a store also provisions a primary sales channel for it.

Table of Contents

  • Core Concepts
  • Common Patterns
  • API Reference
  • Best Practices
  • Troubleshooting
  • References

Core Concepts

Stores

A store is the top-level ecommerce entity tied to your account. Each store carries company details (name, email, country) and a default language used for the storefront.

Sales Channels

Every store has at least one sales channel — the surface through which products are sold. When you create a store, a primary sales channel is created alongside it. You can supply a sales_channel object (e.g., type: custom with an external_id) to link the store to an external system.

Common Patterns

List Stores

curl -X GET "https://developers.hostinger.com/api/ecommerce/v1/stores" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Paginate
curl -X GET "https://developers.hostinger.com/api/ecommerce/v1/stores?page=2" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Python SDK:

from hostinger_api import Hostinger

client = Hostinger(api_token="YOUR_API_TOKEN")

stores = client.ecommerce.stores.list()
for store in stores:
    print(store.name)

TypeScript SDK:

import { Hostinger } from "hostinger-api-sdk";

const client = new Hostinger({ apiToken: "YOUR_API_TOKEN" });

const stores = await client.ecommerce.stores.list();
for (const store of stores) {
  console.log(store.name);
}

PHP SDK:

use Hostinger\Api\HostingerApi;

$client = new HostingerApi('YOUR_API_TOKEN');

$stores = $client->ecommerce->stores->list();
foreach ($stores as $store) {
    echo $store->name . "\n";
}

Create a Store

curl -X POST "https://developers.hostinger.com/api/ecommerce/v1/stores" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My Store",
    "country_code": "us",
    "company_email": "owner@example.com",
    "company_name": "My Company",
    "language": "en",
    "sales_channel": {
      "type": "custom",
      "external_id": "ext-12345"
    }
  }'

A primary sales channel is created automatically with the store. The sales_channel object is optional — omit it to use the default.

API Reference

Stores

MethodEndpointDescription
GET/api/ecommerce/v1/storesGet stores (paginated via page)
POST/api/ecommerce/v1/storesCreate a store (also creates a primary sales channel)

Create Store Body

FieldTypeDescription
namestringStore name
country_codestringISO country code (e.g., us)
company_emailstringCompany contact email
company_namestringCompany name
languagestringDefault storefront language (e.g., en)
sales_channelobjectOptional. { "type": "custom", "external_id": "..." }

Best Practices

Store Setup

  • Set country_code and language to match your target market — they drive storefront defaults
  • Use a monitored company_email — it receives store-related notifications
  • Provide a sales_channel.external_id when integrating with an external system so you can reconcile records later

Listing

  • Paginate with page when an account has many stores rather than assuming a single page

Troubleshooting

401 Unauthorized

  • Verify your API token is valid and not expired
  • Check the Authorization: Bearer <token> header format

422 Unprocessable Content

  • Invalid country_code (use a valid ISO code like us) or malformed company_email
  • Missing or malformed sales_channel object when one is provided

Store Not Appearing After Creation

  • Re-list stores — propagation may take a moment
  • Confirm the create request returned a success status and a store ID

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.