hello-retail-unmanaged
v1.0.1Skills and reference docs that teach AI coding assistants the intricacies and edge cases of Hello Retail's public REST APIs, for building custom frontend solutions.
By Hello RetailLicense: UNLICENSED0 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 9 skill or MCP entries
- Source updated
- Sep 29, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install hello-retail-unmanaged for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install hello-retail-unmanaged@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/helloretail/pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/hello-retail-unmanaged/.
Plugin files
├── .claude-plugin/plugin.json├── skills/cart-tracking-api/SKILL.md├── skills/click-tracking-api/SKILL.md├── skills/conversion-tracking-api/SKILL.md├── skills/pages-api/SKILL.md├── skills/recommendations-api/SKILL.md├── skills/search-api/SKILL.md├── skills/tracking-user-id/SKILL.md├── skills/troubleshooting-with-hello-retail-mcp/SKILL.md└── skills/view-tracking-api/SKILL.md
Included Skills9
Use when a shopper's cart changes (item added, removed, quantity changed, or cart cleared) - covers the Cart tracking REST API (core.helloretail.com/serve/collect/cart), why the platform-agnostic Hello Retail SDK does NOT handle this automatically (unlike some platform-specific plugins), and known gotchas including a cart-specific quirk in how the opted-out sentinel behaves.
Use when a shopper clicks a product tile built from Hello Retail Search, Recommendations, or Pages data - covers the Click tracking REST API (core.helloretail.com/serve/collect/click), how to send the tile's trackingCode back as the opaque source value, and known gotchas.
Use when a shopper completes a purchase - covers the Conversion tracking REST API (core.helloretail.com/serve/collect/conversion), why the platform-agnostic Hello Retail SDK does NOT handle this automatically (same relationship as Cart tracking), and known gotchas including per-line-item quantity, which Cart tracking does not have.
Use when building a custom frontend against Hello Retail's public Pages REST API (core.helloretail.com/serve/pages/{key}) - covers category/brand/collection listing pages, params vs products filtering, the required firstLoad flag, hierarchy filter syntax, and known gotchas.
Use when building a custom frontend against Hello Retail's public Recommendations REST API (core.helloretail.com/serve/recoms) - covers Managed vs Unmanaged recommendation requests, personalization via trackingUserId, and known gotchas.
Use when building a custom frontend against Hello Retail's public Search REST API (core.helloretail.com/serve/search) - covers request/response shapes, config states, filters/sorting, personalization, and known gotchas.
Use whenever a custom frontend needs a trackingUserId (Search personalization, Click tracking, Recommendations, Pages, or any other Hello Retail endpoint that takes one) but the page has no Hello Retail SDK loaded to set the hello_retail_id cookie - covers minting one via the REST API, caching it correctly, and the shared cookie-naming convention.
Use when a Hello Retail REST API integration isn't behaving as expected (missing/wrong results, errors, timeouts) - Hello Retail's own MCP tools (API log, audit log) show what actually happened server-side, so check them before assuming the bug is in your own request code.
Use when a shopper visits a product detail page and you need to know whether View tracking is the integration's responsibility or the Hello Retail SDK's - covers the View tracking REST API (core.helloretail.com/serve/collect/pageview) for when the SDK isn't present (or has automatic tracking disabled), and known gotchas.
Plugin manifests1
{
"name": "hello-retail-unmanaged",
"displayName": "Hello Retail (unmanaged)",
"version": "1.0.1",
"description": "Skills and reference docs that teach AI coding assistants the intricacies and edge cases of Hello Retail's public REST APIs, for building custom frontend solutions.",
"author": {
"name": "Hello Retail",
"email": "[email protected]"
},
"homepage": "https://developer.helloretail.com",
"repository": "https://github.com/helloretail/plugins",
"license": "UNLICENSED",
"keywords": [
"skills",
"hello-retail",
"rest-api",
"search",
"recommendations",
"pages",
"click-tracking",
"view-tracking",
"cart-tracking",
"conversion-tracking",
"frontend"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[hello-retail-unmanaged on Agent Plugins Marketplace](https://pluginsmp.com/plugins/hello-retail-unmanaged)