本文へ移動
cccskills
無料GitHub で公開

agentexchange-publishing

Use when an ISV or consulting partner is creating, pricing, publishing, or maintaining an AgentExchange listing through the Partner Console — covers the listing plan, the 5-step Listing Builder workflow (Fill in the Basics, Set Pricing, Add Details, Link Your Solution, Grow Your Business), commercialization models (revenue share vs. annual fee vs. freemium), AgentExchange Checkout setup (Stripe connection, pricing plans, fees, geographic eligibility), Private Offers, Security Review gating, and post-publish listing updates. NOT for building the agent or managed package itself (use agentforce/agentforce-agent-creation and devops/second-generation-managed-packages), NOT for LMA/Trialforce licensing internals (use devops/isv-license-management-and-trialforce), and NOT for the customer-side install experience.

インストール方法を見る

含まれるファイル(7)

  • SKILL.md14.7 KB
  • references/examples.md7.4 KB
  • references/gotchas.md3.9 KB
  • references/llm-anti-patterns.md5.3 KB
  • references/well-architected.md4.0 KB
  • scripts/check_agentexchange_publishing.py8.2 KB
  • templates/agentexchange-publishing-template.md4.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

AgentExchange Publishing

This skill activates when a Salesforce partner needs to take a solution — an agent, agent actions, an app, or a consulting service — to market on AgentExchange, Salesforce's unified marketplace for "apps, AI agents, Bolt solutions, Flow solutions, Lightning data, components, and more." It covers the partner-side workflow: the listing plan, the Partner Console Listing Builder, commercialization models, AgentExchange Checkout, Private Offers, and post-publish maintenance.


Before Starting

Gather this context before working on anything in this domain:

  • Listing type. A packaged-solution listing uses the full 5-step Listing Builder flow; a consultant listing uses a shorter 3-step flow (Fill in the Basics, Add Details, Grow Your Business) with no pricing or solution-linking steps.
  • Security Review status. For a packaged solution, the application must pass Salesforce's Security Review and Assessment under the AgentExchange ISV Program Track before it can be distributed from a listing. If the review hasn't passed, that is the critical path — not the listing copy.
  • Where payment happens. AgentExchange Checkout (on-platform payment via Stripe) has hard eligibility gates: the partner company must be based in the United States, United Kingdom, or a European Union country; the solution must be distributed in a managed package; and Checkout can't be used with OEM apps. Off-platform billing uses the partner's own payment systems plus the Channel Order App (COA).
  • Publishing permissions. Publishing packages requires both the Create AgentExchange Packages and Upload AgentExchange Packages permissions; customers installing need admin rights or the Download AgentExchange Packages permission.
  • Maturity honesty. The official docs describe the Partner Console, Listing Builder, Checkout, and Private Offers as current, operating functionality without attaching a GA/Beta/Pilot label. Do not assert a maturity level the docs don't state.

Core Concepts

The Partner Console

The AgentExchange Partner Console is "the one-stop shop to create, publish, manage your listings, and much more" — the complete business management site for ISV partners and consultants. Partners reach it by logging into the Partner Community and clicking Publishing; authentication into the console is automatic. Its main tabs:

  • Home — Company Info, Notifications (things to fix or review), Your Analytics (tile views, tile hovers, lead events), and Your Listings.
  • Listings — access in-progress and published listings, and create new ones.
  • Technologies — solution connections, trial templates, License Management Org registration, and security reviews.

The listing plan

Before touching the Listing Builder, partners prepare a listing plan (also called a business plan): "the basic details of your listing plus your pricing model and pricing plans." The plan is submitted to the partner's Salesforce account representative for business approval. Treat it as a real artifact — this skill's templates/agentexchange-publishing-template.md is a fill-in workbook for it.

Commercialization models

For paid solutions, partners choose between:

  • Revenue Share — share 15% of the app's revenue with Salesforce.
  • Annual Fee — a fixed, upfront, yearly fee based on the number of customer orgs and/or users.
  • Freemium — free to use up to specific feature-based limits, with paid expansion.

