FOR THE LICENSED TEAM
Contributing
claude-kit grows from the people who use it. If you've built an agent, a skill, a profile — or just have a good idea — the easiest way to share it back with your team is from inside Claude Code. A manual path works too.
This is for the licensed team: claude-kit is a licensed product of tuempresa.digital, and contributions go to the private repo your license grants you access to — not to a public, open-source project.
The seamless way — /kit-contribute
In any session with the plugin installed:
/kit-contribute
It walks you through it and opens the PR (or issue) for you:
- Resolves the upstream (
tuempresadigital/claude-kit, the licensed repo) and checks you're logged in (gh auth status). - Asks what you're contributing — an agent, a skill, a profile, or a feature request / idea.
- Assembles the artifact at the right path — and for an agent, de-parameterizes it: your project values (
{{PROJECT_NAME}},{{WING}}, the memory block) are turned back into a reusable template, and anything project-specific or secret is stripped. - Lints it — frontmatter, tool and skill names, no leftover template placeholders.
- Opens the PR to
mainin the licensed repo, in a fresh temp clone, after confirming with you.
You can also just send an idea: it opens a Problem · Proposal · Scope · Why issue instead of a PR.
The manual way
In the licensed repo tuempresadigital/claude-kit, add your file in the matching directory:
| Contribution | Path |
|---|---|
| Agent template | templates/agents/<name>.md (use {{VARS}} + <!-- IF:MEMORY -->) |
| Scaffolded skill | templates/skills/<name>/SKILL.md |
| Plugin skill | skills/<name>/SKILL.md |
| Profile | profiles/<name>.json |
Then open a PR against main. Keep agent and skill files de-parameterized (no project-specific values or secrets), match the existing frontmatter contract, and bump the version in .claude-plugin/plugin.json + .claude-plugin/marketplace.json if it's a user-facing change.
Review & release
A maintainer reviews every PR. After merge, the new version reaches every licensed project via:
claude plugin marketplace update claude-kit-marketplace
claude plugin update claude-kit@claude-kit-marketplace
And inside each project, /kit-update brings the new release in safely — adding what's new without touching your customizations.
Where to go next
- Tailor your team — build the agent or profile you'll contribute.
- Stay updated — how merged changes reach your projects.