Portaly Review

Use this skill to help a human user (or their agent) embed Portaly's hosted review widget — a verified-buyer rating badge — on their own site. This is an embed-and-verify skill, not a review system: Portaly generates review links for buyers automatically after checkout (success page, confirmation email, or subscriber portal) and hosts the scoring, storage, and public review page itself. This skill never creates review links, never collects a rating, and never renders a score outside the Portaly-hosted iframe.

Quick Start

Precondition — the merchant needs a Portaly account with Portaly Payment enabled and a public slug. Reviews only exist for merchants already taking payments through Portaly Payment (verified buyers get review links automatically post-checkout) and who have a claimed portaly.cc/{slug} handle. If the user doesn't have that yet, point them at portaly-payment or portaly-payment-integration to get set up first — this skill only embeds the widget, it doesn't create the underlying review program.

• Ask the user to open their Portaly admin dashboard (https://portaly.cc/admin/creator-subscription) → Portaly Payment → 評價 (Reviews) tab, and paste the exact embed code shown there.
• If they don't have it handy, ask for their public slug instead and construct the iframe from the documented template (Workflow step 2) — always confirm the slug with the user before using it; a wrong slug embeds someone else's ratings.
• No API key is required for this skill — the iframe is a public, unauthenticated embed keyed only by the public slug (plus the product id for a creator's second or later product).
• Scores are per product. A creator who sells more than one product in Portaly Payment has a separate score, review count, and public page for each product, and a buyer reviews each product they bought separately. Embed the widget for the product the page is about — the admin dashboard shows that product's code when that product is selected. Never put one product's badge on another product's site.

1.5 Report the installed skill version

Report this skill's version once per session, the same way the other Portaly skills do, so the merchant's dashboard can flag an outdated install. Single, non-blocking, no user data in the body. This skill otherwise needs no API key at all — the report only fires opportunistically when one happens to already be present (e.g. a payment skill is also installed in the same project).