Hustle Got Real

View saved version →

---
name: find-products-to-sell
description: Find supplier products a Hustle Got Real seller could list, from HGR's recommendations or similar to an existing listing, and add the chosen ones to a store. Use when the user asks for product ideas, products to sell, or products like one of theirs.
---

Use this skill to help the user find products and add the ones they choose. Explicit user instructions always take priority over these steps.

## 1. Pick the store

Call `hgr_list_stores`. If the user did not name a store and has more than one, ask which store to use. Use that store's `channelOAuthId` in every later call.

## 2. Find products

Choose the source that matches the request:

- **Recommended products:** call `hgr_list_recommended_products` with a `limit` close to what the user asked for (default 10). Present title, supplier price, suggested selling price and estimated profit, and link each title to its supplier page. Search filters are not available; sort or shortlist the returned items yourself if the user asks.
- **Products like one of theirs:** get the reference listing with `hgr_list_active_listings` or `hgr_get_listing_details`. Call `hgr_list_suppliers` for the store's country, then search the web only on those supplier sites for similar products. For each, give name, supplier, price and the exact product link. Never invent links or prices; if you cannot verify one, leave it out.

## 3. Add the chosen products

- Before adding anything, confirm the exact products, the store, and whether to hold them for review. Default to review before publishing unless the user says otherwise.
- For recommended products, call `hgr_publish_recommended_products` with each product's `id` and `title`, plus `needsReview`, `confirmed=true` and `impactConfirmed=true`.
- For supplier links, call `hgr_add_products_from_links` with the `urls`, `reviewBeforePublishing`, `confirmed=true` and `impactConfirmed=true`. To let the user review links visually first, call `hgr_open_store_manager` with `view` set to `add` and the `urls` instead.
- Leave `optimizeTitle` and `optimizeDescription` off unless the user asks for AI rewriting; it uses their AI tokens.

## 4. Report the result

- For links, report each status (for example Processed, DuplicatedUrl, InvalidUrl or NoQuota) and what it means.
- For recommended products, call `hgr_get_recommended_products_status` after a short wait and report any errors, such as a forbidden word.
- Tell the user where the products will appear: pending listings when held for review, or live after publishing.

Stop and explain if the store needs reconnecting, the quota is full, or a tool returns an error. Do not retry in bulk.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-started
description: Get a new Hustle Got Real user oriented in ChatGPT. Use when the user first connects Hustle Got Real, asks what it can do, or asks to see their stores or store overview.
---

Use this skill to orient the user in their Hustle Got Real (HGR) account. Explicit user instructions always take priority over these steps.

1. Call `hgr_list_stores` to read the user's stores. If the call asks to connect or reconnect, tell the user to connect Hustle Got Real in ChatGPT and stop.
2. If the user has no stores, explain that they need to connect a marketplace store in Hustle Got Real first (https://app.hustlegotreal.com) and stop.
3. Call `hgr_open_store_manager` so the user can see their store overview in the app.
4. Summarize in a few lines:
   - How many stores they have, and each store's marketplace and country when there are only a few.
   - Stores whose `connectionStatus` is "needs reconnecting". Say they must be reconnected in Hustle Got Real; ChatGPT cannot reconnect them.
5. Offer three next steps the plugin supports: review or edit listings, find products to sell, or check orders and sales.

Rules:
- Report only what the tools return. Do not guess listing counts, sales or connection states.
- Do not change anything in this workflow; it is read-only.
- Do not ask for passwords, API keys or marketplace credentials.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: manage-listings
description: Review, find, edit, publish or hold Hustle Got Real listings. Use when the user asks about their active, pending or ended listings, wants to change a price, quantity, title or note, or wants to publish or pause a pending listing.
---

Use this skill for listing questions and changes. Explicit user instructions always take priority over these steps.

## Find listings

1. Call `hgr_list_stores` and resolve the store. Ask which one if several match.
2. Use the list tool for the state the user means: `hgr_list_active_listings`, `hgr_list_pending_listings` or `hgr_list_ended_listings`. Request only the `fields` you need, and use `sortBy`, `sortDirection` and `limit` for rankings such as "most expensive" or "lowest stock".
3. For one listing's full detail, variations and images, call `hgr_get_listing_details` with its `productId`. For trends, use `hgr_get_listing_price_history` or `hgr_get_listing_stock_history`.
4. Answer from the returned rows, and mention when results were limited.

## Change a listing

1. Identify the exact listing by `productId` (and `variationProductId` for one variation). If more than one listing could match, list the candidates and ask.
2. State the exact change: field, current value if known, and new value. If the user's request already states the exact change, that is their confirmation; otherwise ask before changing anything.
3. Call `hgr_update_listing` with only the fields that change and `confirmed=true`.
4. Report what changed. Changes reach the marketplace on HGR's normal sync schedule, so do not claim the marketplace already shows them.

## Pending listings

- To publish one now, confirm first, then call `hgr_publish_pending_listing` with its `pendingListingId` and `confirmed=true`.
- To hold one for manual review instead of automatic publishing, confirm first, then call `hgr_move_pending_listing_to_review` with its `pendingListingId` and `confirmed=true`.
- If a call returns `success: false`, say the change was not applied and suggest checking the listing in Hustle Got Real.

Never delete, end or bulk-change listings with this plugin; it has no tools for that. Do not change prices across many listings unless the user explicitly asks for each one.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: store-health-check
description: Give a Hustle Got Real seller a read-only review of one store, covering listings, pending items, recently ended listings, orders and sales over a period. Use when the user asks how their store is doing, for a daily or weekly review, or what needs attention.
---

Use this skill for a read-only store review. Explicit user instructions always take priority over these steps.

1. Call `hgr_list_stores` and resolve the store; ask if several match. If its `connectionStatus` is "needs reconnecting", say so first, because listings will not sync until it is reconnected in Hustle Got Real.
2. Gather, using small limits:
   - Active listings: `hgr_list_active_listings` with `fields` such as productId, title, salePrice, stock, sourcePrice and sourceStock, sorted by stock ascending, to spot listings at or near zero stock.
   - Pending listings: `hgr_list_pending_listings`, noting items waiting for review or in an error state.
   - Ended listings: `hgr_list_ended_listings` sorted by `terminatedOn` descending to show what ended recently.
   - Sales: `hgr_get_sales` grouped by day for the period the user asked about, default the last 7 days.
   - Orders: `hgr_search_orders` for recent orders.
3. Report in short sections: needs attention, listings, orders and sales. Give counts and a few concrete examples with product IDs.
4. Suggest next steps the plugin can do, such as editing a listing or adding products, and ask before doing any of them.

Rules:
- This workflow never changes anything.
- Use only returned numbers. If a tool returns nothing, say there is no data for that period rather than estimating.
- Do not reveal buyer names, addresses or contact details.

Referenced files: 1 — file references are metadata, not package contents.