Skills & Plugins packages

A package is a bundle of skills, subagents, commands, hooks and plugin settings. Connecto installs it into every project that uses it, and keeps it up to date.

Without packages, a skill you wrote lives in one project's .claude folder and you copy it by hand to the next. With packages, you keep it in one place and each project receives it.

Connecto Home

Packages and automations live in a folder you choose, called Connecto Home. Set it in Settings → CONNECTO HOME.

Connecto Home/
├─ automations/     your automations
└─ packages/        your packages

It is an ordinary folder, so you can keep it in git and share it with your team. It cannot be your home folder, or inside ~/.claude, ~/.codex, ~/.local or ~/Library.

What is in a package

packages/team-tools/
├─ package.json
├─ .claude/
│  ├─ skills/<name>/SKILL.md
│  ├─ agents/<name>.md
│  ├─ commands/<name>.md
│  ├─ hooks/…
│  └─ settings.json
├─ .codex/
│  └─ agents/<name>.toml
└─ .agents/
   └─ skills/<name>/SKILL.md      Codex skills

package.json has four fields and no others:

{
  "name": "Team tools",
  "description": "Review and release workflows for the platform team.",
  "version": 1,
  "extends": "connecto"
}

• extends names a package that is installed first, so yours can build on it.
• version is Connecto's. It goes up by one whenever the content changes. Do not edit it.
• The folder name is the package's id: lowercase letters, digits and -.

The built-in package

Connecto ships one package, and it is the default until you pick another. It contains team workflows in which each tool is reviewed by the other:

• Skills: brainstorm-team, dev-team, strong-dev-team, daily-team and strong-daily-team. They run only when you invoke them.
• Subagents: architect, backend, frontend, developer, finalizer, doc-analyst, requirements-challenger and spec-writer.
• Plugin settings for Claude Code, and a status line showing the model, context use and session cost.

The built-in package cannot be edited or deleted. To change it, create your own package that extends it.

Create a package

1. Open Terminal → Skills & Plugins… and click New package….
2. Give it a name, and optionally a package to extend.
3. A Claude terminal opens in Connecto Home and asks which skills and plugins to include. It can take them from your own ~/.claude and ~/.codex, or from a project.

In the sheet, each package has Set as default, Edit and Delete. You can also write the files yourself and check them:

connecto package check <id>

Which packages a project gets

Open a project's settings from the gear on its row:

• DEFAULT PACKAGE: whether this project uses the default package.
• ADDED PACKAGES: more packages for this project only.
• TOOLS: Claude, Codex or both. Only the chosen tools' files are installed.
• STATUS: what is installed, and a Refresh button.

How installing works

Connecto copies the package's files into the project's .claude, .codex and .agents folders when the project opens, when a package changes, and when you click Refresh. The default package goes in first, then the added ones.

• Files you edited are left alone. Connecto records what it installed in .connecto/packages.lock, so it can tell its own files from your changes. The status lists any file it skipped.
• Files a package dropped are removed.
• settings.json is merged, not replaced. A key you already set is never overwritten, and exactly what Connecto added is taken back if the package changes.
• Running terminals keep what they started with. Restart a terminal to pick up an update.

A package can hold up to 2000 files and 16 MiB. Symbolic links and settings.local.json are never installed.