/bluespec.skills
🧠The dispatcher for Blue Spec's sub-skills: focused, language-agnostic security knowledge modules that load only on demand, never by default.
A sub-skill is not invocable on its own. There is one door, and two ways through it.
Loaded for you, on demand​
When a phase like detect or verify hits a context a sub-skill covers, it runs /bluespec.skills itself and the dispatcher loads the right knowledge. This happens automatically, as part of the phase. You do not run it by hand for this to work.
/bluespec.skills regex
Typing /bluespec.skills regex on its own only loads the knowledge into the agent's context. On its own it does no work, because there is nothing for it to act on. To run a sub-skill against your code yourself, import the file and give it a task (see below).
Run one yourself​
To use a sub-skill directly, import its file with @ and write the task in the same prompt. The knowledge then acts on what you asked for.
@.bluespec/skills/regex.md
Create a collection of regular expressions in @src/utils/regex.py to validate emails and usernames.
This is the user-facing way, and it works in any prompt, even one unrelated to the Blue Spec flow. For the full walkthrough and output, see Available Skills.
Discover what is available​
Run the command with no selector to list the catalog.
/bluespec.skills
Sub-skills are not loaded by default. The relevant knowledge is pulled in for what the project actually is, instead of every check running by default.
The sub-skills live in .bluespec/skills/, so the file to import is @.bluespec/skills/<name>.md.