Overview Start
Work
Personal Assistant Files Routine Research Big Projects Changes & Fixes Shutdown
Skills
Start 1. Identify the Task 2. Output Standard 3. Gather Knowledge 4. Write Instructions 5. Live Test 6. Package 7. Iterate Quick Reference
Skill Workflow · Step 06
06

Package it

Same skill format, two homes. One lives locally with files and shell. The other lives in Claude Teams as a Skill plus a Shared Project working together.

When to do this

Steps 1 to 5 are done. The skill produces the right output across three live tests. Now you decide where it ships.

The decision

How will the team use this skill? LOCAL, FILES + SHELL BROWSER, TEAM Claude Code Skill You, the power operator › One folder, one SKILL.md › Reference files alongside › Reads & writes files › Runs shell, calls APIs › Chains with other skills Lives in .claude/skills/ Claude Teams Combo Whole team, in the browser Skill the methodology uploaded once to Teams workspace triggers on description match + Project the workspace holds reference files + instructions shared with team per use case Lives in claude.ai/Teams

Path A · Claude Code Skill

One folder. The skill and everything it needs sit in the same place.

  • Where it lives: .claude/skills/<name>/SKILL.md with reference files in the same folder.
  • What it can do: read & write files in your workspace, run shell commands, hit any API, chain with other skills.
  • Who uses it: you (or a power operator) in the terminal or the Claude Code desktop app.
  • Why it exists: you need real work on real files. Not just text.

Path B · Claude Teams Combo (Skill + Shared Project)

Two pieces working together. The skill is the methodology, the Project is the workspace around it.

This is what you ship when the team uses Claude in the browser and you want everyone to produce the same quality of work.

Piece 1

The Skill

Same SKILL.md format as the Code skill. Uploaded once to the Teams workspace. Triggers automatically in any chat (including chats inside a Project) when the user's request matches its description.

Carries the methodology: the steps, the voice, the templates, the no-gos.

Piece 2

The Shared Project

A team-shared container with two things attached: Project Knowledge (the reference files the team needs for this use case) and Custom Instructions (what this Project is for, which skills to lean on).

Carries the context: the case studies, brand voice, pricing, examples.

How they work together at runtime

1. A team member opens the Shared Project in claude.ai. 2. They describe a task (e.g. "write a proposal for client X"). 3. The Project Knowledge is already in context. 4. The Skill triggers because the request matches its description. 5. The Skill walks the user through the steps, leaning on the Project files for the team-specific details. Same skill, same quality, every time.

Now do it — Path A · Claude Code Skill

Prompt
Continue with skill-creator. Step 6a: package as Claude Code Skill.

Move SKILL.md and the reference files into
~/.claude/skills/<name>/. Verify the folder structure
matches what a Claude Code skill expects.
Then trigger the skill in a fresh terminal session
to confirm it loads.

Now do it — Path B · Claude Teams Combo

Prompt
Continue with skill-creator. Step 6b: package as Teams Combo.

Walk me through these four moves on claude.ai/Teams:
1. Upload SKILL.md as a Skill in the Teams workspace.
2. Create a new Shared Project for this use case.
3. Add the reference files to Project Knowledge.
4. Add Custom Instructions that name the use case
   and point at the skill.

Then open the Project, type a real request, and check
that the skill triggers and uses the Project files.
Key Rule
Same skill format, different home.

The SKILL.md you wrote in Steps 1 to 5 works in both worlds. The Code path keeps it next to your filesystem. The Teams path pairs it with a Shared Project so the whole team gets the same workflow with the right files in context. Pick the home that matches how the team will actually use it.