Skills: FAQ

The Basics

How many Skills can I have, and can I use more than one at once?
- As many as you need, and yes.

Will editing a Skill change assets I've already made?
- No, completed assets stay as they are.

Who can see my Skills, and what plans support them?
- Private by default unless you share them, and available on every plan, including Free trial.

Creating & Editing

Where do Skills I create live?
- Skills you create are personal to you by default and can be available across your boards in the current team. They are not available to other team members unless shared and installed for the team.

What are the main ways to create a Skill?
- See Best Practices: Ways to Create a Skill for the full list and example phrasing.

Can I edit Luma's built-in Skills?
- Built-in Skills are read-only. Ask the agent to copy the Skill into your Skills, then edit your copy.

Can I edit a Skill someone shared with me?
- The shared version is read-only unless you are its owner. Ask the agent to copy it into your Skills, give the copy a new name, and describe the changes you want.

How do I update a Skill I already shared?
- Edit your authored Skill, then update the existing published package. Updating in place keeps the same share link and creates a newer package version for installations to update to.

What kinds of edits can I make?
- Describe them in plain language: change the default model, resolution, or aspect ratio, rewrite the prompt, add preservation rules, or add and rename presets.

Sharing, publishing, and installing

How do I share a Skill?
- Open the Skills panel on a board, choose Share, select one or more Skills, add a package name and description, and complete the sharing flow. You can also ask the agent to share a Skill for you. When sharing is complete, copy the share link and send it to the recipient.

Where can I find Skills that were shared or installed?
- Open Skills from the left sidebar. The page shows Skill packages available to you and lets you search, sort, and filter by Installed for me, Installed for team, Installed on a board, or Created by me.

Is sharing the same as installing?
- No. Sharing publishes a package and creates a link. Installing determines where that package is available to the agent.

How do I install a shared Skill?
- Open the package from the Skills page. Choose Install for me to make it available to you across the current team's boards, or Install for team to make it available through the team scope. You can also install a package on a specific board and manage that installation from the board.

What is the difference between "Install for me" and "Install for team"?
- Install for me follows you across boards in the active team. Install for team makes the package available to team members across that team's boards. Team installation and removal depend on your team permissions.

Why is a Skill not available after I switch teams?
- Personal Skills and personal installations are scoped to the current team. Switch back to the original team, or share and install the package in the other team as appropriate.

Can I share several Skills together?
- Yes. The Share flow can publish several selected Skills as one package. If any selected Skill depends on another Skill, include the required dependencies when prompted.

Do I need a .zip to share or customize a Skill?
- No. Use a share link to distribute a published package, and ask the agent to copy a read-only Skill when you want an editable version. Download and upload are optional portability tools, not the normal sharing or editing workflow.

Are my instructions visible if I share a Skill?
- Yes, sharing a Skill shares its full instructions.

What happens when the publisher updates a package?
- The existing share link continues to work. Installations can show that an update is available; use Update or Sync to latest where offered.

Basic Troubleshooting