Skill Mesh v2.0.0

Skill Mesh v2.0.0

Qualified source: ddce08eef3ac65084323d75a150595512ef133c9.

The catalog includes 57 Claude skills and 54 portable skills for Codex and GitHub Copilot. All 42 planned rebuilds and 15 retained candidates have source dispositions. Skills are generated from shared behavior contracts and host adapters; this release does not promise every skill will be shorter.

Installation

Use Windows PowerShell 5.1. Extract the release bundle to a dedicated directory. From that directory, select ONE provider and an explicit target home. The distribution root must contain the provider subdirectory:

powershell -NoProfile -File tools/install-skill-mesh.ps1 -Provider claude -Home C:\path\to\consumer-home -DistDir .\dist

For Codex use -Provider codex; resolve the effective Codex home with tools/probe-codex-skills.ps1 as described in documentation/providers/codex.md. For GitHub Copilot use -Provider gpt. Discovery roots are .claude/skills, .agents/skills, and .github/skills, respectively. Start a fresh host session after installation. Installing a profile does not authenticate its host or prove every native capability is available.

Upgrade and rollback

Before upgrading, retain the previous distribution and a separate backup of the target discovery tree and .skill-mesh-install.json. Stop sessions that might write those paths while changing installations. Run the same installer against the new distribution and existing home. It verifies ownership and current bytes; if it refuses a collision, inspect the conflict rather than adding -Force routinely.

To remove this profile's unchanged owned files:

powershell -NoProfile -File tools/install-skill-mesh.ps1 -Provider claude -Home C:\path\to\consumer-home -Uninstall

To restore the preserved previous generated profile, use this release's installer with -DistDir pointing to the preserved previous distribution after the current profile is uninstalled. Qualification exercises this installer restoring preserved pre-rebuild profile bytes; it does not establish compatibility of an older installer or every historical v1 release. Legacy or hand-maintained installations require their own preserved backup and the documented migration procedure; uninstall alone does not reconstruct legacy files. Modified files can require explicit resolution. Keep unrelated user files intact.

Known limitations

• Session advice passes the selected safety/provenance checks and emits a four-line final report, but may add a progress sentence and vary triage-line formatting. The operator accepted this presentation limitation for v2; strict formatting is deferred to v3.

• Native UAT's selected fail-stop smoke passed. Its first command's exit-code wrapper did not independently capture the inner printf exit; matching output was observed. This is a scoped result, not blanket workflow qualification.

• Judge Motion is Claude-native and needs its packaged runtime dependencies, browser runtime, independent judge capability, and native permission approval. The selected live smoke passed: six mechanical assertions, three independent Sonnet judge returns, calibration PASS, and a real missing-rubric capture that correctly escalated without judging. Protected report writes beneath .claude required native safety review; command allow rules alone did not enable those writes.

• Session-dependent actions require authoritative host session identity and the permissions named by the skill. Earlier project SET/CLEAR observations without session identity and Codex read-only holds remain scoped holds; this release does not claim those unavailable write paths succeeded.

• claude-oauth-auth, context-slim, and judge-motion are Claude-only. PowerShell 7 compatibility is not claimed.

• The citation utility dependency is published on skill-mesh-v2/overview-filters in aberson/citation-needed, not merged into that project's main branch.

Qualification

Full root suite: 2128 passed, 16 skipped in 15560.49s (4:19:20). All three final profiles passed fresh install, repeat install, upgrade from preserved pre-rebuild profiles, uninstall preserving unrelated files, and prior-profile byte restoration with the final installer. This is not proof of every historical v1 installer or restoration of user-modified files. The preserved prior profiles were not a published v1 release.

Archive SHA-256 is in the attached checksum file; generated-file hashes are in the bundle CHECKSUMS.txt. Normal installed profiles were not changed during qualification.

Workflow documentation

Browse the v2 README, complete skill reference, and 57 source-linked workflow diagrams. Documentation was published after the qualified bundle; the release tag and assets are unchanged.