# Collaboration Skills 0.1.0

This family gives cross-platform collaborators a small typed projection of a collaboration skill and the field observation that changed its route. The human-readable `SKILL.md` or collaboration account remains semantic authority. JSON makes the current contract, receiving use, standing, evidence, and transfer boundary portable without turning the collection into a router or authority registry.

## Start here

[Browse the repository-local public skills catalog](../../skills/).

| Need | Resource |
| --- | --- |
| Read one live portable contract | [Source authority mapping](../../skills/source-authority-mapping/) |
| Load its typed projection | [Portable skill example](examples/portable-skill.example.json) |
| Understand the exchange shape | [Collaboration skill schema](collaboration-skill.schema.json) |
| See bounded projection lineage | [Retired task-bound projection](examples/retired-projection.example.json) |
| Follow a route-changing observation | [Source authority mapping account](../../skills/source/threadkeeping/collaboration-accounts/2026-08-24-source-authority-mapping.md) and its [typed example](examples/collaboration-account.example.json) |
| Understand the account shape | [Collaboration account schema](collaboration-account.schema.json) |

## Receiving use

The first receiver is the Context Canvas “Skills as Working Affordances” page and its cross-platform adoption kit. A collaborator can begin with the human-readable contract, load the JSON projection into another working environment, bind selected behavior to one named task, and return a material observation through a collaboration account. Direct reasoning remains available when the work needs no skill.

## Forms

- A **portable skill contract** owns one transferable What, When, Boundaries, and Result.
- A **task-bound projection** selects behavior from one contract for one receiving task, authority scope, lifetime, and exit event. Routable projection depth remains one.
- A **collaboration account** records a situated observation, decision effect, route, smallest action, evidence band, transfer boundary, and re-entry trigger.
- A **context capsule** or **skill billet** remains human-readable planning material until a typed receiving use establishes a smaller contract.

## Authority and standing

`semanticAuthorityRef` points to the human-readable source that defines meaning. `sourceRef` points to supporting lineage. The JSON example is an exchange projection and can lag the live source until another reviewed version is published. Routing status, contract-version status, and evidence maturity remain separate dimensions; `routable` does not imply approved, canonical, mature, or authoritative.

The schemas describe structure. Tool authority, publication rights, and execution permission remain with their granting owners. Current user intent, repository evidence, and available tool authority govern each activation and material change.

## Version posture

`0.1.0` is the first receiving-use version. This pre-publication settlement changes branch-bound repository locators into repository-local references while preserving the represented contracts. Exact-version schema bytes become immutable after publication. A structural change receives another exact-version directory. Example revisions that change the represented contract also move with a reviewed family version so a cross-platform receiver can rely on the published shape.

This version concentrates on typed exchange contracts and collaboration accounts. JSON-LD, a registry, a routing service, a composition graph, a hosted workflow, and compatibility automation remain available as later forms when a material receiver calls for them.

## Observation posture

The existing repository schema command covers the Prototype Exemplars, Context Canvas, and Collaboration Skills families in one focused surface. It compiles both Collaboration Skills schemas, validates all three representative examples, affirms repository-local references resolve, and keeps hosted delivery identities independent from source-tree routes. Source review, the linked visitor adoption kit, and natural cross-platform use continue to provide the semantic observation surface.