On-demand scanning
On-demand scans let an authorized user inspect supported content without enabling continuous repository monitoring. Hosted scans use the Workspace’s current policy and hosted-scan allowance.
Supported inputs
Section titled “Supported inputs”The Control Plane accepts pasted Markdown or JSON, a bounded ZIP archive, a public GitHub repository URL, and a CLI upload containing only locally discovered supported files.
Skill entrypoints are matched case-insensitively, so names such as SKILL.md, skill.md, and Skill.MD are discovered at any depth. The scanner also recognizes the registered MCP configuration filenames and bounded compatibility layouts under known skill roots.
Private repositories should use the GitHub App connection. The Captain cannot fetch repository URLs or arbitrary external content.
Isolation and validation
Section titled “Isolation and validation”Signals Corps treats every input as untrusted. It never runs repository code, scripts, hooks, package managers, builds, or binaries. ZIP processing rejects path traversal, links, special files, excessive compressed or extracted size, too many files, and oversized individual files.
The scanner receives a server-generated object reference and verified digest. Input expires from quarantine storage under the retention policy; the durable result keeps bounded metadata and allowed evidence rather than the original archive.
Capacity
Section titled “Capacity”Each accepted hosted request consumes one unit from the Workspace’s current hosted-scan allowance. When the allowance is exhausted, new hosted scans are blocked until its reset time. Supply Chain does not create an automatic paid overage.