Manage SkillsCopy Anchor Link

A Skill provides instructions and resources for an Agent. The desktop app manages Skills in your library, Skills enabled in Work, and copies deployed to local Agents separately. Adding a Skill to your library does not enable it or write it to an Agent's configuration directory.

Get a Skill from the communityCopy Anchor Link

1. In the Lumoswitch desktop app, open Skills from the sidebar and select Get More to open the community catalog.
2. Open a Skill and review its description, source, compatibility, and dependencies.
3. Select Install. The Skill then appears as installed in your library. This step adds it to your local library only.
4. Expand Details and usage to review its declared capabilities, source, and Agent usage. When you trust it, turn on Available in Work. If a permission review appears, check it before selecting Enable Skill; some Skills enable directly without this dialog.

Import from GitHub or a local folderCopy Anchor Link

Import from GitHub: In the Skills library, select From GitHub and enter a public github.com repository. Optionally enter a Skill subdirectory and a branch, tag, or commit, then select Import Skill. Only public repositories are supported. The imported copy stays local and starts disabled. Review the repository, commit, and SKILL.md before enabling it. To update, check for changes, review the commit shown in the confirmation dialog, and confirm the download. An updated Skill is disabled again until you review and enable it.

Import a local Skill: Select Import folder and choose a folder containing a standard SKILL.md. After import, find it with the Local filter in the library. If the Skill has no Lumoswitch permission manifest, the app cannot verify its capabilities from metadata; read SKILL.md and the source files before enabling it.

Deploy to a local AgentCopy Anchor Link

Deployment is a separate action. On an installed Skill, select Install to Agent and choose a detected local Agent. Review the installation dialog's permission and destination details, any compatibility or dependency notices, and the consent text. Check the consent box and select Install to confirm. After success, start a new Agent session to use the Skill. Check the Agent usage or local locations shown in the Skill details; if the Skill still does not appear, follow the app's recheck guidance and restart the Agent if needed.

Available in Work makes the Skill available to Lumoswitch Work. Install to Agent places a copy in the selected local Agent's Skills location. Enabling and deployment are separate actions, but disabling or updating the library Skill also affects existing managed Agent assignments; its impact is not limited to Work.

Disable, update, and restore assignmentsCopy Anchor Link

Before disabling or updating a Skill, review the affected Agents in the confirmation dialog. Disabling clears existing managed Agent assignments. Updating also clears those assignments and leaves the new version disabled. Re-enabling does not restore the previous assignments automatically. Removing the library Skill clears those assignments too. Affected Agents may show that they need syncing.

To use the Skill again:

1. Review the current version's content and permissions, then enable it in the Skills library.
2. Open each affected Agent's configuration, select the required Skill again, preview and apply the change. Complete any sync requested by the app, then confirm the Agent has loaded the Skill.
3. Native copies deployed separately through Install to Agent are managed separately. A library update does not upgrade them automatically, and switching the library Skill off does not guarantee those copies stop working. Check their versions and status in native deployment management; update, redeploy or remove them as needed, then verify the result in the target Agent.

These actions do not install an Agent's runtime dependencies. Resolve missing dependencies or name conflicts shown by the app without clearing the whole library.

Permissions and troubleshootingCopy Anchor Link

• Review permissions when prompted. A permission dialog appears when a Skill needs review. It lists requested capabilities and scopes, such as reading or changing workspace files, running commands, network access, reading configured secrets, or accessing files outside the workspace. Cancel and inspect the source if its origin or requested access is unclear, or if its declared permissions changed.
• Enabling is not blanket approval. Enabling a Skill does not automatically approve file changes, commands, access outside the workspace, or network access. Work continues to follow your approval settings.
• Install is unavailable or deployment is blocked: Expand the details to read compatibility and dependency notices. Follow them to provide a missing dependency, select a supported Agent, or resolve a name conflict. The app does not install every third-party runtime or command for you.
• An imported Skill is missing: Check the library filter (All or Local), clear the search, and make sure the source folder contains SKILL.md.
• The local Agent does not load it: Check the deployment location and status in the Skill details. Agent login, runtime dependencies, and local permissions must also be in place. A successful deployment confirms the files were placed; it does not confirm that the Agent loaded or ran the Skill.

Related guidesCopy Anchor Link

• Desktop overview
• Agents
• Workspace
• MCP
• Troubleshooting