Portable Skill Authoring
Create one canonical workflow source and validate its client projections.
Read client adapters when invocation controls, packaging, or generated Codex, Claude, and Antigravity output are in scope.
Workflow
- Establish the capability gap, target requests, near misses, conflicting skills, supported clients, and authority boundary.
- Confirm that the capability belongs in public core, a private overlay, or neither. Resolve license and source provenance before writing.
- Choose a concise name and a discriminating description whose first clause carries the main trigger.
- Keep the entrypoint focused on decisions the host would not make reliably without it. Move conditional detail into small, linked references.
- Choose implicit or explicit invocation from workflow intent. Do not grant tools merely because the workflow might use them.
- Add positive, near-miss, conflict or safety, output-quality, and installed-versus-baseline evaluations.
- Generate native adapters and packages from canonical source. Validate schema, links, policy mapping, deterministic output, package layout, provenance, originality, and public boundaries.
- Record observed behavior separately for every client surface. Do not infer parity from compatible files or another client result.
Boundaries
- Prefer the host's native skill creator when the task is limited to that host, but preserve this catalog's portable acceptance contract.
- Do not copy a popular skill because its repository is public. Pin license and revision, review the full influence surface, and author independently when clean-room treatment is required.
- Do not bundle hooks, agents, MCP servers, dependencies, broad permissions, or executables without an explicit later release decision.
Output
Report the capability, routing, invocation policy, canonical changes, adapters,
provenance, security, evaluations, validation, and observed client limits. These
are required meanings, not mandatory headings; match detail to the request.
Test concise and requested long-form outputs, competing instructions, partial
failure, stale handoffs, and interruptions. Keep shared meaning canonical and
native loading and invocation controls in generated adapters. A slash command
does not prove explicit-only enforcement; exclude those workflows from an
unverified surface.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: A client has a manual skill command but no verified implicit-selection control.
Output: Keep explicit-only workflows unavailable on that surface until the control is verified. File compatibility does not establish behavioral parity.
1---2name: author-skill3description: "Authors portable skills when asked to create or revise SKILL.md workflows and client distributions; preserves routing, provenance, and invocation controls rather than treating ordinary docs as skills."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/author-skill7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "implicit"11 provenance: "original"12 risk_class: "bounded-execution"13---1415# Portable Skill Authoring1617Create one canonical workflow source and validate its client projections.1819Read [client adapters](references/client-adapters.md) when invocation controls, packaging, or generated Codex, Claude, and Antigravity output are in scope.2021## Workflow22231. Establish the capability gap, target requests, near misses, conflicting skills, supported clients, and authority boundary.242. Confirm that the capability belongs in public core, a private overlay, or neither. Resolve license and source provenance before writing.253. Choose a concise name and a discriminating description whose first clause carries the main trigger.264. Keep the entrypoint focused on decisions the host would not make reliably without it. Move conditional detail into small, linked references.275. Choose implicit or explicit invocation from workflow intent. Do not grant tools merely because the workflow might use them.286. Add positive, near-miss, conflict or safety, output-quality, and installed-versus-baseline evaluations.297. Generate native adapters and packages from canonical source. Validate schema, links, policy mapping, deterministic output, package layout, provenance, originality, and public boundaries.308. Record observed behavior separately for every client surface. Do not infer parity from compatible files or another client result.3132## Boundaries3334- Prefer the host's native skill creator when the task is limited to that host, but preserve this catalog's portable acceptance contract.35- Do not copy a popular skill because its repository is public. Pin license and revision, review the full influence surface, and author independently when clean-room treatment is required.36- Do not bundle hooks, agents, MCP servers, dependencies, broad permissions, or executables without an explicit later release decision.3738## Output3940Report the capability, routing, invocation policy, canonical changes, adapters,41provenance, security, evaluations, validation, and observed client limits. These42are required meanings, not mandatory headings; match detail to the request.4344Test concise and requested long-form outputs, competing instructions, partial45failure, stale handoffs, and interruptions. Keep shared meaning canonical and46native loading and invocation controls in generated adapters. A slash command47does not prove explicit-only enforcement; exclude those workflows from an48unverified surface.4950Read [the original acceptance example](references/continuity-example.md) when checking this behavior.5152## Example5354Synthetic example; not an observed client result.5556Input: A client has a manual skill command but no verified implicit-selection control.5758Output: Keep explicit-only workflows unavailable on that surface until the control is verified. File compatibility does not establish behavioral parity.