Off-platform paid deals run through the Channel Order App (COA) and the partner's own payment systems. On-platform payment is the separate Checkout capability below.

AgentExchange Checkout

Checkout is AgentExchange's integrated payment platform: customers buy the solution directly from the listing with a credit card or bank transfer. Setup is per-listing, in the Partner Console: create a Stripe account, connect it to the listing, and add pricing plans. Key documented parameters:

ParameterDocumented behavior
Partner eligibilityCompany based in the US, UK, or an EU country; English only, eligible partners
Customer reachPayments accepted from any country Stripe supports
Solution constraintsMust be distributed in a managed package; can't be used with OEM apps
Plan shapesOne-time and subscription plans; charged per user or per company
Revenue share15% on bank transfers; 15% + $0.30 per transaction on credit cards
FeesNo minimum revenue share; no setup fees, monthly service charges, or card storage fees
TaxUS partners submit a W-9; EU/UK partners can enable VAT; US sales tax supported
IntegrationsWorks with the License Management App (LMA) and the Checkout Management App (CMA)

Private Offers

Partners can activate a Request Private Offer button on a listing so customers "initiate a private offer conversation without leaving the marketplace, helping shorten the sales cycle" — negotiated terms and pricing without an off-platform sales dance. The partner FAQ attributes the button to partners enrolled in the AgentExchange Partner Program; note that distributing a packaged solution is separately gated on the passed Security Review under the ISV Program Track.


Common Patterns

Full commercial listing (solution + Checkout)

When to use: an ISV with a managed-package solution, a US/UK/EU-based company, and a self-service pricing motion.

How it works: complete the listing plan and get business approval → run the 5-step Listing Builder (Basics → Set Pricing, adding pricing plan details and getting the plan approved → Add Details → Link Your Solution, choosing "Install from your AgentExchange listing" → Grow Your Business) → connect a Stripe account to the listing and add one-time or subscription pricing plans → submit the listing for approval.

Why not the alternative: skipping Checkout means every deal needs an off-platform order via COA; and per the documented flow, the listing can only be submitted for approval once the basics are complete and pricing is set — so leaving Set Pricing half-done stalls submission.

Consultant listing

When to use: a consulting partner listing services rather than a packaged solution.

How it works: the 3-step flow — Fill in the Basics, Add Details, Grow Your Business. There is no Set Pricing or Link Your Solution step and no package or Security Review to gate on.

Sales-assisted listing with Private Offers

When to use: enterprise-priced solutions where public list pricing doesn't fit, but you still want the buying conversation to start (and stay) on the marketplace.

How it works: publish the listing, then enable the Request Private Offer button so customers open a negotiation directly from the listing. Combine with lead capture from the Grow Your Business step so marketplace activity lands in your pipeline.


Decision Guidance

SituationRecommended ApproachReason
Consulting services, no packageConsultant listing (3-step flow)No pricing or solution-linking steps apply
Managed package, company in US/UK/EU, self-service pricingCheckout with one-time or subscription plansOn-platform payment; 15% revenue share, no setup/monthly fees
Company based outside US/UK/EUOff-platform billing + COACheckout requires the partner to be US/UK/EU-based
OEM appOff-platform billing + COACheckout can't be used with OEM apps
Enterprise/negotiated pricingPrivate Offers on the listingCustomers negotiate without leaving the marketplace
Free-with-limits go-to-marketFreemium modelDocumented model: free up to specific feature-based limits
Predictable per-org economics preferred over % of revenueAnnual Fee modelFixed, upfront yearly fee based on customer orgs and/or users

