Official agent skill

Msstore CLI

by github in github/awesome-copilot

Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store.

OfficialMITAuto-check passedMobile

Install Msstore CLI

skills CLI
$ npx skills add github/awesome-copilot --skill msstore-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot msstore-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/msstore-cli .claude/skills/msstore-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

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.

  1. Go to Partner Center
  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)

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.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,040 words, ~4,074 tokens.

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
  • msstore CLI installed via one of these methods:
    • Microsoft Store: Download
    • WinGet: winget install "Microsoft Store Developer CLI"
    • Manual: Download from GitHub Releases
Partner Center Setup

Before using msstore, you need to create an Azure AD application with Partner Center access:

  1. Go to Partner Center
  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:

OptionDescription
-v, --verbosePrint verbose output
reconfigure - Configure Credentials

Configure or update Microsoft Store API credentials.

bash
msstore reconfigure [options]

Options:

OptionDescription
-t, --tenantIdAzure AD Tenant ID
-s, --sellerIdPartner Center Seller ID
-c, --clientIdAzure AD Application Client ID
-cs, --clientSecretClient Secret for authentication
-ct, --certificateThumbprintCertificate thumbprint (alternative to client secret)
-cfp, --certificateFilePathCertificate file path (alternative to client secret)
-cp, --certificatePasswordCertificate password
--resetReset 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:

