convez.ai
Skill
proton-pidgeon

claude-skills

proton-pidgeon/claude-skills

Ver no GitHub
InicialPluginScore · de 0 a 100

Reusable Claude Code skills

Instalação

$npx convez-ai proton-pidgeon/claude-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 3 semanas
Versão
—
Issues abertas
0
Contribuidores
3

README

A tradução para o português deste README ainda está na fila.

claude-skills — Kev's Claude Code marketplace & cross-surface sync

A single source of truth that keeps Claude Code in sync across every surface: CLI + Desktop on many hosts, and claude.ai cloud (web + mobile). It's both a plugin marketplace and the sync machinery around it.

⚡ Quick install — run on each host, then restart Claude Code

macOS / Linux (and Windows via Git Bash):

curl -fsSL https://raw.githubusercontent.com/proton-pidgeon/claude-skills/main/install/install.sh | bash

Windows (native PowerShell):

irm https://raw.githubusercontent.com/proton-pidgeon/claude-skills/main/install/install.ps1 | iex

Installs the kev plugin, merges shared settings, and clones the ~/claude-memory vault. Per-host secrets are not synced — re-run the telegram-notify setup (~/.claude/.telegram) and add any MCP tokens locally. Details below.

The two-camp model (why this is split the way it is)

CampSurfacesPersistenceHow it's reached
FilesystemCLI + Desktopshare the same ~/.claude/ per hostplugin install + git-synced memory + session hooks
Cloudweb + mobileephemeral sandbox; ignores ~/.clauderepo-committed SessionStart hook clones resources (cloud/)

Git is the only substrate that reaches both. So: skills/commands/hooks ship as a plugin; memory lives in a git-synced vault (claude-memory); cloud gets a committed bootstrap hook.

Install a host (CLI + Desktop)

One idempotent line — installs the plugin, merges shared preferences, and clones your memory vault:

curl -fsSL https://raw.githubusercontent.com/proton-pidgeon/claude-skills/main/install/install.sh | bash

(Windows native PowerShell: install/install.ps1.) Then restart Claude Code.

Windows note: the plugin's sync hooks (hooks.json) invoke bash, so on macOS/Linux — or Windows with Git for Windows on PATH — they work as-is. For a pure Windows host, install.ps1 also installs native-PowerShell sync hooks (kev-sync-{pull,push}.ps1, fetched into ~\.claude\ and wired into settings.json), so memory sync works without bash. The two are idempotent, so a Windows host that has both bash and PowerShell can run both harmlessly (the second pull/push is a no-op).

Prefer to do it by hand? /plugin marketplace add proton-pidgeon/claude-skills then /plugin install kev@kevdunn.

What's in the kev plugin

TypeItems
Skills/ingest (design docs → specs/tasks), /implement (autonomously build a tasks/ backlog via worktree-isolated parallel agents), /understand (deep-review a repo → on-screen briefing + durable project memory), /security-test (static source-level security audit → prioritized findings report), /portfolio (read-only status sweep across all ~/code-local repos), /peggy (onboard a local service into the Peggy gateway), /peggy-doctor (diagnose a misbehaving Peggy service against the gotcha catalog), /daemonize (install + verify a durable user LaunchAgent pair), /fork-hack (stand up a hack-fork: origin=fork, upstream push-disabled, branch hack), /ship-ios (Xcode Cloud signing-repair runbook), /fleet (run a command across the Tailscale host fleet; default = plugin sync), /commit (commit + push, and PR-merge a feature branch, in one step)
Commands/telegram (notify via your bot), /gui-teardown (quit the VS Code GUI instance a Remote Control session is hosted in + release its caffeinate)
Hooksfully-automatic memory sync (see below)

Memory sync (fully automatic)

Your operational memory lives in the claude-memory vault (a git repo you can open as an Obsidian vault). Each host points Claude's autoMemoryDirectory at its local clone (~/claude-memory by default), and the plugin's hooks keep it in sync:

  • SessionStart → git pull --rebase --autostash the vault (+ refresh the marketplace clone).
  • SessionEnd → commit + push memory changes, conflict-safe. On an unresolvable rebase conflict it aborts the push, leaves your work intact, and fires a Telegram alert so you can merge by hand.

Scripts: plugins/kev/scripts/. The memory directory is read from autoMemoryDirectory — one source of truth, no hard-coded paths.

Cloud (web + mobile)

See cloud/. Commit cloud/settings.json into a repo's .claude/ (or add the one-liner to your cloud Environment setup script) and cloud sessions will clone the skills + memory at startup. Skills injection is solid; cloud memory is best-effort — verify it on a live session.

Secrets — never synced

.credentials.json, ~/.claude/.telegram, .session-config.json, and MCP tokens stay per host. Shared settings (install/settings.shared.json) deliberately exclude permission-bypass flags and host-specific plugins — set those per machine.

Repo layout

.
├── .claude-plugin/marketplace.json     # marketplace manifest (name: kevdunn)
├── plugins/kev/                        # the plugin
│   ├── .claude-plugin/plugin.json
│   ├── skills/{ingest,implement,understand,security-test,portfolio,peggy,peggy-doctor,daemonize,fork-hack,ship-ios,fleet,commit}/SKILL.md
│   ├── commands/{telegram,gui-teardown}.md
│   ├── hooks/hooks.json                # SessionStart/SessionEnd sync
│   ├── scripts/kev-sync-{pull,push}.{sh,ps1}   # bash + native-PowerShell sync
│   └── scripts/kev-gui-teardown.sh     # backs /gui-teardown
├── install/
│   ├── install.sh / install.ps1        # per-host bootstrap
│   └── settings.shared.json            # portable preferences (jq-merged)
├── cloud/                              # claude.ai cloud bootstrap
│   ├── settings.json  bootstrap-cloud.sh  README.md
├── scripts/  per-repo/                 # legacy ingest-only hook (superseded by the plugin)
└── README.md
Ver o original no GitHub

Bom para

Relacionados