Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .claude/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .agents/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .cursor/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .gemini/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .github/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "msstore-cli" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/msstore-cli into .opencode/skills/msstore-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msstore-cli", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
msstore-cli
GitHub stars
40k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,040 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT
At a glance
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store.
Works in 4 steps: Go to Partner Center → Navigate to Account settings > User… → Create a new application and note the… → …
Asked to configure Store credentials
SKILL.md covers When to Use This Skill, Prerequisites, Core Commands Reference and Common Workflows, plus 4 more sections
Calls winget and dotnet; reaches contoso.com; needs CLIENT_SECRET and MSSTORE_CLIENT_SECRET
What it does
Msstore CLI is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Cross-platform mobile apps and CI/CD. It works with Windows, GitHub, Flutter and React Native. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
When your agent uses it
Asked to configure Store credentials
List Store apps
Check submission status
Publish submissions
Example prompts
“/msstore-cli”
Requirements
A credential in CLIENT_SECRET
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
1Go to Partner Center
2Navigate to Account settings > User management > Azure AD applications
3Create a new application and note the Tenant ID, Client ID, and Client Secret
4Grant the application appropriate permissions (Manager or Developer role)
What it can do on your machine
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
winget
dotnet
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
contoso.com
Also links to:
learn.microsoft.com
microsoft.com
aka.ms
partner.microsoft.com
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
CLIENT_SECRET
MSSTORE_CLIENT_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Msstore CLI loads about 4.1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,040 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~104
When it runs· the whole SKILL.md, loaded when a task matches
~4.1k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/msstore-cli/SKILL.md (or your agent's skills folder).
name
msstore-cli
description
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
license
MIT
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
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:
Bash/Zsh: Wrap the JSON in single quotes so the shell passes it through literally.bash
# 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> <flightId>
# Finalize rollout (100%)
msstore flights submission rollout finalize <productId> <flightId>
Common Workflows
Workflow 1: First-Time Store Setup
bash
# 1. Install the CLI
winget install "Microsoft Store Developer CLI"
# 2. Configure credentials (get these from Partner Center)
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET
# 3. Verify configuration
msstore info
# 4. List your apps to confirm access
msstore apps list
Workflow 2: Initialize and Publish New App
bash
# 1. Navigate to project
cd my-winui-app
# 2. Initialize for Store (creates/updates app identity)
msstore init .
# 3. Package the application
msstore package . --arch x64,arm64
# 4. Publish to Store
msstore publish .
# 5. Check submission status
msstore submission status <productId>
Workflow 3: Update Existing App
bash
# 1. Build your updated application
dotnet publish -c Release
# 2. Package and publish
msstore publish ./my-app
# Or publish from existing package
msstore publish ./my-app --inputFile ./artifacts/MyApp.msixupload
Workflow 4: Gradual Rollout
bash
# 1. Publish with initial rollout percentage
msstore publish ./my-app --packageRolloutPercentage 10
# 2. Monitor and increase rollout
msstore submission poll <productId>
# 3. (After validation) Finalize to 100%
# This completes via Partner Center or submission update
Workflow 5: Beta Testing with Flights
bash
# 1. Create a flight group in Partner Center first
# Then create a flight
msstore flights create <productId> "Beta Testers" --group-ids "group-id-1,group-id-2"
# 2. Publish to the flight
msstore publish ./my-app --flightId <flightId>
# 3. Check flight submission status
msstore flights submission status <productId> <flightId>
# 4. After testing, publish to production
msstore publish ./my-app
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Msstore CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Cross-platform UI/UX design reviewer grounded in Apple's Human Interface Guidelines (122 pages pulled from developer.apple.com, including 57 component pages) plus a design-craft lens for…
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Msstore CLI is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store.
When should I use Msstore CLI?
Msstore CLI fits situations like: asked to configure Store credentials; list Store apps; check submission status; publish submissions.
How do I install Msstore CLI in Claude Code?
Run `npx skills add github/awesome-copilot --skill msstore-cli -a claude-code`. Or copy the skill folder (skills/msstore-cli in github/awesome-copilot) into .claude/skills/msstore-cli in your project. Claude Code loads it when a task matches its description.
How do I install Msstore CLI in Codex?
Run `npx skills add github/awesome-copilot --skill msstore-cli -a codex`. Or copy the skill folder (skills/msstore-cli in github/awesome-copilot) into .agents/skills/msstore-cli in your project. Codex loads it when a task matches its description.
Can I use Msstore CLI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill msstore-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/msstore-cli, .gemini/skills/msstore-cli, .github/skills/msstore-cli and .opencode/skills/msstore-cli in your project.
What does Msstore CLI need to run?
Going by SKILL.md and its folder, Msstore CLI needs the command-line tools its instructions call (winget and dotnet) and credentials named CLIENT_SECRET and MSSTORE_CLIENT_SECRET. Our summary lists: A credential in CLIENT_SECRET.
Does Msstore CLI access the network?
SKILL.md names 6 domains. In commands or code: contoso.com; the agent is likely to contact it when it follows the instructions. As links in the text: learn.microsoft.com, microsoft.com, aka.ms, partner.microsoft.com and github.com. This is read from the text; nothing was executed.
Is Msstore CLI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Msstore CLI use?
Msstore CLI is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Msstore CLI use?
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Msstore CLI?
Skills that share tags, products or a category with Msstore CLI: Android Cicd (davila7/claude-code-templates, 32k stars), Mobile App Builder (revfactory/harness-100, 1.3k stars), GitHub Actions (callstackincubator/agent-skills, 1.7k stars) and Apple Design (vrcm-team/VRCM, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Msstore CLI?
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.