Skill Import Provenance
Keep owned original work and primary authorities separate from external rejection evidence. Read provenance record before proposing an owned-source transfer.
Workflow
- Resolve the exact owned source, revision, artifact, author, license, destination, and authority for the proposed transfer.
- If the source is a third-party skill catalog, stop. Do not track, cite, mirror, adapt, vendor, or use it as an implementation source. Keep authorized investigation outside this repository and its distributions. Separately governed private research may retain original assessments, permalinks, and hashes under its own policy; it cannot supply imported prose, structure, or implementation authority here. Public behavior still requires owned work, primary authorities, and original evidence.
- Confirm ownership, or separately documented authority, for every transferred file, and confirm that the license permits the destination use.
- Inventory the exact files proposed for transfer and their dependencies, scripts, assets, hooks, and network behavior.
- Run or obtain a security review appropriate to the package's influence and execution surface.
- Choose one capability disposition used throughout the catalog:
covered: an accepted public capability already satisfies the need
partial: existing public coverage leaves a named gap
public_candidate: the capability is reusable and can be independently supported
private_overlay: correct use depends on private context or authority
rejected: the capability is unsafe, unsupported, obsolete, duplicative, or not permitted
- For current catalog work, use
original or an honestly preserved historical clean-room method. Do not introduce new adapted, vendored, or third-party reference-only implementations.
- Record provenance before materializing the transfer using the exact schema field names, including
pinned_revision, reviewed_on, and reviewed_material.
- Apply the smallest authorized change. Preserve required notices and avoid unrelated updates.
- Validate the result in every supported host and record rereview triggers, update policy, and revocation path.
Stop conditions
Stop on any third-party skill-catalog source, unclear ownership, incompatible or absent licensing, unverifiable artifact origin, unexplained binary content, unsafe activation, or a review scope that cannot cover the proposed package. Do not install or materialize a rejected source.
Example
Synthetic example; not an observed client result.
Input: An owned skill transfer lacks an exact source revision.
Output: Transfer is blocked until source identity and ownership evidence are established. Do not copy an unidentified payload into the destination.
1---2name: review-skill-import3description: "Reviews an owned skill transfer when explicitly asked to import it; checks ownership, license, exact source, and public boundaries before any copy or installation."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-skill-import7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "explicit"11 provenance: "original"12 risk_class: "trust-decision"13---1415# Skill Import Provenance1617Keep owned original work and primary authorities separate from external rejection evidence. Read [provenance record](references/provenance-record.md) before proposing an owned-source transfer.1819## Workflow20211. Resolve the exact owned source, revision, artifact, author, license, destination, and authority for the proposed transfer.222. If the source is a third-party skill catalog, stop. Do not track, cite, mirror, adapt, vendor, or use it as an implementation source. Keep authorized investigation outside this repository and its distributions. Separately governed private research may retain original assessments, permalinks, and hashes under its own policy; it cannot supply imported prose, structure, or implementation authority here. Public behavior still requires owned work, primary authorities, and original evidence.233. Confirm ownership, or separately documented authority, for every transferred file, and confirm that the license permits the destination use.244. Inventory the exact files proposed for transfer and their dependencies, scripts, assets, hooks, and network behavior.255. Run or obtain a security review appropriate to the package's influence and execution surface.266. Choose one capability disposition used throughout the catalog:27 - `covered`: an accepted public capability already satisfies the need28 - `partial`: existing public coverage leaves a named gap29 - `public_candidate`: the capability is reusable and can be independently supported30 - `private_overlay`: correct use depends on private context or authority31 - `rejected`: the capability is unsafe, unsupported, obsolete, duplicative, or not permitted327. For current catalog work, use `original` or an honestly preserved historical `clean-room` method. Do not introduce new `adapted`, `vendored`, or third-party `reference-only` implementations.338. Record provenance before materializing the transfer using the exact schema field names, including `pinned_revision`, `reviewed_on`, and `reviewed_material`.349. Apply the smallest authorized change. Preserve required notices and avoid unrelated updates.3510. Validate the result in every supported host and record rereview triggers, update policy, and revocation path.3637## Stop conditions3839Stop on any third-party skill-catalog source, unclear ownership, incompatible or absent licensing, unverifiable artifact origin, unexplained binary content, unsafe activation, or a review scope that cannot cover the proposed package. Do not install or materialize a rejected source.4041## Example4243Synthetic example; not an observed client result.4445Input: An owned skill transfer lacks an exact source revision.4647Output: Transfer is blocked until source identity and ownership evidence are established. Do not copy an unidentified payload into the destination.