Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on…
Use when adding or changing a build, storage, credentials, submit, or compute backend in launch-store - implement one of the five provider interfaces and register it, without touching the pipeline.
Use when finishing or verifying a change to launch-store - run the full typecheck, lint, test, build, and docs gate that must be green before a change is done or a PR merges.
Instructions for YosefHayim/launch-store, covering agents.md, branching and prs, repo layout - who owns what, conventions a linter can't infer and source of truth files.
How the engineering skills should consume this repo's domain documentation when exploring the codebase. launch-store is single-context: one CONTEXT.md + docs/adr/ at the repo root.
Issues and PRDs for launch-store live as GitHub issues on YosefHayim/launch-store. Use the gh CLI for all operations - it infers the repo from git remote -v automatically inside a clone.
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker. launch-store uses the canonical names as-is.
MCP server for signed machine-action records, offline tool-surface checks, and SSX360 USB signer support. Runs locally from the matrixscroll Python package.
Expert helper for planning, configuring and troubleshooting Electron desktop builds. Use when packaging or distributing a desktop app with Electron, when an electron-builder or electron-forge build fails, when there are errors related to Electron versions, Node versions, native modules, code signing, installer…
3 4mo agoA104 tokens
originalMIT
At most 3 mods per repository are shown here — the rest are on their repository pages: