platform-ecosystem-prior-art-survey

Surveys existing platform ecosystems to produce validated prior-art records and a decision index.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill platform-ecosystem-prior-art-survey-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-ecosystem-prior-art-survey
Source: https://github.com/bm629/agent-skills/tree/main/skills/platform-ecosystem-prior-art-survey
Command: npx skills add https://github.com/bm629/agent-skills --skill platform-ecosystem-prior-art-survey-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jsonschema, and includes scripts (resource) and references (resource) components.

What problem does it solve? Teams building plugin systems, app marketplaces, or developer platforms reinvent decisions that Shopify, VS Code, Slack, WordPress, and Chrome settled years ago, because the public evidence for those decisions is almost never systematically gathered. This Skill runs one assignment of a structured prior-art survey — a vocabulary map, one search angle, one mechanism extract record, or the final decision index — with every query, zero result, and absence recorded so the evidence is reproducible. ## Core Features & Use Cases - Vocabulary map minting: Defines platform slugs, mechanism vocabulary with vendor synonyms, and per-angle applicability verdicts before any searching begins. - Recorded search angles: Executes one of seven search angles across developer documentation, marketplace policies, declarative contracts, migration history, isolation models, and complementor forums, recording every query verbatim with coverage cells per source. - Extract records and decision index: Reads one mechanism from one platform into a validated extract record, then cuts the corpus across nine lenses into a decision index a build phase consumes directly. - Schema-gated validation: Every artifact is validated by a bundled Python script against JSON schemas, with exit codes distinguishing artifact findings from unusable runs. - Use Case: Before designing an extension API for your SaaS product, run the survey to produce a decision index showing how comparable platforms structured manifest fields, revenue shares, review gates, and migration timelines, each row backed by verbatim evidence quotes. ## Quick Start Use platform-ecosystem-prior-art-survey to run the vocabulary-map assignment for our planned plugin marketplace and produce a validated platform-vocabulary-map.yaml.

Frequently Asked Questions about platform-ecosystem-prior-art-survey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research prior art before building a plugin system or marketplace?

Run a structured survey that mints a platform-and-mechanism vocabulary map first, then executes search angles across each platform's own developer docs, policies, and contracts. Every query is recorded verbatim so the corpus can be re-run and audited.

What platforms does this survey cover as evidence?

The source registry covers Shopify, VS Code, Slack, Chrome extensions, WordPress, Figma, Notion, Zapier, Stripe Connect, Atlassian, GitHub Marketplace, Apple App Store, Mozilla, Google Play, and HubSpot, each with verified access status and fallbacks.

How do I validate the survey output files?

Run the bundled validator with uv: python scripts/validate_platform_ecosystem_prior_art.py with the keyword-map, search, extract, or synthesis subcommand. Exit code 0 means clean, 1 means the artifact has findings, and 2 means the run itself could not be used.

Why does the survey record zero results instead of omitting them?

A recorded zero on a reached source is a measurement proving the search ran and found nothing, while an omitted cell is indistinguishable from a search that never happened. This distinction is what makes a later no-prior-art claim defensible.

What is the difference between retrieved_at, as_of, and source_claimed_modified_at?

retrieved_at is when you fetched the page, as_of is when the fact became true and stays null when unstated, and source_claimed_modified_at is the page's claim about itself, which can be provably false. Never default an absent date to the fetch date.

When should an angle record not_run instead of searching?

When the vocabulary map's angle_applicability verdict for that angle is holds: false, the angle must not search and records outcome: not_run with no coverage cells. Searching anyway inflates the survey with an angle the scope ruled out.