alicloud-platform-multicloud-docs-api-benchmark_skill

Overview

This skill benchmarks similar product documentation and API documentation across major cloud providers to surface quality gaps and prioritized fixes. It auto-discovers official docs/APIs for Alibaba Cloud, AWS, Azure, GCP, Tencent Cloud, Volcano Engine, and Huawei Cloud, scores them consistently, and produces evidence plus an actionable report. The output highlights P0/P1/P2 issues and specific remediation steps to improve parity and developer experience.

How this skill works

Given a product keyword, the skill attempts automated discovery of official docs and API surfaces using layered data sources (official APIs/metadata, constrained web discovery, and fallbacks). It scores each provider against a shared rubric, generates benchmark_evidence.json and benchmark_report.md, and writes outputs under the expected output folder. You can pin authoritative links per provider to override discovery and switch scoring profiles for different product categories.

When to use it

• Compare documentation and API quality across clouds for the same product or capability
• Prioritize documentation improvements after product launches or migrations
• Assess multi-cloud parity for developer experience and onboarding
• Prepare procurement or compliance evaluations that include docs/API quality
• Validate API discoverability and machine-readability across providers

Best practices

• Pin official links when auto-discovery confidence is low to ensure accurate comparison
• Select or customize a scoring profile that matches your product category (see references/scoring.json)
• Run benchmarks regularly to track improvements and regressions over time
• Review P0 items first — they represent highest-impact fixes for developer usability
• Keep a copy of benchmark_evidence.json for auditability and change-tracking

Example use cases

• Competitive analysis: compare storage/service docs across AWS, GCP, Azure, Alibaba Cloud and others
• Migration planning: identify gaps that could slow cloud-to-cloud migrations
• Documentation triage: generate prioritized remediation tasks (P0/P1/P2) for a docs team
• API design review: expose missing machine-readable metadata or discovery endpoints
• Procurement: include vendor docs quality scores in vendor selection decisions