Automate Microsoft Store publishing and submission management from the command line.
Works with
Supports Windows App SDK, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications with automatic project detection
Core commands cover credential configuration, app listing, submission status checks, publishing, metadata updates, and gradual rollouts
Includes package flight management for beta testing with group-based distribution and rollout percentage control
Integrates with Partne
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmsstore-cliExecute the skills CLI command in your project's root directory to begin installation:
Fetches msstore-cli from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate msstore-cli. Access via /msstore-cli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
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.
Use this skill when you need to:
winget install "Microsoft Store Developer CLI"Before using msstore, you need to create an Azure AD application with Partner Center access:
Display the current credential configuration.
msstore info
Options:
| Option | Description |
|---|---|
-v, --verbose |
Print verbose output |
Configure or update Microsoft Store API credentials.
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:
# 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
Change settings of the Microsoft Store Developer CLI.
msstore settings [options]
Options:
| Option | Description |
|---|---|
-t, --enableTelemetry |
Enable (true) or disable (false) telemetry |
msstore settings setpdn <publisherDisplayName>
Sets the default Publisher Display Name for the init command.
List and retrieve application information.
msstore apps list
Lists all applications in your Partner Center account.
msstore apps get <productId>
Arguments:
| Argument | Description |
|---|---|
productId |
The Store product ID (e.g., 9NBLGGH4R315) |
Example:
# Get details of a specific app
msstore apps get 9NBLGGH4R315
Manage Store submissions.
| Sub-Command | Description |
|---|---|
status |
Get submission status |
get |
Get submission metadata and package info |
getListingAssets |
Get listing assets of a submission |
updateMetadata |
Update submission metadata |
poll |
Poll submission status until complete |
publish |
Publish a submission |
delete |
Delete a submission |
msstore submission status <productId>
msstore submission get <productId>
msstore submission updateMetadata <productId> <metadata>
Where <metadata> is a JSON string with the updated metadata. Because JSON contains characters that shells interpret (quotes, braces, etc.), you must quote and/or escape the value appropriately:
msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
msstore submission updateMetadata 9NBLGGH4R315 "{\"description\":\"My updated app\"}"
Tip: For complex or multi-line metadata, save the JSON to a file and pass its contents instead to avoid quoting issues:
msstore submission updateMetadata 9NBLGGH4R315 "$(cat metadata.json)"
Options:
| Option | Description |
|---|---|
-s, --skipInitialPolling |
Skip initial status polling |
msstore submission publish <productId>
msstore submission poll <productId>
Polls until the submission status is PUBLISHED or FAILED.
msstore submission delete <productId>
Options:
| Option | Description |
|---|---|
--no-confirm |
Skip confirmation prompt |
Initialize a project for Microsoft Store publishing. Automatically detects project type and configures Store identity.
msstore init <pathOrUrl> [options]
Arguments:
| Argument | Description |
|---|---|
pathOrUrl |
Project directory path or PWA URL |
Options:
| Option | Description |
|---|---|
-n, --publisherDisplayName |
Publisher Display Name |
--package |
Also package the project |
--publish |
Package and publish (implies --package) |
-f, --flightId |
Publish to a specific flight |
-prp, --packageRolloutPercentage |
Gradual rollout percentage (0-100) |
-a, --arch |
Architecture(s): x86, x64, arm64 |
-o, --output |
Output directory for packages |
-ver, --version |
Version to use when building |
Supported Project Types:
Examples:
# Initialize WinUI project
msstore init ./my-winui-app
# Initialize PWA
msstore init https://contoso.com --output ./pwa-package
# Initialize and publish
msstore init ./my-app --publish
Package an application for Microsoft Store submission.
msstore package <pathOrUrl> [options]
Arguments:
| Argument | Description |
|---|---|
pathOrUrl |
Project directory path or PWA URL |
Options:
| Option | Description |
|---|---|
-o, --output |
Output directory for the package |
-a, --arch |
Architecture(s): x86, x64, arm64 |
-ver, --version |
Version for the package |
Examples:
# Package for default architecture
msstore package ./my-app
# Package for multiple architectures
msstore package ./my-app --arch x64,arm64 --output ./packages
# Package with specific version
msstore package ./my-app --version 1.2.3.0
Publish an application to the Microsoft Store.
msstore publish <pathOrUrl> [options]
Arguments:
| Argument | Description |
|---|---|
pathOrUrl |
Project directory path or PWA URL |
Options:
| Option | Description |
|---|---|
-i, --inputFile |
Path to existing .msix or .msixupload file |
-id, --appId |
Application ID (if not initialized) |
-nc, --noCommit |
Keep submission in draft state |
-f, --flightId |
Publish to a specific flight |
-prp, --packageRolloutPercentage |
Gradual rollout percentage (0-100) |
Examples:
# Publish project
msstore publish ./my-app
# Publish existing package
msstore publish ./my-app --inputFile ./packages/MyApp.msixupload
# Publish as draft
msstore publish ./my-app --noCommit
# Publish with gradual rollout
msstore publish ./my-app --packageRolloutPercentage 10
Manage package flights (beta testing groups).
| Sub-Command | Description |
|---|---|
list |
List all flights for an app |
get |
Get flight details |
delete |
Delete a flight |
create |
Create a new flight |
submission |
Manage flight submissions |
msstore flights list <productId>
msstore flights get <productId> <flightId>
msstore flights create <productId> <friendlyName> --group-ids <group-ids>
Options:
| Option | Description |
|---|---|
-g, --group-ids |
Flight group IDs (comma-separated) |
-r, --rank-higher-than |
Flight ID to rank higher than |
msstore flights delete <productId> <flightId>
# Get flight submission
msstore flights submission get <productId> <flightId>
# Publish flight submission
msstore flights submission publish <productId> <flightId>
# Check flight submission status
msstore flights submission status <productId> <flightId>
# Poll flight submission
msstore flights submission poll <productId> <flightId>
# Delete flight submission
msstore flights submission delete <productId> <flightId>
# Get rollout status
msstore flights submission rollout get <productId> <flightId>
# Update rollout percentage
msstore flights submission rollout update <productId> <flightId> <percentage>
# Halt rollout
msstore flights submission rollout halt <productId> ✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
premium-frontend-ui
232github/awesome-copilot
Frontendsame repojava-springboot
52github/awesome-copilot
Backendsame repogrill-me
699mattpocock/skills
Productivitysame categorypremortem
217parcadei/continuous-claude-v3
Productivitysame categorydeslop
163cursor/plugins
Productivitysame categorytravel-planner
142ailabs-393/ai-labs-claude-skills
Productivitysame categoryReviews
4.6★★★★★34 reviews- NNoor Brown★★★★★Dec 28, 2024
Useful defaults in msstore-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- AAanya Choi★★★★★Dec 4, 2024
msstore-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAanya Robinson★★★★★Nov 23, 2024
Keeps context tight: msstore-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAditi Thomas★★★★★Nov 19, 2024
We added msstore-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- AAisha Khan★★★★★Oct 14, 2024
I recommend msstore-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- AAditi Li★★★★★Oct 10, 2024
msstore-cli reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ZZaid Patel★★★★★Sep 25, 2024
msstore-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNoor Liu★★★★★Sep 25, 2024
I recommend msstore-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- PPiyush G★★★★★Sep 21, 2024
Keeps context tight: msstore-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAisha Diallo★★★★★Sep 21, 2024
Useful defaults in msstore-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 34
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.