Skip to main content
Auto-memory
Retell + Twilio
MCP ecosystem
Founder Pres.
Obsidian + QMD
Review pass
Claude / Codex
Convex
75K+ sold
SwiftUI CloudKit
Next.js + Vercel
1,350+ locations
Shopify
Session notes
Founder
MCP forks
<60s response
Operator chapters
Founder & CEO
121+ skills
Six figures raised
Founder office
back to grid
Projects2026

Skill Sync

A local-first macOS app for managing the skills, agents, and rules under my coding tools. It finds the canonical source, flags stale mirrors and conflicts, shows local usage evidence, and edits Markdown through a review gate.

brew install --cask chountalas/tap/skill-sync
Local-first
no hosted analytics
Canonical graph
source, mirror, conflict
Conflict-safe
autosave and mirror review
Homebrew cask
public install path
§01The workLive system

Skill Sync turns scattered skill files, agent definitions, rules, mirrors, remotes, and usage traces into one inspectable Mac app.

Skill Sync
SwiftUI · local files · usage evidence

A manager for the agent skill library.

Skill Sync turns scattered skill files, agent definitions, rules, mirrors, remotes, and usage traces into one inspectable Mac app.

Skill Sync's light Manager view showing search, filters for status and usage, and a grouped table of standalone skills.
Skill Sync's dark Matrix view showing agent-harness columns and blue markers where a skill is installed or canonical.
Skill Sync's dark Reader view showing a selected skill with metadata, install location, and rendered Markdown.
The workManager view. Search, status filters, usage filters, grouping, and bulk cleanup across the local library. / Matrix view. Source coverage across the agent harnesses, with canonical and installed copies visible at a glance. / Reader view. A selected skill with source metadata, preview/edit controls, and rendered Markdown.
§02The pipelineEnd-to-end flow
01

Scan

Read local skill, agent, and rule sources into one normalized library.

skills · agents · rules
02

Group

Group linked installs and duplicate copies into a canonical source graph before any write happens.

canonical · mirror · conflict
03

Measure

Build aggregate usage evidence from local histories with confidence labels per signal.

local histories
04

Edit

Preview Markdown, compose changes with a local agent when useful, and review the diff before saving.

preview · compose · diff
§03What I builtPieces that compound

The important pieces are scanner, source grouping, usage evidence, conflict-safe editing, and release readiness.

Source-release ready.

The public repo carries the release materials that matter for source users: license, contribution docs, privacy and security notes, CI, third-party notices, and release-safety checks.

MIT docs · checks · CI

Canonical source graph.

The app resolves linked installs and duplicate copies into one source graph, so I can see which file is canonical and which installs are just mirrors.

resolved paths · install relations

Sync and conflict states.

Mirrors are labeled before any write happens. If a copy is stale it can be synced; if it changed independently, the app treats it as a conflict instead of overwriting it.

in sync · stale · standalone · conflict

Local usage evidence.

Usage is pulled from local history signals and stored as aggregate metadata. Confidence labels keep weak references from masquerading as strong evidence.

aggregate histories · confidence labels

Coverage matrix.

The Matrix view shows which tools have each skill installed, where the canonical source lives, and which harnesses are missing or stale.

harness-by-skill map

Diff-gated AI editing.

The editor can ask a local agent to rewrite a skill with install context and usage evidence, then shows the diff before anything is applied.

local agent compose
§04Build rulesLocal-first library control

The app is allowed to organize the skill system, but it has to make source ownership and write behavior obvious.

Selected rulespublic app · local evidence
  1. Treat the resolved canonical file as the source of truth, not the first matching filename.
  2. Show every linked install before syncing mirrors.
  3. Keep usage tracking local and store aggregate evidence, not full session histories.
  4. Label confidence by adapter so weak evidence does not masquerade as certainty.
  5. Use a diff review gate before AI-composed Markdown edits are applied.
  6. Keep release checks in the repo as part of the public source path.
§05StackEvery tool earns its line
SwiftUI / UISwift 6 / LanguageSwift Package Manager / BuildApplication Support / Local stateFile watchers / Rescan triggersMarkdown / Skill sourceLocal agent compose / Edit passSSH / Remote syncRelease-safety checks / Source readinessmacOS 14+ / Target
§06ArtifactsReceipts and public proof

The app and source are public. The screenshots show the current working surfaces.