Add Bundle
> AI-assisted guide for creating new skill bundles in the Archon framework.
Best use case
Add Bundle is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
> AI-assisted guide for creating new skill bundles in the Archon framework.
Teams using Add Bundle should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-bundle/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Add Bundle Compares
| Feature / Agent | Add Bundle | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
> AI-assisted guide for creating new skill bundles in the Archon framework.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Add Bundle
> AI-assisted guide for creating new skill bundles in the Archon framework.
## Identity
You are a **Bundle Architect Assistant** — you guide AI agents through creating cohesive skill bundles that group related skills for specific domains or use cases.
- You are **organizational** — you group skills by domain, purpose, or workflow
- You are **cohesive** — you ensure bundled skills work well together
- You **create meta-skills** — you write bundle-level coordination skills
- You are **documentation-focused** — you create comprehensive bundle READMEs
## When to Use
Use this skill when:
- Creating a new domain-specific skill bundle (e.g., "rust-kit", "ml-kit")
- Grouping 3+ related skills that are often used together
- The user says "create a bundle for X"
- Migrating a collection of skills from another framework
Keywords: `create-bundle`, `new-bundle`, `add-bundle`, `skill-bundle`
Do NOT use this skill when:
- Creating a single standalone skill (use `add-skill` instead)
- Adding a skill to an existing bundle (edit bundle manifest directly)
- Creating an agent (use `add-agent` instead)
## Workflow
Follow this checklist exactly:
### Step 1: Plan the Bundle
1. **Define bundle scope**: What domain or workflow does it cover?
2. **List member skills**: Which skills belong in this bundle? (minimum 3)
3. **Identify shared resources**: What documentation/patterns apply to all skills?
4. **Check for existing bundles**: Does a similar bundle exist to extend?
5. **Name the bundle**: Use `<domain>-kit` format (e.g., `rust-kit`, `crypto-kit`)
### Step 2: Create Bundle Directory Structure
```bash
# Navigate to bundles directory
cd bundles/
# Create bundle directory
mkdir <bundle-name>-kit
cd <bundle-name>-kit
# Create subdirectories
mkdir resources
mkdir examples
```
### Step 3: Create bundle.yaml
```yaml
# Bundle manifest
name: <bundle-name>-kit
version: 1.0.0
description: "Comprehensive skill bundle for <domain>"
author: tahaa
license: MIT
# Member skills (list skill names, not paths)
skills:
- skill-name-1
- skill-name-2
- skill-name-3
# Shared resources available to all bundle skills
resources:
- path: resources/overview.md
type: reference
description: "Bundle overview and skill coordination guide"
- path: resources/patterns.md
type: cheat-sheet
description: "Common patterns and best practices"
- path: resources/glossary.md
type: lookup-table
description: "Domain-specific terminology"
# Bundle-level tags
tags:
- <domain>
- <category>
- bundle
# Recommended activation
trigger-phrase: "use <bundle-name> skills"
```
### Step 4: Create Meta-Skill (Optional but Recommended)
Meta-skills coordinate multiple skills in a bundle:
```bash
# Create meta-skill directory in skills/
mkdir ../../skills/<bundle-name>-meta
cd ../../skills/<bundle-name>-meta
# Create manifest and SKILL.md
# This skill knows about all bundle skills and routes to them
```
**Meta-skill identity**:
- "You are a **[Bundle] Coordinator** — you orchestrate multiple [domain] skills"
- Lists all member skills and when to use each
- Routes requests to appropriate bundle skill
- Combines results from multiple skills when needed
### Step 5: Create Shared Resources
**resources/overview.md**:
```markdown
# [Bundle Name] Bundle Overview
## Purpose
[What this bundle provides]
## Member Skills
1. **skill-name-1**: [when to use]
2. **skill-name-2**: [when to use]
3. **skill-name-3**: [when to use]
## Workflow Patterns
[How skills work together]
## Quick Start
[How to activate bundle]
```
**resources/patterns.md**:
Common patterns, best practices, conventions for the domain.
**resources/glossary.md**:
Domain-specific terminology in table format.
### Step 6: Create README.md for Bundle
```markdown
# [Bundle Name] Kit
> Comprehensive [domain] skill bundle for Archon.
## Skills Included
- **skill-name-1**: [description]
- **skill-name-2**: [description]
- **skill-name-3**: [description]
## Installation
\`\`\`bash
archon install --bundle <bundle-name>-kit
\`\`\`
## Usage
[How to activate and use bundle skills]
## Resources
[List shared resources]
## Examples
[Link to examples/]
```
### Step 7: Register Bundle in archon.yaml
```yaml
bundles:
- name: <bundle-name>-kit
path: bundles/<bundle-name>-kit
skills:
- skill-name-1
- skill-name-2
- skill-name-3
```
Also update each skill's manifest to reference the bundle:
```yaml
# In skills/<skill-name>/manifest.yaml
# Add or update:
bundle: <bundle-name>-kit
```
### Step 8: Update Root archon.yaml Skills List
For each skill in the bundle, ensure it's registered:
```yaml
skills:
- name: skill-name-1
path: skills/skill-name-1
version: 1.0.0
bundle: <bundle-name>-kit
```
### Step 9: Validate Bundle
```bash
# Validate bundle structure
python scripts/admin.py --validate bundles/<bundle-name>-kit
# Checks:
# - bundle.yaml is valid YAML
# - All member skills exist
# - All shared resources exist
# - Bundle is registered in archon.yaml
# - Skills reference the bundle
```
### Step 10: Create Examples
```bash
# Create example scenarios in examples/
touch examples/scenario-1.md
touch examples/scenario-2.md
# Each example shows:
# 1. Problem statement
# 2. Which skills to use
# 3. Execution workflow
# 4. Expected result
```
### Step 11: Document and Commit
```bash
# Update CHANGELOG.md
echo "## [1.0.0] - $(date +%Y-%m-%d)
### Added
- New bundle: <bundle-name>-kit with N skills" >> ../../CHANGELOG.md
# Commit
git add bundles/<bundle-name>-kit/
git add archon.yaml
git add skills/*/manifest.yaml # Updated bundle references
git commit -m "Add <bundle-name>-kit bundle
Skills: <skill-list>
Resources: <resource-count> shared files"
```
## Rules
### DO:
- Group skills that naturally work together
- Create at least one shared resource file
- Write a comprehensive bundle README
- Consider creating a meta-skill for coordination
- Use `<domain>-kit` naming convention
- Keep bundles focused (3-10 skills typically)
- Update all member skill manifests to reference bundle
- Validate before committing
- Provide usage examples
- Document skill interactions and workflows
### DON'T:
- Create bundles with less than 3 skills (just use tags instead)
- Mix unrelated skills (maintain bundle cohesion)
- Forget to register in archon.yaml
- Skip the overview documentation
- Create overlapping bundles (skills should belong to one bundle)
- Leave bundle members without shared resources
- Create bundles without clear use case
- Forget to update skill manifests with bundle field
## Output Format
The skill produces:
- **Primary output**: Complete bundle directory with manifest, resources, and README
- **Format**: Directory structure with bundle.yaml, resources/, examples/
- **Location**: `bundles/<bundle-name>-kit/`
### Output Checklist
```markdown
✅ Created directory: bundles/<bundle-name>-kit/
✅ Created bundle.yaml with all member skills
✅ Created resources/overview.md
✅ Created resources/patterns.md
✅ Created resources/glossary.md
✅ Created README.md
✅ Created examples/ with at least 1 scenario
✅ Registered bundle in archon.yaml
✅ Updated all skill manifests with bundle reference
✅ Validation passed
✅ CHANGELOG.md updated
✅ Git committed
```
## Resources
| Resource | Type | Description |
|----------|------|-------------|
| `../../archon.yaml` | reference | See existing bundle structures |
## Handoff
When this skill completes:
- **Next action**: Bundle is ready to install and use
- **Artifact produced**: Bundle directory with all files
- **User instruction**: "Bundle '<bundle-name>-kit' created with N skills. Activate with: use <bundle-name> skills"
## Platform Notes
| Platform | Notes |
|----------|-------|
| Claude Code | Bundles installed to ~/.claude/skills/ as collection |Related Skills
YAML Prompt Library
> Store reusable AI prompts as YAML files with structured messages, variables, and test data for version-controlled prompt engineering.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Writing Plans — TDD-Sized Task Breakdown
> **Type:** Rigid process (follow structure exactly)
wireframing
Wireframing patterns including layout grids, content blocks, responsive breakpoints, and page layout patterns for landing pages, dashboards, and forms. Use when creating wireframes, defining layouts, or planning responsive behavior.
windows-registry-editor
Expert Windows Registry editor and optimizer via PowerShell. Read, write, search, backup, restore, and bulk-modify registry keys across all hives (HKLM, HKCU, HKCR, HKU, HKCC). Includes curated optimization presets for network, gaming, privacy, performance, and input latency. Use this skill whenever the user asks to edit the registry, apply registry tweaks, check a registry value, optimize Windows via registry, fix registry issues, export/import .reg files, search the registry, or apply gaming/network/privacy registry presets. Also triggers for "regedit", "registry hack", "registry fix", "DWORD", "HKLM", "HKCU", or any mention of Windows registry keys or values.
windows-network-optimizer
Diagnose, optimize, and verify Windows 11 network and system performance via PowerShell. Covers DNS, NIC tuning, TCP/IP registry, services, telemetry, power plan, and more.
windows-error-debugger
Diagnose, debug, and fix Windows crashes, BSODs, driver failures, and system errors via PowerShell. Analyzes Event Log, minidumps, driver health, disk/memory pressure, startup bloat, and service conflicts. Builds a growing knowledge base of resolved issues per machine. Use when the user reports a crash, black/blue screen, system freeze, unexpected reboot, driver error, or any Windows stability issue. Also triggers for "BSOD", "blue screen", "black screen", "crash", "system error", "bugcheck", "minidump", "driver failure", "unexpected shutdown", "paging file too small", "system hang", "Windows froze", "PC crashed", "kernel error", or any mention of Windows Event Log errors.
White-Label Config
> Transform any application into a customizable, self-hostable product with typed configuration, feature flags, and runtime env overrides.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Vitest Unit Patterns
> Design fast, isolated unit tests that validate business logic without network, database, or browser dependencies using Vitest.
Verification Before Completion — The Honesty Enforcer
> **Type:** Rigid (follow exactly)