agentleFS
Microsoft AzureKnown publisherAzure/git-ape/.github/community-skills/onboard-to-marketplace/SKILL.md

onboard-to-marketplace

Skill274 starsChanged 29 days agoMITView on GitHub

End-to-end onboarding flow for Azure Marketplace SaaS publication, from Partner Center readiness to final go-live checks.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to move a ready SaaS platform into a publishable Azure Marketplace offer.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboard to Marketplace

Use this skill to move a ready SaaS platform into a publishable Azure Marketplace offer.

What this skill covers

  1. Publisher and Partner Center readiness checks.
  2. Offer setup (listing, plans, pricing, legal).
  3. Technical validation inputs (fulfillment, landing page, webhooks).
  4. Private audience testing and certification prep.
  5. Final launch checklist and operational handoff.

Output

  • Marketplace onboarding checklist with blockers.
  • Required artifact inventory for submission.
  • Go-live readiness status by stage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.