Building a bundle

What is a bundle?

A bundle groups several skills into one team. A manager (entry) skill takes the user's request and hands the work, in order, to role skills such as research, content, and reporting. People install the whole team with one install line.

marketing-team (bundle)
├── marketing-manager   manager: splits the request and hands it off
├── marketing-research  role: research
├── marketing-content   role: content writing
└── marketing-report    role: summary report

• A bundle can only include public skills, between 2 and 20 of them.
• Each skill's version is pinned. If the author publishes a new version, bundles that already include the skill don't change.
• You can include public skills uploaded by other people.

Naming rules

Give every skill in the team the same prefix.

• The prefix is the bundle address without its last word (marketing-team → marketing, sales-ops-team → sales-ops).
• Adding a skill that doesn't start with the prefix shows a warning. You can still publish, but names are more likely to collide in Aside's skill folder or be confused with another team's skills.
• Addresses use lowercase letters, numbers, and hyphens (-) only. Keep the name in SKILL.md the same as the address.

Writing the manager skill

The manager skill doesn't do all the work itself. It splits the request, hands off each part, and collects the results.

---
name: marketing-manager
description: Marketing team manager. Use when the user asks for research, content, and a report in one go, such as "Create marketing material for our new product." Does not do everything itself; hands work to the role skills in order.
---

# Marketing team manager

## Team
- marketing-research: market and competitor research
- marketing-content: blog and social copy
- marketing-report: one-page summary of the results

## Steps
1. Confirm the product, target customer, and deadline. Ask instead of guessing if anything is missing.
2. Hand research to the marketing-research skill.
3. Pass the research to the marketing-content skill to write the copy.
4. Use the marketing-report skill to summarize everything.
5. Show the user a short result after each step and confirm before moving on.

## Do not
- Do the role skills' work yourself.
- If a role skill isn't installed, tell the user to reinstall this bundle.

Tips

1. In the description, say it's for requests that need the whole team. That way the manager is called first instead of a single role skill.
2. In the body, list the team (role skill names and what each does) and the order of hand-offs with numbers.
3. Adding user check-ins between steps keeps the work from drifting off course.
4. Write role skill names exactly as they appear in the bundle.

Writing role skill descriptions

Narrow each role skill so it's used only when the manager hands work to it. Without that limit, Aside may call the skill on its own for similar requests.

• Include a phrase such as "Use only when the manager hands off …" or "only if …". When you check a bundle, any non-manager skill without such a phrase gets a warning.
• Describe what it receives and what it returns (input and output format) so the manager can pass results to the next role easily.
• Install the bundle in Aside and confirm how the manager actually calls the role skills before describing it.

Publishing steps

1. Publish the manager and each role skill as public skills from submit a skill. If a skill has supporting files, upload it as a folder (zip) (see Understanding SKILL.md).
2. On create a bundle, enter a title, address, one-line summary, and bundle version.
3. Enter each skill's address to load its versions. Add a role name (e.g. Research), choose the version to pin, then pick one manager skill.
4. Click Check.
   • Errors (can't publish): missing skills, private or hidden skills, missing versions
   • Warnings (can publish): names without the prefix, role skill descriptions without a scope phrase
5. Review the diagram preview and publish.

New versions and things to know

• To use a skill's new version in your bundle, open Publish new version on the bundle page, change the pinned version, raise the bundle version, and save. Earlier bundle versions keep their setup.
• If any included skill has a scripts/ folder, the bundle gets an Includes scripts badge and people are asked to confirm before copying the install line.
• If an author makes an included skill private or a moderator hides it, the bundle page notes that the skill won't be installed.
• You can create up to 5 bundles per day.

Checklist before publishing

• The bundle address and skill names share the same prefix
• The manager description says it's for requests that need the whole team
• The manager body lists the team and the hand-off order with numbers
• Each role skill description says to use it only when the manager hands off work
• You installed it in Aside and confirmed the manager hands work to the role skills