The right skills, current everywhere.
Discover Agent Skills or bring your own. Denju keeps public subscriptions, private skills, shared skills, packs, and team skill sets current wherever your agents run.
denju · 伝授 — Japanese for passing on or transmitting knowledge or a skill.
Your own contract-review workflow, references, scripts, and supporting files.
Folders are simple.
Copies drift.
Agent Skills are ordinary directories. That is great until the same skill exists on three machines, in two harnesses, and on a teammate's laptop. Denju replaces manual copies with durable relationships.
review/v4MacBookreview/v3Workstationreview-copy/?teammate@alice/review → latestDenju keeps the copies true.Find useful skills before you make your own.
Search the public registry, inspect authors and releases, browse topics, and see what people star. You do not need an account to search, inspect, or subscribe.
Discover and subscribe →legal research⌘ KInstall once. Then stop thinking about updates.
A subscription means “keep this skill here.” Follow latest for automatic updates or pin one immutable release when stability matters.
@alice/reviewsubscriptionKeep it private.
Keep it everywhere.
Import a skill once. It stays private, and your saved changes follow you across signed-in devices. No publish step. No second sync tool.
Private multi-device sync →@alice/my-skillShare with one person,
not the internet.
Grant one Denju user access with denju share. They choose whether to subscribe; if they do, their private copy follows your saved changes while the skill stays out of the public catalog.
Private while you work.
Public when you decide.
Personal skills start private. Publishing turns the current private state into an immutable numbered release for everyone else. Fix mistakes by publishing the next release, not by rewriting history.
Publishing releases →@alice/reviewsaved changesdenju publish @alice/review→A pack is just a set of skills.
Group the skills that belong together. Add one, remove one, follow latest, or pin a version. One pack subscription keeps the whole set current.
Packs →@northstar/packs/legal-corev18Private to the team
by default.
A normal team publish creates a team-only release. Put private team skills in an assigned pack and Denju keeps the approved set on every current member's computers—and on future members when they join.
Teams and assigned packs →Edit somebody else's skill.
Keep your work.
Editing a subscribed skill does not mutate upstream. Denju turns your change into a fork, lets you sync upstream explicitly, and lets you propose the result back when it is ready.
Forks and proposals →Go offline. Come back.
Catch up to now.
Private edits queue locally. When connectivity returns, Denju syncs current state rather than replaying every missed event. Concurrent edits merge when they can; real conflicts preserve both sides.
Sync and conflicts →Rename it. Move it.
Retire it without surprises.
Rename skills and packs, move them into teams, deprecate old ones, unpublish, export, or delete. Existing relationships follow the underlying skill instead of breaking on every name change.
Manage skills and packs →@alice/reviewrename@alice/code-review@alice/code-reviewtransfer@acme/code-review@acme/code-reviewdeprecate→ @acme/review-v2Verify what Denju can verify.
Denju verifies access, skill structure, hashes, and complete downloads before updates become visible. It does not pretend to know whether arbitrary skill instructions are safe; subscribing remains a trust decision.
Trust and safety →The hosted registry.
Or your registry.
Run the same open-source denju-server with PostgreSQL and S3-compatible storage. The client experience stays the same; only the registry origin changes.
Your first skill is four commands away.
Setup, search, and public subscriptions are anonymous. Claim an identity later when you need private account features.
$ denju setup
$ denju search "react performance"
$ denju show @ashray/react-performance
$ denju subscribe @ashray/react-performance