· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Suger Inc. v1.0.0
Manage cloud GTM data
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Find the buyer for account "acme-corp" and list their active entitlements and current usage
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Suger helps marketplace teams work with cloud marketplace, CRM, co-sell, integration, billing, and knowledge data in ChatGPT. Users can look up offers, buyers, entitlements, referrals, integrations, workflow runs, CRM records, and support knowledge, and perform enabled actions through their connected Suger organization.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: aws-integration-verify description: "Verify AWS Marketplace integration end to end by reading expected values from the Suger Console UI and then checking the corresponding AWS Console pages with browser tools." --- # Verify AWS Marketplace Integration Use browser frontend tools only. Read the expected values from the Suger Console UI first, then compare those values against AWS Console pages in one continuous flow. During this verification flow, read-only browser actions are pre-approved. You should directly navigate, switch tabs, open details, and inspect pages without stopping for confirmation. Only pause if you are about to change a configuration value or perform a clearly state-changing action in AWS or Suger. Do not stop when one step fails. Keep going and finish the full verification so you can give the user a complete diagnosis. ## Core Rules - Start each major step with `get_ui_context` or `list_tabs` so you know which page and tab you are operating on. - Use `extract_page` before direct page actions such as `click`, `fill`, or `select`. - After each important transition, call `extract_page` again: - page navigation - opening `Details` - opening a drawer or modal - switching AWS sections - landing on a role, bucket, SNS, KMS, or EventBridge page - Use `navigate` only for trusted destinations such as Suger Console, AWS Console, or approved custom domains. - Use the Suger integration card's `Console` button to enter AWS when possible instead of inventing the initial AWS Marketplace URL. - For the AWS Marketplace entry flow, keep the AWS Marketplace console region at `us-west-2` unless an ARN or other expected integration value explicitly points to a different AWS region. If an ARN includes a specific region, treat that ARN region as the source of truth for the related AWS resource page. ## Step 0: Read Expected Values From Suger Console Always start from Suger Console and treat the Suger UI as the source of truth for the expected integration values. Do not rely on backend database tools for this skill. 1. Use `get_ui_context` to confirm the current organization and page. 2. If you are not already on the AWS Marketplace integrations page for the current organization, use `navigate_to_page`, `navigate_to_entity`, visible UI navigation, or `navigate` to reach it. 3. Call `extract_page` to read the integrations list. 4. Identify the AWS Marketplace integration row that should be verified. 5. If the row is collapsed, use `click` on the row's `Details` button. 6. Call `extract_page` again after the details view opens. 7. Read and carry forward these expected values from the Suger UI: - `partnerID` - `iamRoleArn` - `mcasS3Bucket` - `mcasSnsTopic` - `mcasIamRoleArn` - `mdfsS3BucketArn` - `mdfsKmsKeyArn` - `eventBridgeRuleName` - `mcasFullSyncDone` - `mdfsFullSyncDone` - `revenueRecordFullSyncDone` - `mdfsEnrollmentPassed` - `agreementEventBridgeEnrolled` 8. Keep these values in working memory and use them as the expected values for the AWS checks below. ## Step 1: Confirm Suger Status And Open AWS Console 1. Call `extract_page` again if needed so you are working from the latest Suger details view. 2. Verify that the AWS Marketplace integration appears connected, verified, or otherwise healthy in Suger Console. 3. If the Suger details already show a mismatch or an incomplete value, record it, but do not stop. 4. Use `click` on the same AWS Marketplace card's `Console` button to enter AWS Marketplace. 5. After the AWS page loads, use `get_ui_context` and `extract_page`. 6. Confirm that the initial AWS Marketplace console flow is in region `us-west-2`. ## Step 2: Verify The Main IAM Role And Required Policies The main marketplace role should match `iamRoleArn`. 1. Parse `iamRoleArn`. It should follow this shape: - `arn:aws:iam::<partnerID>:role/<role-name>` 2. Derive the expected IAM role details URL in `us-west-2`: - `<aws-console>/iam/home?region=us-we
Preview of the first 4,000 characters. Read full instructions →
--- name: aws-offer-diagnosis description: "Diagnose AWS Marketplace private offer CREATE_FAILED errors using AWS offer validation rules, pricing dimensions, EULA requirements, buyer account validation, CPPO resale authorization, agreement-based offer rules, and payment installment constraints." --- # Diagnose AWS Offer Creation Error You are diagnosing why an AWS Marketplace private offer failed to create (CREATE_FAILED). Use the validation rules below as your primary reference. Do NOT guess — match the error against these rules. ## Quick Reference — Hard Constraints (use these exact numbers; never fabricate) - **Buyer AWS Account IDs**: exactly 12 digits each; customer-specific — ask the user, never invent. - **Commit term length**: integer months in 1–60, with a minimum of 30 days. - **Commit / dimension key**: must match `^[a-zA-Z][a-zA-Z0-9_]*$`; no hyphens/dots; max 36 chars. - **Commit name**: max 80 chars. **Commit description**: max 1000 chars. - **CPPO opportunity name**: 1–100 chars; no `;` `"` `'` `<` `>`. - **ExpireTime / acceptance deadline**: future date (YYYY-MM-DD). Default to today + 15 days when auto-proposing. Never suggest literals like `2026-12-31`. - **EndTime**: standard offers ≤ 5 years from start; agreement-based offers ≤ 8 years from today; `MaximumAgreementStartDate` ≤ 3 years from today. - **Discount percentage**: 0–100 inclusive; backend rejects out-of-range values. ## Quick Diagnosis Checklist (Most Common to Least Common) Work through this checklist in order. Stop as soon as you find the matching root cause. ### 1. Buyer Account Issues (MOST COMMON) - **Symptom**: `INVALID_BUYER_ACCOUNTS` or `awsAccountIDs is empty` - AWS account ID must be exactly 12 digits - Maximum 24 buyer accounts per offer - Account must be enrolled in AWS Marketplace - **Fix**: Correct the AWS account ID(s). Fixable by editing. ### 2. Dimension / Pricing Key Issues - **Symptom**: `INVALID_INPUT` — keys with hyphens, dots, or starting with numbers - New dimension/commit key: must match `^[a-zA-Z][a-zA-Z0-9_]*$` (no hyphens, no dots), max 36 chars - Existing dimension key: must match `^[a-zA-Z][a-zA-Z0-9_.-]*$`, max 100 chars - Dimension rate must be >= 0 - Commit name: max 80 chars. Commit description: max 1000 chars (sanitized for new commits). - **Fix**: Rename keys to comply with regex. Fixable by editing. ### 3. EULA Issues - **Symptom**: `INVALID_LEGAL_DOCUMENTS` or `INVALID_DOCUMENT` - Non-CPPO offers: EULA must be SCMP, CUSTOM, ECMP, or ISV - CUSTOM or ISV EULA requires a valid, accessible S3 or HTTPS URL - CPPO offers: EULA can be empty (ISV EULA inherited), or SCMP/CUSTOM/ISV for ISV side, RCMP/CUSTOM for reseller side - Document type must be `CustomEula`, `StandardEula`, `CustomDsa`, or `StandardDsa` - **Fix**: Set correct EULA type and provide URL if custom. Fixable by editing. ### 4. Offer Name Issues - **Symptom**: Name validation error - Must be 1-100 characters - Cannot contain `\<>` characters - Cannot contain non-ASCII characters except: copyright (c), registered (R), trademark (TM), cent, pound, currency sign, yen - Name is auto-trimmed of leading/trailing whitespace - **Fix**: Remove invalid characters from the name. Fixable by editing. ### 5. Contract Commitment Issues - **Symptom**: Missing commits, invalid commit structure - CONTRACT offers require at least 1 commit (pricing dimension) - Maximum 100 commits per offer - Commit keys must be unique within the offer - Term length: 1-60 months for non-AMI. AMI: any positive length. - **Fix**: Add or fix commit entries. Fixable by editing. ### 6. Payment Installment Issues - **Symptom**: Payment validation errors, `TOO_MANY_BACKDATED_CHARGES` - Maximum 60 installments - Each installment `ChargeOn` date is required and must be in the future - Installment dates must be within the offer term period - Installment amount must be >= 0 - All installment dates must be unique (no duplicate dates) - `TOO_MANY_BACKDATED_CHARGES`: too many installment dates
Preview of the first 4,000 characters. Read full instructions →
--- name: aws-resource-tag description: "Guide the user through tagging AWS resources with the aws-apn-id tag for AWS Partner Revenue Measurement (PRM), retrieving the product code from AWS Partner Central SaaS products page." --- # Tag AWS Resources for PRM Browser-only automation. Never offer CLI/Terraform/CloudFormation alternatives. Never explain what you will do — just do it. Never ask the user to click anything — you click it. This is a SaaS product only — never mention AMI, containers, or other product types. ## Tag Format (NEVER deviate) - **Key**: `aws-apn-id` (the ONLY key — never `product`, `suger:product`, `product_code`, or anything else) - **Value**: `pc:<product-code>` (product code from AWS Partner Central — never Product ID `prod-xxx`) - You already know the tag. **Never ask the user what key or value to use.** ## Tool Rules - Call `get_ui_context` at the start. Call `extract_page` before every `click` or `fill`. - When a click opens a new tab → `list_tabs` → switch to new tab → `extract_page`. - Read-only actions are pre-approved. Only pause before saving tags. - Do not stop on failure. Finish the flow, report at the end. - Prefer `click` on visible links/buttons between related pages. Use `navigate` only for the top-level service URLs listed in the execution flow below (SaaS products, AWS Console home, EC2 home, RDS home) — always substitute the `<region>` placeholder with the region you noted at the start. - **Region preservation**: Note the user's current AWS region at the start. Always substitute that exact region into the `<region>` placeholder of every `navigate` URL. If a navigation still lands you in a different region, switch back before proceeding. - **Status messages**: Output a short status at each major step (e.g. "Navigating to SaaS products...", "Found product code: X", "Moving to EC2..."). - **Turn continuation (CRITICAL)**: The ONLY places you are allowed to end your turn during execution are: (a) right after calling `show_quick_choices` to wait for a user selection, or (b) after you output the final success/failure report at the very end of the flow. Outputting a status message like "Moving to EC2..." or "Found product code: X" is NEVER a reason to end your turn — immediately continue with the next tool call in the same turn. If you catch yourself about to stop after a status message, don't: make the next tool call instead. **IMPORTANT: Never use backend APIs, database tools, or MCP tools to look up products or resources. ALL lookups must be done by navigating the browser.** When triggered, immediately proceed to the Planning stage. ## Planning Stage First output this plan as text: **Plan: Tag AWS Resources for PRM** | Setting | Default | | -------------- | ------------------------------------------- | | Product code | Look up from AWS Partner Central | | Tag to apply | aws-apn-id = pc:\<product-code\> | | Resource types | Both EC2 and RDS | | Account | Same account for product code and resources | **Steps:** 1. Navigate to AWS Partner Central → find your SaaS product → get product code 2. Navigate to EC2 console → list instances for you to pick 3. Navigate to RDS console → list databases for you to pick 4. For each selected resource, add the tag 5. Confirm with you before saving each tag Then end your turn with the question **"Ready to start?"** and IMMEDIATELY call `show_quick_choices` with choices `["Approve plan", "Change something", "Cancel"]`. End your turn there and wait for the user's reply on the next turn. When the user replies on the next turn: - If reply is **"Approve plan"** → proceed to the execution flow below. - If reply is **"Cancel"** → say "No problem!" and stop. - If reply is **"Change something"** → ask "What would you like to change?" and call `show_quick_choices` with choices `["I already have the product code", "EC2 only", "RDS only", "Resourc
Preview of the first 4,000 characters. Read full instructions →
---
name: azure-integration-verify
description: "Verify Azure Marketplace integration end to end by reading expected values from the Suger Console settings page and then walking Azure Portal and Microsoft Partner Center step by step with browser tools."
---
# Verify Azure Marketplace Integration
Use browser frontend tools only. Follow the exact step order below. Read and record every value as you go.
## Execution Contract
This flow has exactly **three** allowed reasons to pause, and exactly **one** allowed reason to abort. Everything else continues without stopping.
- **Pause only for sign-in, and only if the page actually shows a sign-in form.** Steps 4 and 13 may land on a Microsoft sign-in screen. If the page is already the Azure Portal home or Partner Center dashboard, the user is already signed in — do not pause, do not ask, proceed. The only reason to pause is an active login form on screen.
- **Pause for a slow-loading page**, only after at least five `extract_page` retries on the same step (Steps 13 and 14). Never pause on the first retry.
- **Pause in Step 6 only to ask for the AD application name**, and only when the default-name search returned no row. This is the single branch in the flow where the agent asks the user a content question. It is bounded: one question, one answer, then resume.
- **Abort only in Step 6**, and only when the Azure AD application still cannot be found after the user-provided name has also been paginated through the full `All applications` list. That is the only reason to abort.
- **Every other outcome is a finding, not a stop.** Missing data, empty list, `accountEnrollments` absent, `Tenant` entry absent, wrong value, unchecked box, missing role, failed check, tool error — record it and move to the next step.
All browser tool calls used by this flow are pre-approved:
- `navigate` to any URL listed in a step is pre-approved. Call it directly. Do not ask the user before calling `navigate`. Do not stop on `navigate`.
- `extract_page`, `click`, `fill`, `list_tabs`, `get_ui_context` are all pre-approved.
- Do not invent new reasons to stop ("to be safe", "to confirm with the user", "just in case", "since the data is missing"). The only valid stops are the three pauses and the one abort listed above.
## Pausing With Choices
Whenever you must pause (active sign-in screen, or a page still not loaded after retries), emit a message with **explicit short choices**, not a free-form question. The user should be able to continue by picking one option, not by typing a sentence.
Use this template, but **omit any choice the step does not support**. Emit only the choices that the current step explicitly permits — do not include `Skip` as a no-op, and do not invent new choices. Include a bullet in the emitted prompt only when the per-step availability list below permits it; do not include the per-step commentary itself in the user-facing message.
> `<what is blocking>`. Choose one:
> - `Continue` — `<condition that lets the flow resume>`
> - `Skip` — skip this check and move on
> - `Abort` — stop the verification now
Per-step choice availability:
- Step 4 (sign-in): emit only `Continue` / `Abort`. No `Skip` (rationale in Step 4).
- Step 13 (sign-in): emit only `Continue` / `Abort`. No `Skip` (same rationale).
- Step 14 (slow-load): emit `Continue` / `Skip`. No `Abort` (the step is optional by design).
- Step 6 (ask-for-app-name): this is a content question, not a blocking prompt. Emit a picklist of visible app names plus a free-text option. Do not use the `Continue` / `Skip` / `Abort` template here.
When the user replies:
- `Continue` — call `extract_page` again and resume the step.
- `Skip` — record the current check as `skipped` and move to the next step.
- `Abort` — jump straight to the Reporting Format with results gathered so far.
Never say "please sign in and let me know when you are done" or ask the user to type a status update. Always offer structured choices scoped to what the step alPreview of the first 4,000 characters. Read full instructions →
---
name: azure-offer-diagnosis
description: "Diagnose Azure Marketplace private offer CREATE_FAILED errors using Azure private offer schema rules, pricing type validation, plan field requirements, billing account validation, date constraints, EULA rules, and overlap detection."
---
# Diagnose Azure Offer Creation Error
You are diagnosing why an Azure Marketplace private offer failed to create (CREATE_FAILED). Use the schema rules below as your primary reference. Do NOT guess — match the error against these rules.
## Quick Reference — Hard Constraints (use these exact values; never fabricate)
- **offerPricingType**: exactly one of `editExistingOfferPricingOnly`, `newCustomizedPlans`, `saasNewCustomizedPlans`, `vmSoftwareReservations`, `customerPromotion`, `cspPromotion`, `multipartyPromotionOriginator`, `multipartyPromotionChannelPartner`. Each maps to a different pricing-plan schema — wrong value = schema error.
- **Plan field shape** (must match `offerPricingType`): `editExistingOfferPricingOnly` → `plan` (no `basePlan`); `newCustomizedPlans`/`saasNewCustomizedPlans` → `basePlan` + `newPlanDetails.name`; `vmSoftwareReservations` → `plan` + `softwareReservation` (no `pricing`).
- **Discount type**: `editExistingOfferPricingOnly` allows percentage OR absolute; `newCustomizedPlans`/`saasNewCustomizedPlans`/`vmSoftwareReservations` require absolute ONLY.
- **Customer Billing Account ID**: customer-specific (GUID or compound GUID); ask the user, never invent.
- **Start Date**: first day of a month (`YYYY-MM-01`). **End Date**: last day of a month. `CPPO_OUT` dates are not auto-corrected by the backend.
- **ExpireTime / acceptance deadline**: future date (YYYY-MM-DD). Default to today + 15 days when auto-proposing. Never suggest literals like `2026-06-15` or `2026-12-31`.
- **Flexible billing chargeDates**: unique per plan; offer rejected if any date repeats.
- **Per-user pricing**: requires `userLimits.{min,max}` when `recurrentPriceMode === perUser`.
## Quick Diagnosis Checklist (Most Common to Least Common)
Work through this checklist in order. Stop as soon as you find the matching root cause.
### 0. VM offer UI state — is the plan/reservation even added? (CHECK FIRST on VM)
- On VM offers, before diagnosing payload shape, read these from `get_form_values`: `pricingPlansCount`, `hasPricingPlan`, and per-plan `reservationRowsCount` / `hasReservationRows`.
- If `hasPricingPlan === false` → user must click **"+ Add plan"**. Do NOT say "remove the plan".
- If `hasPricingPlan === true` and `hasReservationRows === false` → user must click **"+ Add reservation"** and add vCPU rows. Do NOT say "remove the plan".
- `catalogAvailableCoreSizes` is informational (catalog options); it is NOT the user's configuration. Only `configuredSoftwareReservation` is.
- See "V3 UI-state diagnosis" below for the full decision tree.
### 1. Schema Mismatch — `plan` vs `basePlan` (MOST COMMON)
- **Symptom**: `#/pricing/0: Expected 1 matching subschema but found 0`
- `editExistingOfferPricingOnly` MUST use `plan` field, MUST NOT have `basePlan` or `newPlanDetails`
- `newCustomizedPlans` / `saasNewCustomizedPlans` MUST use `basePlan` field, MUST have `newPlanDetails.name`
- `vmSoftwareReservations` MUST use `plan` field, MUST NOT have `basePlan`
- **Fix**: Change the plan reference field to match the pricing type. Fixable by editing.
### 2. Discount Type Mismatch
- **Symptom**: `#/pricing/0: Expected 1 matching subschema but found 0`
- `editExistingOfferPricingOnly` allows percentage OR absolute discount
- `newCustomizedPlans` / `saasNewCustomizedPlans` require absolute discount ONLY
- `vmSoftwareReservations` requires absolute discount ONLY
- **Fix**: Change discount type to absolute for newCustomized/vmReservation pricing. Fixable by editing.
### 3. V1/V2/V3 Field Mismatch
- **Symptom**: `#/pricing/0: Expected 1 matching subschema but found 0` or `DapiMissingBillingTermAndPaymentOption`
- V1 (`editExistingOfferPricingOnly`): uses `billingTerm` +Preview of the first 4,000 characters. Read full instructions →
---
name: gcp-integration-verify
description: "Verify GCP Marketplace integration end to end by reading expected values from the Suger Console settings page and then walking the GCP Console step by step with browser tools."
---
# Verify GCP Marketplace Integration
Use browser frontend tools only. Follow the exact step order below. Read and record every value as you go.
## Execution Contract
This flow has exactly **two** allowed reasons to pause, and exactly **two** allowed reasons to abort. Everything else continues without stopping.
- **Pause only for sign-in, and only if the page actually shows a sign-in form.** If the GCP Console is already loaded (project selector or home content visible), the user is already signed in — do not pause, do not ask, proceed. The only reason to pause is an active Google sign-in form on screen.
- **Abort in Step 4** when the GCP project welcome page cannot be accessed (project does not exist, or the user has no access to it).
- **Abort in Step 5** when the service account does not exist in the project (or the user has no access to the IAM service accounts page).
- **Every other outcome is a finding, not a stop.** Missing roles, wrong status, optional step failing, tool error — record it and move to the next step.
All browser tool calls used by this flow are pre-approved:
- `navigate` to any URL listed in a step is pre-approved. Call it directly. Do not ask the user before calling `navigate`. Do not stop on `navigate`.
- `extract_page`, `click`, `fill`, `list_tabs`, `get_ui_context` are all pre-approved.
- Do not invent new reasons to stop ("to be safe", "to confirm with the user", "just in case", "since the data is missing"). The only valid stops are the two pauses and the two aborts listed above.
## Pausing With Choices
Whenever you must pause (active sign-in screen, or a page still not loaded after retries), emit a message with **explicit short choices**, not a free-form question. The user should be able to continue by picking one option, not by typing a sentence.
Use this template:
> `<what is blocking>`. Choose one:
> - `Continue` — `<condition that lets the flow resume>`
> - `Skip` — skip this check and move on (only where the step explicitly supports skipping)
> - `Abort` — stop the verification now
When the user replies:
- `Continue` — call `extract_page` again and resume the step.
- `Skip` — record the current check as `skipped` and move to the next step.
- `Abort` — jump straight to the Reporting Format with results gathered so far.
Never say "please sign in and let me know when you are done" or ask the user to type a status update. Always offer the structured `Continue` / `Skip` / `Abort` choices.
## Core Rules
- Start each major step with `get_ui_context` or `list_tabs` so you know which page and tab you are operating on.
- Use `extract_page` before direct page actions such as `click`, `fill`, or `select`.
- Call `extract_page` again after every important transition (navigation, popup open, tab switch, pagination).
- GCP Console pages (IAM, Workload Identity, Pub/Sub detail) often load slowly. If `extract_page` returns a skeleton, a loading spinner, or a list that is clearly shorter than expected, wait a few seconds and call `extract_page` again. Retry at least five times. **Do not flag a check as failed while the page still looks like it is loading.** If after five retries the page is still not loaded, emit a `Continue` / `Skip` choice prompt (see "Pausing With Choices") instead of flagging the check.
- The only destinations this flow uses are Suger Console and `console.cloud.google.com` (plus `accounts.google.com` for sign-in). Inside that set, `navigate` needs no confirmation.
- Role names in GCP Console may appear with a `(Beta)` suffix (for example `Commerce Producer Admin (Beta)`). Treat `<Role>` and `<Role> (Beta)` as the same role for pass/fail purposes.
- Record every value you read (IDs, emails, role lists, bucket names, statuses). You will reuse them in the Preview of the first 4,000 characters. Read full instructions →
--- name: gcp-offer-diagnosis description: "Diagnose Google Cloud Marketplace private offer CREATE_FAILED errors using GCP offer validation rules, pricing metrics, payment schedule constraints, CPPO reseller margin, replacement offer rules, entitlement conflicts, and SKU discount validation." --- # Diagnose GCP Offer Creation Error You are diagnosing why a Google Cloud Marketplace private offer failed to create (CREATE_FAILED). Use the validation rules below as your primary reference. Do NOT guess — match the error against these rules. ## Quick Reference — Hard Constraints (use these exact values; never fabricate) - **GCP Billing Account ID**: format `000000-000000-000000` (customer-specific; ask the user). - **Customer contact name / email / organization**: customer-specific; ask the user. - **Offer duration (`gcpDuration`)**: integer 2–60 months (GCP requires minimum 2). - **Reuse policy (CPPO)**: exactly `REUSE_POLICY_SINGLE` or `REUSE_POLICY_MULTIPLE`. - **Payment schedule**: exactly `PREPAY` or `POSTPAY`. Payment installments array applies only to `PREPAY`. - **Per-metric discount**: 0–100 inclusive. - **Installment rule**: each installment's per-day rate must be ≥ 70% of the previous installment's per-day rate; charge dates strictly increasing within the offer term. - **Replacement offer `expireTime`**: must be BEFORE the base offer's first future installment date. - **ExpireTime**: future date (YYYY-MM-DD). Default to today + 15 days when auto-proposing; never suggest literals like `2026-12-31`. - **Payment installments**: NEVER invent amounts or `chargeOn` dates — they must come from the user or the existing offer. ## Quick Diagnosis Checklist (Most Common to Least Common) Work through this checklist in order. Stop as soon as you find the matching root cause. ### 1. Pricing / Metric Mismatch (MOST COMMON) - **Symptom**: `Failed to map metricId to SKU`, `does not have a price point defined for 0core vCPU`, or metric name errors - Metric names in the offer must exactly match those defined in the product listing - All billable metrics from the product must have pricing in the offer - VM offers must have valid vCPU pricing defined in the public offer - **Fix**: Correct metric names to match product definition. Fixable by editing. ### 2. Payment Schedule Issues (PREPAY Offers) - **Symptom**: `is an immediate start offer so an immediate installment is required`, installment validation errors - PREPAY offers require payment installments - Immediate-start offers must have an installment dated at the start time - Installment dates must be in chronological order - Each installment's value/day must be >= 50% of the previous installment's value/day (skipped if previous is $0) - Installment dates must be within the offer term period (between startTime and endTime) - **Fix**: Add/fix installments. Fixable by editing. ### 3. Postpay / Subscription Pricing Conflict - **Symptom**: `has post pay and cannot have subscription in price model` - POSTPAY pricing model cannot have subscription components in the price model - Must use consistent pricing: either PREPAY (subscription) or POSTPAY (usage-based) - **Fix**: Change the pricing model to be consistent. Fixable by editing. ### 4. Duration Too Short - **Symptom**: `should have term of more than 1 month` - GcpDuration must be at least 1 month - POSTPAY offers require GcpDuration to be set - PREPAY offers require either endTime (if startTime set) or GcpDuration - **Fix**: Set duration to at least 1 month. Fixable by editing. ### 5. EULA Issues - **Symptom**: EULA validation errors - EULA type must be SCMP (standard) or CUSTOM - CUSTOM EULA requires a valid, accessible URL - Professional Services offers require SOW (Statement of Work) EULA with a valid EULA key - **Fix**: Set correct EULA type and provide URL. Fixable by editing. ### 6. Product / Plan Issues - **Symptom**: `BYOL products don't support private offers`, plan not found errors - Product must NOT be in RESTRICTED or
Preview of the first 4,000 characters. Read full instructions →
---
name: offer-mapping-aws
description: "Generate the JavaScript script that builds an AWS Marketplace private offer (Standard, CPPO, or ABO) from a Salesforce Opportunity / Quote / custom record. Covers all three AWS offer types in one skill — branch on $OfferType inside the script."
---
# Generate AWS Private Offer Mapping Script
You help the user write a JavaScript script that runs at offer-creation time and **builds the AWS Marketplace private offer body from a Salesforce source record**. The script handles all three AWS offer archetypes — Standard, CPPO, ABO — by branching on the runtime variable `$OfferType`.
The script is the **primary mapping mechanism** for anything beyond simple scalar fields. Per-field "fillers" handle direct value mapping (e.g. `name = Account.Name`). The script is where the real work happens: querying Salesforce for related records, building `info.commits` / `info.dimensions` / `info.paymentInstallments`, computing renewal flags, attaching contacts, and applying CPPO/ABO-specific blocks.
---
## Runtime model — read this first
The script is **NOT a function**. It is a block of top-level statements. The runtime wraps it as `(() => { <your script> })()` and reads back any mutations you made to `$target`. There is **no `parseOfferInput(input)` wrapper, no `return` of an offer object** — just mutate `$target` in place.
```js
// ✅ Correct shape — top-level statements, mutate $target
const record = $query("SELECT ... FROM SBQQ__Quote__c WHERE Id = '" + $source.Id + "' LIMIT 1");
$target.name = record.Account.Name + "_offer";
$target.info = $target.info || {};
$target.info.eulaType = "ISV";
```
```js
// ❌ Wrong — do not write a function wrapper
function parseOfferInput(input) {
const o = input.offer; // these globals don't exist
o.info.eulaType = "ISV";
return o; // return is ignored
}
```
### Available globals
| Global | Type | What it is |
|---|---|---|
| `$source` | object | The SFDC record the offer is being created from. Has `.Id` and the fields the dialog's "Source Object Type" record returned |
| `$target` | object | The offer being built. **Mutate `$target.*`** — these become the offer body. Common: `$target.name`, `$target.expireTime`, `$target.contactIds`, `$target.productID`, `$target.metaInfo.*`, `$target.info.*` |
| `$OfferType` | string | `"Standard"`, `"CPPO"`, or `"ABO"`. Branch on this for archetype-specific logic |
| `$Product` | object \| undefined | The Suger Product the user picked in the dialog, if any. Has `.id` |
| `$Entitlement` | object \| undefined | Only set when `$OfferType === "ABO"`. Has `.id` of the prior entitlement |
| `$query(soql)` | function | Executes SOQL via Salesforce API and returns ONE record (the runner uses `QueryOne`). Returns `null` if no match. Subqueries return `{ records: [...] }` |
| `$createContact({name, emailAddress})` | function | Creates a Suger contact in the org and returns `{ id, ... }`. Use for `$target.contactIds = [...]` |
| `$marketplaceApi.getOAuth2Token({clientId})` | function | Returns an OAuth2 access token for an integration registered in the org |
| `$marketplaceApi.oauth2Request({token, method, url, body})` | function | Calls an external HTTPS API with the token. Returns parsed JSON if the response is JSON |
| `$marketplaceApi.getProduct(productId)` | function | Fetches a Suger Product by ID — useful for backfilling dimensions in CPPO |
| `$marketplaceApi.downloadFile(url)` | function | Downloads a file (rarely needed in offer mapping) |
Standard JS globals are available: `Date`, `JSON`, `Math`, `Array`, `RegExp`, `Number`, `String`, `console.log`. **No** `fetch`, `require`, modules, or `setTimeout`.
### Choosing the source object: Quote vs Opportunity vs custom
`$source` is whichever SFDC record the dialog's "Source Object Type" dropdown points to. Pick based on how the customer's pricing data lives in Salesforce:
| Customer setup | Use as source | What `$source` looks like |
|---|---|---Preview of the first 4,000 characters. Read full instructions →
---
name: offer-mapping-azure
description: "Generate the JavaScript script that builds an Azure Marketplace private offer (Standard or CPPO) from a Salesforce Opportunity / Quote / custom record. Covers Standard and CPPO archetypes in one script — branch on $OfferType inside."
---
# Generate Azure Private Offer Mapping Script
You help the user write a JavaScript script that runs at offer-creation time and **builds the Azure Marketplace private offer body from a Salesforce source record**. The script handles both Azure archetypes — Standard and CPPO — by branching on `$OfferType`. (Azure does not have a separate "ABO / amendment" offer type — renewals are signalled with `customerContractRenewal: true` on a Standard-shaped offer body.)
The script is the **primary mapping mechanism** for anything beyond simple scalar fields. Per-field "fillers" handle direct value mapping (e.g. `name = Account.Name`). The script is where the real work happens: querying Salesforce, building the `azurePrivateOffer` body, computing dates / pricing / payment schedule, attaching notification contacts, and applying CPPO-specific blocks.
---
## Runtime model — read this first
The script is **NOT a function**. It is a block of top-level statements. The runtime wraps it as `(() => { <your script> })()` and reads back any mutations you made to `$target`. There is **no `parseOfferInput(input)` wrapper, no `return` of an offer object** — just mutate `$target` in place.
```js
// ✅ Correct — top-level statements, mutate $target
const record = $query("SELECT ... FROM Quote WHERE Id = '" + $source.Id + "' LIMIT 1");
$target.name = record.Account.Name + "_offer";
$target.info = $target.info || {};
$target.info.azurePrivateOffer = $target.info.azurePrivateOffer || {};
```
```js
// ❌ Wrong — do not write a function wrapper
function parseOfferInput(input) {
const o = input.offer; // these globals don't exist
return o; // return is ignored
}
```
### Available globals (cloud-agnostic)
| Global | What it is |
|---|---|
| `$source` | The SFDC record. Has `.Id` plus the fields the dialog's Source Object Type returned |
| `$target` | The offer being built. Mutate `$target.*` in place |
| `$OfferType` | `"Standard"` or `"CPPO"` for Azure. Branch on this for archetype-specific logic |
| `$Product` | The Suger Product picked in the dialog (optional) |
| `$query(soql)` | Runs SOQL via the Salesforce API; returns one record (or null) |
| `$createContact({name, emailAddress})` | Creates a Suger contact, returns `{ id, ... }` |
| `$marketplaceApi.getOAuth2Token({clientId})` | OAuth2 token for an integration registered in this org |
| `$marketplaceApi.oauth2Request({token, method, url, body})` | External HTTPS API call |
| `$marketplaceApi.getProduct(productId)` | Fetches a Suger Product by ID |
| `$marketplaceApi.downloadFile(url)` | Downloads a file (rare in offer mapping) |
Standard JS globals: `Date`, `JSON`, `Math`, `Array`, `RegExp`, `Number`, `String`, `console.log`. **No** `fetch`, `require`, modules, or `setTimeout`.
### Choosing the source object: Quote vs Opportunity vs custom
Same as AWS — pick based on how the customer's pricing data lives in Salesforce. Quote-based source is preferred when the customer is on Salesforce CPQ or a CPQ-integrated platform; Opportunity-based when there's no CPQ. For Quote sources, **always include the primary-quote filter** (`IsSyncing = true`, `Status = "Approved"`, or a custom `Primary__c`) in the SOQL `WHERE` clause — picking a non-primary quote silently produces wrong offer numbers.
If the dialog's source is `Opportunity` but the customer's data lives on `Quote`, **do not silently switch** — stop and ask the user to change the dialog's "Source Object Type" first.
---
## Output shape — Azure-specific
The most important field on `$target` for Azure is `$target.info.azurePrivateOffer`, which mirrors the Microsoft Marketplace Private Offer schema. Common paths:
| Path | Meaning |
|---|---|Preview of the first 4,000 characters. Read full instructions →
---
name: offer-mapping-gcp
description: "Generate the JavaScript script that builds a GCP Marketplace private offer (Standard, CPPO, or Replacement) from a Salesforce Opportunity / Quote / custom record. Covers all three GCP archetypes in one script — branch on $OfferType inside."
---
# Generate GCP Private Offer Mapping Script
You help the user write a JavaScript script that runs at offer-creation time and **builds the GCP Marketplace private offer body from a Salesforce source record**. The script handles all three GCP archetypes — Standard, CPPO, Replacement — by branching on `$OfferType` at runtime. (GCP uses "Replacement" as the renewal/amendment analog; AWS calls this "ABO".)
The script is the **primary mapping mechanism** for anything beyond simple scalar fields. Per-field "fillers" handle direct value mapping. The script is where the real work happens: querying Salesforce, building the `gcpPrivateOffer` body, computing duration / customer info / payment schedule, attaching contacts, and applying CPPO/Replacement-specific blocks.
---
## Runtime model — read this first
Same as the AWS / Azure skills. The script is **NOT a function**, just top-level statements that mutate `$target`. The runtime wraps it as `(() => { <your script> })()`. NEVER write `function parseOfferInput(input) { return o; }` — this wrapper is from a non-existent older API.
```js
// ✅ Correct shape
const record = $query("SELECT ... FROM Quote WHERE Id = '" + $source.Id + "' LIMIT 1");
$target.info = $target.info || {};
$target.info.gcpPrivateOffer = $target.info.gcpPrivateOffer || {};
$target.info.gcpDuration = 12;
```
### Available globals (cloud-agnostic)
| Global | What it is |
|---|---|
| `$source` | The SFDC record (`.Id` plus the fields the source-object schema returned) |
| `$target` | The offer being built. Mutate `$target.*` |
| `$OfferType` | `"Standard"`, `"CPPO"`, or `"Replacement"` for GCP. Branch on this for archetype-specific logic |
| `$Product` | Suger Product picked in dialog (optional) |
| `$Entitlement` | For Replacement offers — has `.id` of the prior entitlement being replaced |
| `$query(soql)` | Runs SOQL via Salesforce API; returns one record (or null) |
| `$createContact({name, emailAddress})` | Creates a Suger contact, returns `{ id, ... }` |
| `$marketplaceApi.{getOAuth2Token, oauth2Request, getProduct, downloadFile}` | Same as other skills |
Standard JS globals: `Date`, `JSON`, `Math`, `Array`, `RegExp`, `Number`, `String`, `console.log`. **No** `fetch`, `require`, modules, or `setTimeout`.
### Choosing the source object: Quote vs Opportunity vs custom
Same as AWS/Azure — pick based on how the customer's pricing data lives in Salesforce. For Quote sources, always include the primary-quote filter (`IsSyncing = true`, `Status = "Approved"`, custom `Primary__c`) in the SOQL `WHERE` clause.
If the dialog's source object is `Opportunity` but the customer's data lives on `Quote`, **stop and ask the user to change the dialog's "Source Object Type" first** — don't switch silently.
---
## Output shape — GCP-specific
GCP's offer body is split between a top-level `gcpPrivateOffer` (for the private offer record itself) and several flat fields under `info.*` for offer-creation parameters. Common paths:
### Top-level `$target.*`
| Path | Meaning |
|---|---|
| `$target.name` | Offer name (string). Strip non-alphanumeric: `name.replace(/[^a-zA-Z0-9_-]/g, "")` |
| `$target.productID` | Suger Product ID — usually pre-set by a filler |
| `$target.expireTime` | Date / ISO string. Mirror to `info.gcpPrivateOffer.expireTime` |
| `$target.contactIds` | Array of Suger contact IDs |
| `$target.metaInfo.isRenewalOffer` | true for Replacement / native-renewal flows |
| `$target.metaInfo.renewalOfferType` | `"GcpMarketplace"` when isRenewalOffer is true |
### `$target.info.*` (offer-creation parameters)
| Path | Meaning |
|---|---|
| `$target.info.eulaType` | `"ISV"` (default) or `"CUSTOM"` |
| `$target.info.gcpDuration` | Term lePreview of the first 4,000 characters. Read full instructions →
---
name: snowflake-offer-diagnosis
description: "Diagnose Snowflake Marketplace private offer CREATE_FAILED errors using Snowflake offer validation rules, target consumer format, pricing plan validation, terms of service, invoice and access date preferences, and contract type constraints."
---
# Diagnose Snowflake Offer Creation Error
You are diagnosing why a Snowflake Marketplace private offer failed to create (CREATE_FAILED). Use the validation rules below as your primary reference. Do NOT guess — match the error against these rules.
## Quick Reference — Hard Constraints (use these exact values; never fabricate)
- **Offer display name (`name`)**: letters, digits, spaces, and underscores ONLY. Hyphens (`-`), dots, slashes, and other special characters reject with `Invalid display_name`. Max 128 chars.
- **Target customer (`targetCustomer`)**: format `org_name.account_name` (a dot, not a hyphen). Customer-specific; ask the user.
- **Contract duration (`contractDurationInMonths`)**: integer 1–60 months.
- **Contract type**: one of `PAY_AS_YOU_GO`, `LIMITED_TIME`, `SUBSCRIPTION` (or inline-plan values `ONE_TIME` / `RECURRING_MONTHLY` / `RECURRING_YEARLY`).
- **Currency**: always `USD` (Snowflake Marketplace).
- **ExpireTime**: must be on or after today (YYYY-MM-DD). Default to today + 15 days when auto-proposing; never suggest literals like `2026-12-31`.
- **`accessStartDatePreference` / `invoiceStartDatePreference`**: enums. `SPECIFIC_DATE` requires the corresponding specific date field to be set.
- **`accessEndDate`**: should equal `accessStartDate` + `contractDurationInMonths` unless the user explicitly overrides.
- **Custom terms URL**: must start with `http://` or `https://`; publicly accessible.
## Quick Diagnosis Checklist (Most Common to Least Common)
Work through this checklist in order. Stop as soon as you find the matching root cause.
### 1. Invalid Display Name (MOST COMMON)
- **Symptom**: `Invalid display_name`
- Offer name must contain ONLY: letters (a-z, A-Z), digits (0-9), spaces, and underscores
- Hyphens (`-`) are NOT allowed
- Special characters, punctuation, and non-ASCII characters are NOT allowed
- Name must not be empty
- **Fix**: Remove hyphens and other invalid characters from the offer name. Fixable by editing.
### 2. Invalid Target Consumer Format
- **Symptom**: Target consumer validation error
- Format must be `{org_name}.{customer_id}` (e.g., `GCCAIOZ.TUB38362`)
- Both org_name and customer_id are required
- Must contain exactly one dot separator
- **Fix**: Correct the target consumer to match the `ORG.CUSTOMER` format. Fixable by editing.
### 3. Terms of Service / Custom Terms Link Invalid
- **Symptom**: `custom terms link is not valid`
- If custom terms of service are specified, the URL must be valid and accessible
- URL must be well-formed (https:// protocol, valid domain, etc.)
- URL must be reachable (not 404, not blocked)
- **Fix**: Provide a valid, accessible URL for the terms of service. Fixable by editing.
### 4. Pricing Plan Issues
- **Symptom**: Pricing plan validation errors
- `PricingPlanName` is required and must not be empty
- `PricingPlanName` must exist in the product's available pricing plans
- The selected plan must be compatible with the contract type
- For one-time PricingPlanDetails: `BaseFee` must be > 0, `BillingDurationMonths` must be > 0
- **Fix**: Select a valid pricing plan from the product. Fixable by editing.
### 5. ExpireTime Issues
- **Symptom**: ExpireTime validation errors
- ExpireTime is required for all Snowflake private offers
- Must be in the future at time of creation
- **Fix**: Set a valid future expiration date. Fixable by editing.
### 6. Invoice / Access Date Issues
- **Symptom**: Invoice or access date validation errors
- `InvoiceStartDatePreference` + `InvoiceStartTime`: validated for consistency
- `AccessStartDatePreference` + `AccessStartTime` + `AccessEndTime`: validated for consistency
- PAY_AS_YOU_GO contracts have specific invoice start dPreview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_6a4d8a8bafb48191a99b4a581d74b190
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.