← ClaudeAtlas

microsoft-store-listing-evidence-verifierlisted

Validate evidence-backed Microsoft Store MSIX listing readiness. Use when auditing Partner Center keywords, truthful screenshot provenance, capture manifests, MSIX/AppX bundles, bundle checksums, clean-Windows test evidence, or final submission checklists for Windows desktop apps.
SteveKinzey/claude-code-tools-installer · ★ 1 · AI & Automation · score 67
Install: claude install-skill SteveKinzey/claude-code-tools-installer
# Microsoft Store Listing Evidence Verifier Use this skill to keep Microsoft Store metadata, screenshots, and package evidence tied to the same tested Windows candidate. It complements `microsoft-store-listing-readiness` and `windows-msix-store-release`. ## Boundaries - Never claim a package is signed, certified, submitted, or published without direct evidence. - A ZIP, DMG, MSI, EXE, or test-signed copy is not evidence for an unsigned Store MSIX bundle. - Do not create a Partner Center account, set price or availability, enter tax/business data, or submit certification without explicit owner approval. - Never create final Store screenshots from a browser, mock, fixture, renderer-only session, composite, generated image, older build, macOS, or Linux session. - Do not print, commit, or place exact Partner Center Identity/Publisher values in chat, reports, source, or workflow inputs. Validator output must redact identity values. ## Required inputs 1. Read `references/partner-center-rules.md` for current keyword and screenshot rules. 2. Locate the canonical desktop source, exact release commit, unsigned candidate, checksum companion, and clean-Windows test record. 3. Copy `templates/capture-manifest.template.json` for a new capture set. Keep it in template mode until actual evidence exists. 4. Treat the request as one of: **draft audit**, **template-to-candidate verification**, **final capture validation**, or **submission checklist**. ## Evidence states Keep two states s