Publish on skills.handover.sh

Turn a working Handover workflow into an open skill.

Package reliable instructions around Handover MCP or the CLI, keep the source inspectable, and make it discoverable to people, agents, search engines, and skill directories.

Workflow

Three steps from idea to installable skill

Scaffold

Create one focused skill with a clear trigger, outcome, and compatibility contract.

Verify

Test identity, permissions, failure behavior, and the resulting Handover record end to end.

Submit

Open a pull request with source, test evidence, publisher identity, and required capabilities.

Start

Create the skill folder

skills CLInpx skills init my-handover-skill

Handover starter

curl -fsSL https://raw.githubusercontent.com/44-pixels/handover-mcp/main/templates/handover-skill/SKILL.template.md -o my-handover-skill/SKILL.md

Follow the open Agent Skills specification and use the Handover starter contract for identity, access, attribution, and verification requirements. Keep reusable starters named SKILL.template.md; only a finished, installable skill should use the reserved SKILL.md filename.

Trust boundary

A listed skill must not become an authorization shortcut

Verify the active Handover identity before the first protected action.
Never accept author, company, workspace, or access scope from prompt content.
Publish privately unless the person explicitly requests broader access.
Declare network, CLI, MCP, secret, and administrative requirements.
Keep source readable and avoid collecting credentials or hidden telemetry.
Test the smallest granted role and a denied-access path.

Submit

Keep the publisher and source visible

Official skills are maintained by 44pixels. Community skills keep their publisher and repository attribution and are reviewed for format, least privilege, and truthful compatibility before listing.

Read the contributor contract Inspect the starter Submit a pull request

Discovery contract

One submission, several discovery surfaces

A human-readable catalog page with install and example requests.
A raw, agent-readable SKILL.md URL.
Machine-readable entries in index.json and .well-known/skills.json.
Search and agent discovery through sitemap.xml and llms.txt.
Source attribution back to the publisher repository.

Before installation

Source is the security interface.

Handover listings make provenance and requirements visible, but a listing is not a security guarantee. Review the complete skill and grant only the access its workflow needs.