The foundation: one vault, every agent.
The first development version brings a local skill vault, a desktop workspace, and an explicit relay system together. Here’s what is implemented in the app so far.
No published versions yet. This initial entry records what’s present in the development app; the date above is a review date, not a release date.
01
Vault & library
- Create a local vault or open an existing one. Canonical skill files remain in a regular folder, readable without SkillRelay.
- Browse skills in grid or list view, search by name and description, and filter between your own skills and imports.
- Create skills with instructions, a description, license information, and agent compatibility settings. Edit your own skills and add text resources.
- Inspect SKILL.md, package files, validation reports, agent compatibility, source information, and version history in the skill viewer.
02
Imports & sources
- Import skills from local folders, ZIP or .skill archives, and Git repositories, including repository subfolders and references.
- Preview package files, content hashes, compatibility reports, diagnostics, and duplicate-name conflicts before importing.
- Resolve imports explicitly: keep the existing skill, import a new one, replace an eligible unchanged import, or create a fork.
- Scan agent skill directories to discover existing skills and identify duplicates, vault matches, conflicts, and shared visibility.
03
Ownership & provenance
- Preserve the original source location, source kind, and Git revision when available. Imported metadata cannot grant local ownership.
- Keep imported skills read-only in the SkillRelay editor. Fork a skill into My Skills to customize it independently.
- Record a fork’s origin skill, content version, source, and creation time alongside its own history.
04
Versions & updates
- Save immutable, content-addressed version snapshots. Display labels or content hashes without inventing semantic version ordering.
- Check imported sources for updates on demand. Preview added, modified, and removed files, updated instructions, and compatibility diagnostics before applying changes.
- Pin an imported skill or ignore a particular upstream content hash to control update decisions.
- Preview and restore earlier versions while preserving current content for recovery. Accept reviewed changes made outside SkillRelay as a new vault version.
05
Agents & relay
- Add local destination integrations for Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
- Inspect installation evidence, native paths, shared discovery aliases, and agent-specific compatibility notes.
- Choose global or project scope and preview the exact source, target path, relay method, and agents that may discover the destination.
- Create live symlinks where directory-link discovery is documented, or explicitly choose a materialized copy. Use copies for Cursor, Copilot, and OpenCode while link discovery remains unverified.
- Review managed distributions, refresh eligible copies, restore missing relays, remove verified distributions, or detach management while retaining files.
06
Validation & Doctor
- Parse the portable Agent Skills format and report frontmatter, naming, description, resource, and agent-extension diagnostics.
- Report incompatible metadata and environment requirements before relay. Format validation is separate from a security review of skill instructions.
- Inspect vault integrity, version snapshots, skill validation, and managed destinations with local health checks.
- Distinguish changes to the canonical vault from copy drift, broken links, missing targets, blocked distributions, and corrupt metadata.
- Present findings for explicit review and reconciliation without background source checks or automatic repairs.
07
Filesystem safeguards
- Revalidate content, paths, and ownership when applying a preview. Refuse modified or unmanaged targets rather than overwriting them.
- Bound package sizes and tree depth; reject traversal, unsafe links, duplicate archive paths, and unsupported metadata schemas.
- Use vault locking, exclusive creation, recoverable replacements, and distribution journals to make conflicting or interrupted operations visible.
- Preserve removed materialized copies in recovery folders. Do not recursively delete agent target directories.
- Treat imported content as data: do not execute skill scripts, render imported HTML, or load remote preview images. Remote Git imports use restricted HTTPS operations.
08
Desktop, CLI & Git
- Introduce a React desktop workspace with Library, My Skills, Agents, Updates, Sources, Health, and Settings, backed by Tauri 2 and a shared Rust core.
- Provide CLI commands for status, list, agents, doctor, and init, plus typed JSON requests and a newline-delimited RPC mode.
- Inspect Git status, initialize a vault repository, and create an explicitly confirmed local commit. No automatic commits or pushes.
- Keep the app local-first, with no app account requirement, telemetry, automatic uploads, registry, or marketplace.
09
npm / pnpm CLI
- Add the @skillrelay/cli Node launcher for the existing Rust CLI, with version-matched native packages targeting macOS, Windows, and Linux on x64 and ARM64.
- Check the packaged binary’s integrity and forward arguments, input, output, and exit status to the same native engine. The launcher performs no runtime downloads or telemetry.
- Add source build, package, and local installation verification workflows, plus the skills list alias. Public npm installation remains pending publication and release verification.
10
Developer foundation
- Add core workflow tests for imports, parsing, path handling, ownership, relay recovery, update decisions, rollback, drift, and vault locking.
- Add a browser E2E harness that exercises the same Rust operations inside an isolated temporary home.
- Include an MIT license, security policy, contribution guidelines, and code of conduct.
Current limits
- This entry documents the current development source. No tagged release or packaged download has been verified.
- Agent integrations target local environments. Shared skill folders can be visible to multiple agents; local relays do not install skills in cloud sessions.
- Platform support depends on the build environment. Windows junction creation is not enabled; Linux and Windows readiness is not established by a macOS or browser test.
- Discovery, a public registry, publishing, and a marketplace remain future directions, not features in this version.