Recommended Workflow

  1. Classify the listing and check the gates — solution vs. consultant listing; for solutions, confirm the managed package exists and the Security Review has passed (or plan for it); confirm the publisher holds Create + Upload AgentExchange Packages permissions.
  2. Draft the listing plan — basic details + pricing model + pricing plans (use templates/agentexchange-publishing-template.md), then submit it to your Salesforce account representative for business approval before building anything in the console.
  3. Build the listing in the Partner Console — Partner Community → Publishing → Listings → create the listing and work the steps in order: Fill in the Basics; Set Pricing (add pricing plan details and get the plan approved); Add Details; Link Your Solution (connect the managed package, confirm security compliance, pick the install method); Grow Your Business (test drives via trial templates, free trials, lead capture). Consultant listings: Basics → Details → Grow only.
  4. Configure payment — if Checkout-eligible (US/UK/EU company, managed package, not OEM), create and connect the Stripe account and add pricing plans on the listing; US partners submit a W-9, EU/UK partners enable VAT as needed. Otherwise wire the off-platform COA motion. Optionally enable the Request Private Offer button.
  5. Submit and verify — submit the listing for review; once public, verify the live listing's content, pricing plans, and install path end to end.
  6. Maintain post-publish — update public-facing company contact details from the Partner Console Home page (Home → Overview → Company Info), not the Business Contact field inside the listing steps; watch Notifications and Your Analytics (tile views, tile hovers, lead events) for follow-ups.

Review Checklist

Run through these before marking work in this area complete:

  • Listing type identified; consultant listings use the 3-step flow, solutions the 5-step flow
  • Security Review passed (or scheduled as the critical path) for any packaged solution
  • Listing plan (details + pricing model + pricing plans) approved by the account representative
  • Checkout eligibility verified before promising on-platform payment: US/UK/EU company, managed package, not OEM
  • Checkout fee math uses documented numbers: 15% bank transfer; 15% + $0.30/transaction credit card
  • Private Offers enablement decision recorded for negotiated-pricing motions
  • Public contact details maintained from Partner Console Home, not the in-listing Business Contact field
  • No GA/Beta/Pilot maturity claim made that the docs don't state

Salesforce-Specific Gotchas

Non-obvious platform behaviors that cause real production problems:

  1. Business Contact edits vanish from the public listing — updating the Business Contact field during the "Fill in the Basics" stage does not appear on the public listing. Public contact info is maintained from the Partner Console Home page, and those updates apply to all your public listings.
  2. Checkout eligibility is about the partner, not the customer — the partner company must be based in the US, UK, or an EU country, but payments can be accepted from any country Stripe supports. Teams routinely invert this and wrongly rule Checkout in or out.
  3. Basics + pricing gate listing submission — per the documented flow, a listing can be submitted for approval only once Fill in the Basics is complete and pricing is set; leaving either half-done stalls the submission, not just the copywriting.

Output Artifacts

ArtifactDescription
templates/agentexchange-publishing-template.mdFill-in listing-plan workbook (basics + pricing model + pricing plans + Checkout/Private Offers decisions) with machine-checkable fields
scripts/check_agentexchange_publishing.pyStdlib validator for a completed listing plan: flow shape, pricing model, Checkout eligibility gates, Security Review gate
Partner Console publishing sequenceOrdered step list (5-step or 3-step) tailored to the listing type

Related Skills

  • devops/second-generation-managed-packages — build and version the managed package the listing's Link Your Solution step connects to.
  • devops/isv-license-management-and-trialforce — LMA registration, Trialforce trial templates (used by the Grow Your Business test-drive setup), and Checkout licensing integration internals.
  • devops/appexchange-app-analytics — deeper marketplace usage analytics beyond the Partner Console's tile views / tile hovers / lead events.
  • agentforce/agent-security-review — pre-production hardening of the agent itself before submitting the packaged solution to the marketplace Security Review.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use admin/case-management-setup. Covers ActivitiesSettings metadata, enableActivities, shared Task/Event custom fields and FLS, TaskStatus value sets, Shared Activities and TaskRelation/EventRelation, recurring and child activities, and partial-success bulk DML on Task.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Designing or reviewing Agentforce actions: Flow actions, Apex invocable actions, prompt-template actions, action naming, input and output contracts, confirmation requirements, and safe error behavior. Triggers: 'agent actions', 'build an agent that can look up an order', 'make the agent able to check order status', 'give the agent a capability', 'agent that can retrieve a record', 'flow action for agent', 'agent invocable action', 'action schema design'. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex. NOT for the reason_code error envelope that stops an agent retry loop — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

PranavNagrecha のスキルをすべて見る

このスキルの問題を報告する