Why does an installed Skill not work in my agent?
Check that a Skill is enabled, its permissions are confirmed, it supports and is bound to the target agent, and the current workspace has selected it.
Maintained by the 路墨 Lumoswitch product team
Installation only places a Skill on the device. Check its enabled state, permissions, and compatibility, then select it for the agent or current workspace.
Why does “installed” not mean “ready to use”?
1. Open Skills in the desktop app and check for “Enabled,” not just installed. Some installs must have their permissions reviewed and confirmed before enabling. 2. Check supported agents, dependencies, and permission notices; a missing dependency, unconfirmed permission, or unsupported agent keeps it from being available to the workspace. 3. If an update left it disabled, read the change and permission summary and confirm before enabling it. Do not ignore permission details just to make it work.
How do I make the current task use this Skill?
1. In Skills management, confirm that it is enabled and bound to the agent you are using. 2. In the current workspace conversation's Skills picker, choose Select Skills, check the target item, and apply it. This changes only the current conversation. You can leave Auto on, but automatic selection does not guarantee that every Skill will be used. 3. Try a small task that matches the Skill's description. For example: “Use this Skill's checklist to review `README.md` and report only the paragraphs that need correction.”
How can I tell whether the Skill had an effect?
1. Confirm that the picker kept the target Skill and shows no unavailable, missing-dependency, or incompatible notice. 2. Match the task to the Skill's purpose and compare the result with its instructions. 3. Read the Skill's `SKILL.md` and source, and check that its requested tool permissions fit the task. A Skill provides instructions and tool guidance; it cannot guarantee that a model will follow every instruction every time.
What if the option disappears or the result does not change?
1. Refresh Skills management and recheck installation, enabled state, and agent binding; after a community install, complete any permission confirmation shown by the app. 2. If the workspace marks the selected Skill unavailable, check whether the target agent is supported and dependencies are ready; then reopen the picker and apply it again. 3. Make sure the task matches the Skill's scope; a mismatched request does not show that installation failed. 4. If a permission change or update disabled it, review the changes before deciding whether to enable it again.