@vocdoni/skills
v0.5.2
Published
Vocdoni's curated skills for AI coding assistants (Claude Code, Cursor, Cline, and other Anthropic-skill-compatible clients).
Readme
Vocdoni Skills
Curated Agent Skills from Vocdoni, packaged as a Claude Code plugin marketplace and also installable via npx for any client that reads a skills directory (Cursor, Cline, Zed, …) or via the Claude API.
# Claude Code — add the marketplace, then install what you want
claude plugin marketplace add vocdoni/skills
# Building on Vocdoni? These are for you:
claude plugin install vocdoni-sdk@vocdoni
claude plugin install davinci-sdk@vocdoni
claude plugin install vocdoni-integrator-sdk@vocdoni
# Internal tooling we use at Vocdoni:
claude plugin install vocdoni-go@vocdoni
claude plugin install vocdoni-stripe@vocdoni
claude plugin install vocdoni-internal-oauth@vocdoni
claude plugin install vocdoni-ui-style@vocdoni
claude plugin install agentic-dev@vocdoni
claude plugin install vocdoni-comments@vocdoni
claude plugin install vocdoni-contributing@vocdoni
claude plugin install pi-subagent@vocdoni # MCP server + agents — needs Pi (see its README)
# Or grab everything in one shot (skill plugins only; pi-subagent is Claude Code-only)
npx @vocdoni/skills install
# Later, to upgrade (see "Upgrade" below)
claude plugin marketplace update vocdoni
claude plugin update agentic-dev@vocdoni # repeat per installed pluginSkills for integrators
SDK references for anyone building voting on Vocdoni — clients, partners, and third-party developers.
🗳️ vocdoni-sdk — Vocdoni voting SDK
| Skill | What it covers |
| -------------------------- | ------------------------------------------------------------------------------------------------------- |
| vocdoni-sdk | Exhaustive @vocdoni/sdk reference — client, accounts, census, all election variants, anonymous (ZK), CSP, Census3 — plus runnable recipes. |
| vocdoni-ballot-protocol | The on-chain data model the SDK serialises into: ballot encoding, results matrix, parameter semantics. |
🔐 davinci-sdk — Vocdoni Davinci (zk voting) SDK
| Skill | What it covers |
| ------------- | ------------------------------------------------------------------------------------------------------- |
| davinci-sdk | The @vocdoni/davinci-sdk facade — create a process, cast encrypted (ElGamal + zk-SNARK) votes, every census type (Merkle/dynamic/CSP/on-chain), ballot-mode configuration, lifecycle, and results — plus protocol grounding and runnable recipes. |
🧩 vocdoni-integrator-sdk — Vocdoni Integrator SDK
| Skill | What it covers |
| ---------------- | ------------------------------------------------------------------------------------------------------- |
| vocdoni-integrator-sdk | The Integrator SDK packages — @vocdoni/api-client, @vocdoni/api-voting, @vocdoni/react-providers, @vocdoni/react-components: CSP auth flow, vote relay, ballot building, and React integration, with runnable recipes. |
This is a remote plugin: the skill lives in the vocdoni-integrator-sdk repo and is cloned (or pulled) on demand by the npx CLI — pass --offline to skip fetching and use the cached clone.
Building the voting UI itself? vocdoni-ui-style (listed under the team skills) carries the product look of the Vocdoni app, including the white-label accent for an organization's own color.
Skills for the Vocdoni team
Tooling we use internally for our own development workflow. Nothing stops you from installing these, but they target how we work rather than the Vocdoni platform.
🐹 vocdoni-go — Go engineering
| Skill | What it covers |
| -------------------- | ------------------------------------------------------------------------- |
| go-best-practices | Rob Pike's Go Proverbs — idiomatic & architectural defaults. |
| go-code-quality | Production checklist: domain types, error contracts, context, goroutines. |
| go-modern | Version-aware modern Go syntax. Reads go.mod to pick the right target. |
💳 vocdoni-stripe — Stripe operations for the SaaS
| Skill | What it covers |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| stripe-subscription | Create a subscription for an existing customer through the Stripe CLI (or MCP): prompts for the minimum inputs, clones per-customer Custom / Integrator Starter plan products, handles discounts and collection, confirms before writing. |
Requires jq and either the Stripe CLI with a started session (stripe login, then stripe agent setup for its own skill) or a Stripe MCP server.
🔑 vocdoni-internal-oauth — staff sign-in for internal tools
| Skill | What it covers |
| ------------------------ | -------------- |
| vocdoni-internal-oauth | Add Google sign-in for @vocdoni.org accounts to an existing internal web tool through the central OpenID Connect provider at oauth.vocdoni.org: register the tool as a client in vocdoni/oauth, wire the Go kit (vocauth) or the Node/TypeScript kit (@vocdoni/oauth, Express and Fetch-API frameworks), use any OIDC library or oauth2-proxy for other stacks, develop locally against the dev provider, migrate away from a shared password, rotate cookie keys and troubleshoot. |
🎨 vocdoni-ui-style — Vocdoni look and feel
| Skill | What it covers |
| ------------------ | -------------- |
| vocdoni-ui-style | Build UIs that look and behave like Vocdoni's products, in its two visual modes: editorial (vocdoni.io: cream surfaces, warm ink, Fraunces serif headings, green accent, yellow eyebrow dot) for marketing, landing and docs pages, and product (vocdoni-app: white, Inter at light weights, monochrome or white-label accent) for dashboards, voting pages and admin tools. Ships tokens for Tailwind v4 + shadcn/ui, Chakra UI v3 and plain CSS, React components, logo files, reference screenshots, runnable HTML examples (landing, voting flow, dashboard, sign-in, vote builder, transactional email), worked React recipes, step-by-step UX flows for voting, vote building and onboarding, specs for docs sites and result PDFs, copy rules, and a brand style checker (scripts/check-style.mjs). |
🧭 agentic-dev — subagent-driven development with independent audits
| Skill | What it covers |
| ---------------------- | -------------- |
| subagent-driven-development | How the main session runs any multi-step change that will be merged: size the work (spike / bounded / architectural), write and audit a spec, have a plan drafted and pre-flight audited, dispatch one subagent per task with a strict prompt contract, review every diff, run a whole-branch gate audit, then merge and release only on the owner's OK. An auditor model, the strongest one available, is the independent auditor and consultant; a ledger in .delivery/ survives context compaction. The skill names model roles rather than models: references/models.md maps them to today's defaults (see that file for today's defaults), moves to newer versions as they ship, and picks a model with similar strengths when a default is unavailable. Ships audit and dispatch prompts, spec and plan templates, and init-workspace.sh / task-brief.sh. |
The plugin also installs a SessionStart hook so the model loads the skill on its own for feature, refactor, protocol, migration, multi-repo, deploy and benchmark work, and resumes any unfinished .delivery/ ledger in the current repo. The hook is Claude Code-only; an npx install gets the skill, which still triggers from its description.
💬 vocdoni-comments — code comments
| Skill | What it covers |
| ---------- | -------------- |
| comments | How to write code comments (doc, inline, JSDoc): 1-3 lines per block that say the why or a constraint the code can't show, without restating code, narrating history or repeating documented flows, and with claims that match the code. trim.md shortens existing comments, either the blocks a branch added (/comments trim) or every long block in a project or folder (/comments trim project [path]; a plugin install namespaces them as /vocdoni-comments:comments trim), keeping anything only the comment said and reporting where each dropped piece lives. |
📝 vocdoni-contributing — what the agent posts on the git host
| Skill | What it covers |
| -------------- | -------------- |
| contributing | The rules for everything the agent writes on GitHub or GitLab: an opening line naming the model and the user it acts for, no Co-authored-by trailer, every PR linked to an issue (found, or opened before the PR), an epic's PRs stacked on each other with gh stack and merged in one go, length limits and structure for PR/MR descriptions and issues, findings of about three sentences in reviews (nits marked "Nit:"), and reviews posted as reviews marked "Approve" or "Request changes". |
The plugin also installs a SessionStart hook that injects the same contributing body into every Claude Code session, so the rules hold even when a PR is one step of a larger task and the skill's description never matches. The hook reads skills/contributing/SKILL.md directly, so the skill is the only place to edit. The hook is Claude Code-only; an npx install gets the skill, which still triggers from its description.
🤖 pi-subagent — delegate to Pi subagents
Delegate work to named Pi subagents — reusable personas, each with its own model and tools (including MCP tools) — and to bounded one-off coding tasks. Unlike the skill plugins above, this one bundles a local MCP server that launches Pi (pi --mode rpc), isolates code edits in a detached git worktree, and hands back a summary plus a diff to review. Changes are never applied automatically.
From Claude: "use pi-agent web-scout to research Vocdoni" → a sourced summary produced by Pi.
| Provides | What it is |
| -------------------------------------------------- | ------------------------------------------------------------------------ |
| pi_run_agent, pi_list_agents | Run / list named .md subagents (persona + model + tools, incl. MCP). |
| pi_run_task, pi_get_status, pi_get_result, … | Bounded coding tasks with worktree isolation and reviewable diffs. |
Requires Pi (and, for MCP-backed agents, the pi-mcp-adapter). See the pi-subagent README for setup, creating and configuring subagents, real examples, and the full tool reference.
More plugins (vocdoni-typescript, vocdoni-solidity, …) will land under plugins/ over time.
Install
Claude Code
# Add this repo as a marketplace
claude plugin marketplace add vocdoni/skills
# Install all current plugins
claude plugin install vocdoni-sdk@vocdoni
claude plugin install davinci-sdk@vocdoni
claude plugin install vocdoni-integrator-sdk@vocdoni
claude plugin install vocdoni-go@vocdoni
claude plugin install vocdoni-stripe@vocdoni
claude plugin install vocdoni-internal-oauth@vocdoni
claude plugin install vocdoni-ui-style@vocdoni
claude plugin install agentic-dev@vocdoni
claude plugin install vocdoni-comments@vocdoni
claude plugin install vocdoni-contributing@vocdoni
claude plugin install pi-subagent@vocdoni # see plugins/claude-pi-subagent/plugins/pi-subagent/README.mdIterating locally? Point the marketplace at a checkout instead:
claude plugin marketplace add /path/to/skillsTo have a repo's contributors install the plugins, commit this as the repo's .claude/settings.json. Once a contributor trusts the folder, Claude Code registers the marketplace and enables these plugins:
{
"extraKnownMarketplaces": {
"vocdoni": { "source": { "source": "github", "repo": "vocdoni/skills" } }
},
"enabledPlugins": {
"vocdoni-comments@vocdoni": true,
"vocdoni-contributing@vocdoni": true
}
}npx (any client that reads a skills directory)
Installs into ~/.claude/skills/ by default (where Claude Code looks at user scope).
# All plugins at once
npx @vocdoni/skills install
# A whole plugin (short form: 'go' → 'vocdoni-go', 'sdk' → 'vocdoni-sdk')
npx @vocdoni/skills install --plugin go
npx @vocdoni/skills install --plugin sdk
npx @vocdoni/skills install --plugin integrator-sdk # remote plugin, cloned on demand
npx @vocdoni/skills install --plugin davinci-sdk # full name (no vocdoni- prefix)
npx @vocdoni/skills install --plugin agentic-dev # skill only; the SessionStart hook is Claude Code plugin-only
npx @vocdoni/skills install --plugin ui-style # 'ui-style' → 'vocdoni-ui-style'
npx @vocdoni/skills install --plugin comments # 'comments' → 'vocdoni-comments'
npx @vocdoni/skills install --plugin contributing # 'contributing' → 'vocdoni-contributing'; skill only, the SessionStart hook is Claude Code plugin-only
# A single skill, looked up across plugins
npx @vocdoni/skills install go-modern
# Project-local, as a symlink for live updates while authoring
npx @vocdoni/skills install --plugin sdk --dest ./.claude/skills --symlinkOther commands: list, uninstall, plus --force, --dry-run. Full help:
npx @vocdoni/skills --helpManual / Claude API
Skills are plain directories at plugins/<plugin>/skills/<skill>/.
- Manual: copy or symlink into
~/.claude/skills/(user) or<project>/.claude/skills/(project), or whatever your client reads. - Claude API: upload
SKILL.mdand its supporting files via the Skills API.
Upgrade
Claude Code
Third-party marketplaces such as this one do not auto-update by default, so installed plugins stay at the version you installed until you upgrade them:
# Refresh the marketplace listing
claude plugin marketplace update vocdoni
# Update each plugin you installed
claude plugin update vocdoni-sdk@vocdoni
claude plugin update davinci-sdk@vocdoni
claude plugin update vocdoni-integrator-sdk@vocdoni
claude plugin update vocdoni-go@vocdoni
claude plugin update vocdoni-stripe@vocdoni
claude plugin update agentic-dev@vocdoni
claude plugin update vocdoni-comments@vocdoni
claude plugin update vocdoni-contributing@vocdoni
claude plugin update pi-subagent@vocdoniUpdates apply to new sessions; in a running session, run /reload-plugins. Run claude plugin list to see which plugins and versions you have.
From inside a session you can do the same with /plugin: on the Marketplaces tab, select vocdoni and choose Update marketplace to update every plugin you installed from it, or Enable auto-update to have Claude Code update them in the background at the start of each session.
A plugin only updates when its version changes, so an unreleased change on main does not reach installed users until the plugin is released (see Releasing).
npx
Re-run the install against the latest package. --force overwrites the skill directories that are already there:
npx @vocdoni/skills@latest install --force # everything
npx @vocdoni/skills@latest install --plugin agentic-dev --force # one pluginPin @latest, or npx may reuse an older cached copy of the CLI. Remote plugins such as vocdoni-integrator-sdk are re-fetched on every run unless you pass --offline.
Installed with --symlink from a checkout? git pull in that checkout is enough; the links already point at the updated files.
Manual
Copy the skill directories again over the old ones, or git pull if you symlinked them.
Layout
.
├── .claude-plugin/marketplace.json # Marketplace manifest
├── plugins/
│ ├── vocdoni-go/
│ │ ├── .claude-plugin/plugin.json
│ │ └── skills/<skill>/SKILL.md
│ ├── vocdoni-sdk/
│ │ └── …
│ ├── davinci-sdk/
│ │ └── …
│ ├── vocdoni-stripe/
│ │ └── …
│ ├── vocdoni-internal-oauth/
│ │ └── …
│ ├── vocdoni-ui-style/ # skill + tokens, components, logos, examples
│ │ └── …
│ ├── agentic-dev/ # skill + SessionStart hook (hooks/)
│ │ └── …
│ ├── vocdoni-comments/
│ │ └── …
│ ├── vocdoni-contributing/ # skill + SessionStart hook (hooks/)
│ │ └── …
│ └── claude-pi-subagent/ # nested marketplace (pi-agent-tools)
│ └── plugins/pi-subagent/ # MCP server plugin + agents — see its README
├── bin/install.js # npx CLI (zero deps, Node ≥ 18)
├── package.json # Published as @vocdoni/skills
├── README.md
├── CONTRIBUTING.md # Authoring guide
└── LICENSE # AGPL-3.0-or-latervocdoni-integrator-sdk has no directory here — it is a remote plugin whose source in marketplace.json points at vocdoni/vocdoni-integrator-sdk.
Contributing
See CONTRIBUTING.md for the skill format, naming rules, and the steps to add a new skill or plugin.
