A Skill is a procedure saved in Luumen so LuumenAI can run it, built from the runbooks and SOPs your team already follows. Instead of explaining the same steps in every conversation, you save them as a Skill and run it by name.
Skills suit repetitive work with a set order, such as pre-patch checks, log rotation, service health verification, deployment checks, and incident triage.
What a Skill Contains
A Skill has a name, a description of what it does and when to use it, an ordered list of steps with the commands each step runs, and a scope that controls who can see it.
LuumenAI uses the description to decide when a Skill is relevant, so write it with the trigger conditions in it. A description that states when to run the Skill and what it confirms is more useful than a two-word label.
Scope
Every Skill has a scope, shown on its detail view and available as a filter in the library:
Personal: visible to you alone.
Workspace: visible to everyone who can see that workspace.
Organization: visible to everyone in your organization, across workspaces.
Create a Skill
Skills are created through a conversation. There are two ways to start:
Describe it. From Skills in the left hand navigation, click Add Skill, or type
/skill createin any conversation. Describe the procedure, or paste in the text of an existing runbook or set of commands. LuumenAI asks follow-up questions, then proposes a name, description, and steps. Review and save, or say what is wrong and it revises.Save from a session. After working through a problem with LuumenAI, ask it to turn the steps into a Skill. It builds the Skill from the commands that ran and their results, and asks about anything missing.
Run a Skill
From the library, open a Skill, choose the host, and run it. From a conversation, type /skill run and pick from the list, or ask for the Skill by name. LuumenAI may also suggest a Skill when your question matches its description.
A Skill runs one step at a time, and every command waits for your approval. On a host group, each step is approved once for the whole group. A Skill is not an automation that runs unattended.
Edit and Delete
Open a Skill to see its description, scope, owner, run count, and steps.
Edit starts a LuumenAI conversation for that Skill, and you describe the change the same way you described the Skill when creating it. /skill manage from any conversation opens the library.
Deleting a Skill requires an Admin or Owner. Members can create and edit Skills, but cannot delete them.
When to Use Skills vs Snippets
A snippet is a single command you copy into a terminal. A Skill is a multi-step procedure LuumenAI carries out with your approval. If you run the same snippets together in the same order, save them as a Skill.