Msstore Cli
Publish and manage Microsoft Store submissions, flights, rollouts, and CI/CD using the msstore CLI against Partner Center APIs.
Overview
msstore-cli is an agent skill most often used in Ship (also Launch distribution and Operate iterate) that configures Microsoft Store credentials, submissions, flights, and CI/CD via the msstore command-line interface.
Install
npx skills add https://github.com/github/awesome-copilot --skill msstore-cliWhat is this skill?
- Partner Center workflows: credentials, list apps, submission status, publish, metadata updates
- Package flights for beta testing and gradual rollout of submissions
- CI/CD setup for automated Store publishing across WinUI, UWP, MAUI, Flutter, Electron, React Native, and PWA
- Cross-platform CLI on Windows 10+, macOS, or Linux with .NET 9 runtime prerequisites
- Initialize projects for Store publishing and package applications for submission
Adoption & trust: 6.8k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Windows app ready to ship but Partner Center publish steps, flight management, and rollout status are opaque without a documented CLI and API path.
Who is it for?
Indie Windows developers automating Microsoft Store releases for MAUI, WinUI, Electron, or PWA apps with Partner Center and Azure AD already in place.
Skip if: Teams only targeting Google Play or Apple App Store, projects with no Partner Center account, or pure web SaaS with no Store package.
When should I use this skill?
User asks to configure Store credentials, list apps, check submission status, publish, manage flights, CI/CD for Store, gradual rollouts, or metadata updates with msstore.
What do I get? / Deliverables
The agent can run msstore commands to configure Store access, check and publish submissions, manage flights and rollouts, and scaffold CI/CD for repeatable Microsoft Store releases.
- Configured msstore credential and project initialization
- Published or updated Store submission with documented status
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Store submission is the canonical shelf in Ship because packaging, credentials, and publish actions happen right before customers can install. Launch subphase captures go-live mechanics—publish submission, check status, gradual rollout—distinct from local testing or code review.
Where it fits
Package a MAUI build and publish a new submission after local QA passes.
List Store apps and confirm submission visibility before announcing release.
Advance gradual rollout percentage or spin a package flight for hotfix validation.
How it compares
Store-specific release CLI skill— not generic Azure deployment and not mobile ASO copywriting.
Common Questions / FAQ
Who is msstore-cli for?
Solo and small-team Windows app publishers who want agent-guided msstore CLI workflows for Partner Center instead of manual portal repetition.
When should I use msstore-cli?
Use it in Ship when packaging and submitting; in Launch when checking distribution status and publishing; and in Operate when updating flights, rollouts, or CI/CD pipelines for Store releases.
Is msstore-cli safe to install?
It implies Partner Center and Azure AD credentials with network and shell access; review the Security Audits panel on this Prism page and protect publish permissions.
SKILL.md
READMESKILL.md - Msstore Cli
# Microsoft Store Developer CLI (msstore) The Microsoft Store Developer CLI (`msstore`) is a cross-platform command-line interface for publishing and managing applications in the Microsoft Store. It integrates with Partner Center APIs and supports automated publishing workflows for various application types. ## When to Use This Skill Use this skill when you need to: - Configure Store credentials for API access - List applications in your Store account - Check the status of a submission - Publish submissions to the Store - Package applications for Store submission - Initialize projects for Store publishing - Manage package flights (beta testing) - Set up CI/CD pipelines for automated Store publishing - Manage gradual rollouts of submissions - Update submission metadata programmatically ## Prerequisites - Windows 10+, macOS, or Linux - .NET 9 Desktop Runtime (Windows) or .NET 9 Runtime (macOS/Linux) - Partner Center account with appropriate permissions - Azure AD app registration with Partner Center API access - msstore CLI installed via one of these methods: - **Microsoft Store**: [Download](https://www.microsoft.com/store/apps/9P53PC5S0PHJ) - **WinGet**: `winget install "Microsoft Store Developer CLI"` - **Manual**: Download from [GitHub Releases](https://aka.ms/msstoredevcli/releases) ### Partner Center Setup Before using msstore, you need to create an Azure AD application with Partner Center access: 1. Go to [Partner Center](https://partner.microsoft.com/dashboard) 2. Navigate to **Account settings** > **User management** > **Azure AD applications** 3. Create a new application and note the **Tenant ID**, **Client ID**, and **Client Secret** 4. Grant the application appropriate permissions (Manager or Developer role) ## Core Commands Reference ### info - Print Configuration Display the current credential configuration. ```bash msstore info ``` **Options:** | Option | Description | | ------ | ----------- | | `-v, --verbose` | Print verbose output | ### reconfigure - Configure Credentials Configure or update Microsoft Store API credentials. ```bash msstore reconfigure [options] ``` **Options:** | Option | Description | | ------ | ----------- | | `-t, --tenantId` | Azure AD Tenant ID | | `-s, --sellerId` | Partner Center Seller ID | | `-c, --clientId` | Azure AD Application Client ID | | `-cs, --clientSecret` | Client Secret for authentication | | `-ct, --certificateThumbprint` | Certificate thumbprint (alternative to client secret) | | `-cfp, --certificateFilePath` | Certificate file path (alternative to client secret) | | `-cp, --certificatePassword` | Certificate password | | `--reset` | Reset credentials without full reconfiguration | **Examples:** ```bash # Configure with client secret msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET # Configure with certificate msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --certificateFilePath ./cert.pfx --certificatePassword MyPassword ``` ### settings - CLI Settings Change settings of the Microsoft Store Developer CLI. ```bash msstore settings [options] ``` **Options:** | Option | Description | | ------ | ----------- | | `-t, --enableTelemetry` | Enable (true) or disable (false) telemetry | #### Set Publisher Display Name ```bash msstore settings setpdn <publisherDisplayName> ``` Sets the default Publisher Display Name for the `init` command. ### apps - Application Management List and retrie