Assess Launch Readiness¶

Capability Slug: assess_launch_readiness Plan Tier: Command Credit Cost: 8 base + 5 (recommendations, default on) ≈ 13 typical Category: Intelligence & Attribution Default mode: prediction_type: 'readiness' Backend: Prediction Engine (PredictionEngineService::scoreLaunchReadiness())

Overview¶

The publish-readiness gate for AWS Marketplace listing versions. Given a saved ListingVersion, the capability returns a weighted overall score across five dimensions, lists explicit blocking issues that would prevent publishing, and provides a percentile rank against other listings in the same category. Use it as the programmatic gate before pushing a listing live.

This capability is the API counterpart to the Launch Readiness Dashboard — same scoring algorithm, single-version scope.

Shared handler with two sibling capabilities¶

PredictPerformanceCapability backs three registry slugs that dispatch by prediction_type. See Predict Co-Sell Partner Success for the full shared-handler explanation.

Slug	`prediction_type`	What it scores
`assess_launch_readiness` (this page)	`readiness`	Publish-readiness against blocking issues
`predict_performance`	`full` (or `listing`)	CTR, conversion, revenue forecast
`predict_partner_success`	`partner`	Partnership success probability

The five scoring dimensions¶

Weight	Dimension	What it measures
25%	Content Quality	Title length (40-80 chars), description quality, highlights with metrics, action verbs
20%	Compliance	Required fields, pricing information, support details, AWS submission requirements
20%	Competitive Position	Unique value propositions, free trial availability, differentiators vs. benchmarks
20%	Market Fit	Use case clarity, target audience definition, AWS service integrations
15%	SEO Optimization	Keyword density, AWS service mentions, optimal lengths for search visibility

These weights match the Launch Readiness Dashboard exactly. The dashboard runs the same scoring over every listing on a team in batch; this capability runs it on a single version on demand.

What you get back¶

{
  "success": true,
  "prediction_type": "readiness",
  "credits_used": 13,
  "prediction": {
    "overall_score": 78,
    "readiness_level": "almost_ready",
    "category_scores": {
      "content_quality": 85,
      "seo_optimization": 72,
      "compliance": 90,
      "competitive_position": 68,
      "market_fit": 75
    },
    "percentile_rank": 64
  },
  "blocking_issues": [
    {
      "field": "...",
      "issue": "...",
      "severity": "high|medium|low",
      "fix": "..."
    }
  ],
  "check_results": [ /* every individual check the scorer ran */ ],
  "interpretation": "..."
}

The blocking_issues list is the actionable output. Treat empty blocking_issues as the publish-go signal regardless of overall score; treat any severity: high issue as a hard publish-block. The check_results list captures every individual check the scorer ran (not just the failing ones) so you can inspect why a particular dimension scored where it did.

percentile_rank compares against other listings in the same category — useful for "are we average, top quartile, or top decile?" reads.

Required and optional parameters¶

Parameter	Required	Description
`version_id`	Yes	Saved `ListingVersion` to score. Unlike `predict_performance`, raw content is not accepted.
`prediction_type`	Implicit (`readiness`)	Defaults to `readiness` for this slug
`include_recommendations`	No	Default `true`. +5 credits.

The version_id requirement is intentional — the readiness scorer needs the full structured listing (title, description, highlights, pricing, support, AWS services) coherent against a version, not loose content fragments.

When to use it¶

Scenario	Use this capability
Pre-publish gate before pushing a listing live	✅
Quarterly readiness audit on the listing portfolio	Use the admin dashboard for the batch view
Forecast performance lift from a listing change	`predict_performance`
Score brand-voice / KB / market-definition completeness (not listing-specific)	`content_readiness_analyzer`

It is not:

A scorer for raw content. Save a ListingVersion first.
The same as Content Readiness Analyzer. That one scores the brand-voice and KB inputs that feed into listing creation. This one scores a finished listing version.

API access¶

Exposed as assess_launch_readiness. Partner API keys scoped with view_listings plus the agent capability slug can run readiness checks programmatically. See Partner API Capabilities.