specialize
Skill216 starsChanged 16 days agoApache-2.0View on GitHub
Author a new built-in Lagune specialization inside the Lagune source, not a project's own catalog. Use when adding or refining a security knowledge module that ships with Lagune, against the native layout (`catalog/*.md` plus the built-in index).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Lucas-Grilli/context-os-plugintheir own version, first seen Aug 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Lucas-Grilli/context-os-plugin★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectureSkill
- blind-reviewSkill
- calibrateSkill
- cdpSkill
- dashboardSkill
- engineeringSkill
- ingestSkill
- mcp-catalogSkill
- playgroundSkill
- refineSkill
- simulateSkill
- testingSkill
- uiSkill
- writerSkill
- lagune-charterSkill
- lagune-detectSkill
- lagune-hardenSkill
- lagune-planSkill
- lagune-proveSkill
- lagune-repairSkill
- laguneSkill
- lagune-specializeSkill
- lagune-verifySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read and follow skills/lagune-specialize/SKILL.md in full.
- Very specific: line 32
Every built-in belongs to at least one category, which is how a project brings it into its catalog with npx lagune write add --categories …
- Very specific: line 46
Write the authored module to catalog/<name>.md (Step 1).
- Very specific: line 47
Add the BuiltinSpecialization { name, tags, categories } to src/catalog/builtin.ts.
- Very specific: line 48
Add a Category to src/categories/categories.ts, but only when you introduced a new category.
- Very specific: line 49
Add its label, description, icon, and prompt task to src/dashboard/shared/specialization-meta.ts, which the dashboard and the website share.
- Very specific: line 54
Run the full suite: npm test.
- Very specific: line 58
Add a row to the table of built-ins in website/docs/catalog.mdx, giving the built-in its categories and focus.
- Distinctive: line 59
Update README.md only when it enumerates built-ins.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Authoring a built-in Lagune specialization (development workspace)
The published skill skills/lagune-specialize/SKILL.md writes into a project's own catalog: .lagune/catalog/<name>.md plus its entry in .lagune/configs.json. This repo is the Lagune source, where built-in specializations live in catalog/<name>.md and their index is a TypeScript array, not a runtime JSON file. A built-in is registered in code, published with the engine, and tested.
So you reuse the skill's authoring discipline (terrain, defense-only gate, template, tags, reconcile-never-append) but override every output path to the native layout, and you update the registration points the published skill never has to.
Step 1: Run the skill's authoring steps, with redirected paths
Read and follow skills/lagune-specialize/SKILL.md in full. Its authoring steps hold unchanged. The one thing that does not is where files are read and written, since the skill targets a project and you are in the source. Remap every path it names:
| Skill path (a project's own catalog) | Native path (use this instead) |
read catalog <name> for regex, javascript, browser | every *.md already in catalog/ (list the directory, mirror the closest one) |
template.md, next to the skill | skills/lagune-specialize/template.md |
read catalog (list what exists) | read catalog/ and BUILTIN_SPECIALIZATIONS in src/catalog/builtin.ts |
.lagune/catalog/<name>.md (the specialization file) | catalog/<name>.md |
.lagune/configs.json (index entry) | a BuiltinSpecialization in src/catalog/builtin.ts |
A hook reference inside the .md body is a call to the lagune_read tool, with command set to the hook and long flags only in arguments, because that body ships verbatim to the end user and the skill that loads it carries the npx fallback.
Step 2: Decide the category
Every built-in belongs to at least one category, which is how a project brings it into its catalog with npx lagune write add --categories <category>. Categories live in CATEGORIES in src/categories/categories.ts.
- A language specialization goes under its language key (
pythonunderpython, and so on). - A specialization about an application-security risk OWASP tracks goes under
owasp. - Match the specialization to the category that actually describes it. If none fits, that is a signal a new category may be needed, adding a
CategorytoCATEGORIES(key, label, description) and its icon. Ask the user before inventing one, do not force an unrelated module intoowaspto avoid the question.
A project's own index entry carries no categories, but the built-in index entry does. Set it.
Step 3: Write and register, then verify
A new built-in is not done when the .md exists. Touch each of these:
Required (a specialization is broken without these)
- Write the authored module to
catalog/<name>.md(Step 1). The engine readscatalog/<name>.mdby name, so the file resolves once it is on disk and indexed. - Add the
BuiltinSpecialization{ name, tags, categories }tosrc/catalog/builtin.ts. Without this row,read catalognever lists it andread catalog <name>cannot resolve it. - Add a
Categorytosrc/categories/categories.ts, but only when you introduced a new category. - Add its label, description, icon, and prompt task to
src/dashboard/shared/specialization-meta.ts, which the dashboard and the website share.
Tests (the suite asserts the index, the files, and the docs stay in sync)
- The catalog tests iterate
BUILTIN_SPECIALIZATIONS(for example, no built-in repeats its name inside its own tags, every index row has a file and every file a row, every engine call carries the package version and long flags), so a new entry is exercised automatically. Update a hardcoded list only when your change alters it, such as the built-ins a category holds. - Run the full suite:
npm test. It runsscripts/build.shfirst, so the engine the e2e tests exercise is rebuilt automatically. All green before you call it done.
Documentation (the built-in catalog is enumerated by hand in the website)
- Add a row to the table of built-ins in
website/docs/catalog.mdx, giving the built-in its categories and focus. The sync test fails until the row matches the index. - Update
README.mdonly when it enumerates built-ins.
Not touched
.lagune/configs.jsonand.lagune/catalog/: these hold a project's own catalog. A built-in never writes there.
Quick checklist
[ ] catalog/<name>.md authored from skills/lagune-specialize/template.md (reconciled on a refine), verify closing only on what the repository shows and detect recording the rest as a side quest
[ ] src/catalog/builtin.ts BuiltinSpecialization added { name, tags, categories }
[ ] src/categories/categories.ts only if a new category was introduced
[ ] src/dashboard/shared/specialization-meta.ts label, description, icon, prompt task
[ ] tests updated + npm test green
[ ] website/docs/catalog.mdx table row addedSummary to the user
As Step 8 of the skill: state the name, tags, categories, what it covers, and that the phases load it on demand once shipped (a prompt loads it directly with the engine's read catalog <name>). Note that a project's own specialization of the same name shadows it. Suggest a commit such as feat: add specialization in `<name>` defense, matching the wording the existing built-ins use, as a suggestion, not a mandate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

