English | Русский

Skill Bundles

Skill bundles are a logical grouping of vendor skills from tausik-skills (the official Kibertum/tausik-skills repo, mirrored under skills-official/ in dev). One CLI call installs every skill in a bundle — useful for matching a project's domain (integrations, data extraction, deep quality) without remembering individual skill names.

Status (v1.4.0): bundles are configured locally — every consumer project that re-runs bootstrap gets skills-official/bundles.json and the tausik skill bundle CLI. The marketplace push to github.com/Kibertum/tausik-skills itself is deferred until after v1.4 ships (the polish moratorium forbids public pushes). The local CLI works against the in-tree skills-official/ mirror.

The 6 bundles

Bundle	Skills	When to install
integrations	jira, bitrix24, confluence, sentry	External-service projects: ticket workflows, CRM, docs publishing, error monitoring. Each skill needs environment credentials.
data-formats	excel, pdf, markitdown	Document-processing projects: read/extract/convert binary formats.
quality-pro	audit, security, optimize, zero-defect, ultra	Anything where "looks fine" is not an acceptable bar — security-sensitive code, perf bottlenecks, precision-mode work.
automation	run, loop-task, dispatch	Batch / loop / multi-worker workflows — autonomous execution beyond single-task work.
workflow-helpers	daily, retro, presale, skill-test, docs	Productivity, retrospectives, presale estimation, doc generation, meta tooling.
ru-locale	(empty placeholder)	Reserved for Russian-language-specific skills. Will be populated as RU-specific skills are authored.

CLI

.tausik/tausik skill bundle list                    # all bundles + skill counts
.tausik/tausik skill bundle list --json             # machine-readable

.tausik/tausik skill bundle show integrations       # human-readable bundle body
.tausik/tausik skill bundle show integrations --json

.tausik/tausik skill bundle install integrations    # installs all 4 skills
.tausik/tausik skill bundle uninstall integrations  # removes all 4

bundle install reuses the existing tausik skill install <name> pipeline per skill — same vendor cache, same pip dependency resolution, same activation step. Bundle install:

• Routes each skill through the standard install code path (so per-skill safeguards still apply).
• Continues on per-skill error — one missing dep doesn't abort the rest. Errors land as [ERR] rows in the report.
• Skips deprecated skill names with a clear migration message (see "Deprecated skills" below).
• For the ru-locale placeholder, returns a single placeholder row and exits without installing anything.

Deprecated skills

Five skills are removed from skills-official/ and registry.json in v1.4 — they were duplicating built-in functionality.

Removed	Replacement
go	Use /plan + /task (built-in skills with QG-0 enforcement).
next	Use the CLI tausik task next (no skill install required).
diff	Use git diff and /review (already analyzes diffs).
onboard	Built-in /start covers session onboarding; first-time setup uses python bootstrap/bootstrap.py --init.
init	First-time project setup is python bootstrap/bootstrap.py --init.

If you try to install a deprecated skill via tausik skill bundle install <bundle> (which can happen if a stale third-party manifest still references it), the CLI prints [SKIP] <name>: deprecated: <migration message> and continues with the rest of the bundle.

For migration steps if you currently have these skills installed locally, see Skill Bundles Migration.

Authoring a custom bundles file

If you maintain your own skill repo, ship a bundles.json next to tausik-skills.json. Schema:

{
  "version": 1,
  "bundles": {
    "<bundle-name>": {
      "title": "Human-readable title",
      "description": "One-paragraph description.",
      "skills": ["skill-a", "skill-b"],
      "placeholder": false
    }
  },
  "deprecated": {
    "old-skill-name": "Migration message shown when bundle install hits this name."
  }
}

• bundles.<name>.skills is a list of skill names that must exist as <repo>/<skill-name>/SKILL.md.
• bundles.<name>.placeholder = true makes bundle install/uninstall a no-op (useful for reserving a future bundle slot).
• deprecated entries are advisory — they only affect the printed message during bundle install; CLI never deletes anything based on this.

What's next

• Vendor skills — repo trust, manifest format, three-tier system
• Skill ecosystem — how bundles fit alongside core skills + Claude-native sub-agents
• Skill Bundles Migration — for users with the deprecated 5 skills installed