OptionDescription
-t, --enableTelemetryEnable (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 retrieve application information.

List Applications
bash
msstore apps list

Lists all applications in your Partner Center account.

Get Application Details
bash
msstore apps get <productId>

Arguments:

ArgumentDescription
productIdThe Store product ID (e.g., 9NBLGGH4R315)

Example:

bash
# Get details of a specific app
msstore apps get 9NBLGGH4R315
submission - Submission Management

Manage Store submissions.

Sub-CommandDescription
statusGet submission status
getGet submission metadata and package info
getListingAssetsGet listing assets of a submission
updateMetadataUpdate submission metadata
pollPoll submission status until complete
publishPublish a submission
deleteDelete a submission
Get Submission Status
bash
msstore submission status <productId>
Get Submission Details
bash
msstore submission get <productId>
Update Metadata
bash
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:

  • Bash/Zsh: Wrap the JSON in single quotes so the shell passes it through literally.
    bash
    msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
  • PowerShell: Use single quotes (or escape double quotes inside a double-quoted string).
    powershell
    msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'
  • cmd.exe: Escape each inner double quote with a backslash.
    cmd
    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:

bash
msstore submission updateMetadata 9NBLGGH4R315 "$(cat metadata.json)"

Options:

OptionDescription
-s, --skipInitialPollingSkip initial status polling
Publish Submission
bash
msstore submission publish <productId>
Poll Submission
bash
msstore submission poll <productId>

Polls until the submission status is PUBLISHED or FAILED.

Delete Submission
bash
msstore submission delete <productId>

Options:

OptionDescription
--no-confirmSkip confirmation prompt
init - Initialize Project for Store

Initialize a project for Microsoft Store publishing. Automatically detects project type and configures Store identity.

bash
msstore init <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-n, --publisherDisplayNamePublisher Display Name
--packageAlso package the project
--publishPackage and publish (implies --package)
-f, --flightIdPublish to a specific flight
-prp, --packageRolloutPercentageGradual rollout percentage (0-100)
-a, --archArchitecture(s): x86, x64, arm64
-o, --outputOutput directory for packages
-ver, --versionVersion to use when building

Supported Project Types:

  • Windows App SDK / WinUI 3
  • UWP
  • .NET MAUI
  • Flutter
  • Electron
  • React Native for Desktop
  • PWA (Progressive Web Apps)

Examples:

bash
# 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
Show full SKILL.md (391 more words)Show less
package - Package for Store

Package an application for Microsoft Store submission.

bash
msstore package <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-o, --outputOutput directory for the package
-a, --archArchitecture(s): x86, x64, arm64
-ver, --versionVersion for the package

Examples:

bash
# 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 - Publish to Store

Publish an application to the Microsoft Store.

bash
msstore publish <pathOrUrl> [options]

Arguments:

ArgumentDescription
pathOrUrlProject directory path or PWA URL

Options:

OptionDescription
-i, --inputFilePath to existing .msix or .msixupload file
-id, --appIdApplication ID (if not initialized)
-nc, --noCommitKeep submission in draft state
-f, --flightIdPublish to a specific flight
-prp, --packageRolloutPercentageGradual rollout percentage (0-100)

Examples:

bash
# 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
flights - Package Flight Management

Manage package flights (beta testing groups).

Sub-CommandDescription
listList all flights for an app
getGet flight details
deleteDelete a flight
createCreate a new flight
submissionManage flight submissions
List Flights
bash
msstore flights list <productId>
Get Flight Details
bash
msstore flights get <productId> <flightId>
Create Flight
bash
msstore flights create <productId> <friendlyName> --group-ids <group-ids>

Options:

OptionDescription
-g, --group-idsFlight group IDs (comma-separated)
-r, --rank-higher-thanFlight ID to rank higher than
Delete Flight
bash
msstore flights delete <productId> <flightId>
Flight Submissions
bash
# 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>
Flight Rollout Management
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
Workflow 6: CI/CD Pipeline Integration
yaml
# GitHub Actions example
name: Publish to Store

on:
  release:
    types: [published]

jobs:
  publish:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Setup .NET
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '9.0.x'
      
      - name: Install msstore CLI
        run: winget install "Microsoft Store Developer CLI" --accept-package-agreements --accept-source-agreements
      
      - name: Configure Store credentials
        run: |
          msstore reconfigure --tenantId ${{ secrets.TENANT_ID }} --sellerId ${{ secrets.SELLER_ID }} --clientId ${{ secrets.CLIENT_ID }} --clientSecret ${{ secrets.CLIENT_SECRET }}
      
      - name: Build application
        run: dotnet publish -c Release
      
      - name: Publish to Store
        run: msstore publish ./src/MyApp

Integration with winapp CLI

The winapp CLI (v0.2.0+) integrates with msstore via the winapp store subcommand:

bash
# These commands are equivalent:
msstore reconfigure --tenantId xxx --clientId xxx --clientSecret xxx
winapp store reconfigure --tenantId xxx --clientId xxx --clientSecret xxx

# List apps
msstore apps list
winapp store apps list

# Publish
msstore publish ./my-app
winapp store publish ./my-app

Use winapp store when you want a unified CLI experience for both packaging and publishing.

Troubleshooting

IssueSolution
Authentication failedVerify credentials with msstore info; re-run msstore reconfigure
App not foundEnsure the product ID is correct; run msstore apps list to verify
Insufficient permissionsCheck Azure AD app role in Partner Center (needs Manager or Developer)
Package validation failedEnsure package meets Store requirements; check Partner Center for details
Submission stuckRun msstore submission poll <productId> to check status
Flight not foundVerify flight ID with msstore flights list <productId>
Rollout percentage invalidValue must be between 0 and 100
Init fails for PWAEnsure URL is publicly accessible and has valid web app manifest

Environment Variables

The CLI supports environment variables for credentials:

VariableDescription
MSSTORE_TENANT_IDAzure AD Tenant ID
MSSTORE_SELLER_IDPartner Center Seller ID
MSSTORE_CLIENT_IDAzure AD Application Client ID
MSSTORE_CLIENT_SECRETClient Secret

References

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/msstore-cli of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

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.

Compare with similar skills

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.

Msstore CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Msstore CLI this skillgithub/awesome-copilot40k1 repos~4.1kAutomated safety check: PassMIT
Android Cicddavila7/claude-code-templates32k—~2.2kAutomated safety check: PassMIT
Mobile App Builderrevfactory/harness-1001.3k—~1.8kAutomated safety check: PassApache-2.0
GitHub Actionscallstackincubator/agent-skills1.7k1 repos~703Automated safety check: PassMIT
Apple Designvrcm-team/VRCM1791 repos~6.2kAutomated safety check: PassMIT
Flutter Pub ReleaseMixinNetwork/flutter-plugins512—~1.3kAutomated safety check: PassMIT

Similar skills

  • Android Cicd

    davila7/claude-code-templates

    Automated Android CI/CD pipeline to Google Play — supports TWA, React Native, Flutter, and native Android.

    32k GitHub stars~2.2k tokensUpdated today
    MobileAuto-check passed
  • Mobile App Builder

    revfactory/harness-100

    Full mobile app development pipeline. An agent skill from revfactory/harness-100.

    1.3k GitHub stars~1.8k tokensUpdated 6 mo ago
    MobileAuto-check passed
  • GitHub Actions

    callstackincubator/agent-skills

    Official

    GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts.

    1.7k GitHub starsUsed in 1 repo~703 tokens
    DevOps & CloudAuto-check passed
  • Apple Design

    vrcm-team/VRCM

    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…

    179 GitHub starsUsed in 1 repo~6.2k tokens
    MobileAuto-check passed
  • Flutter Pub Release

    MixinNetwork/flutter-plugins

    Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.

    512 GitHub stars~1.3k tokensUpdated 1 mo ago
    MobileAuto-check passed
  • Claude Android Ninja

    Drjacky/claude-android-ninja

    Build and migrate Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, Room 3 (KSP, SQLiteDriver, Flow/suspend DAOs), Navigation3, and multi-module Gradle.

    124 GitHub stars~5.2k tokensUpdated 8 days ago
    MobileAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    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.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    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.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Msstore CLI

What does Msstore CLI do?

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.