Agent skill · Security

specialize

Author a new built-in Lagune sub-skill inside the Lagune source, not a scaffolded `.lagune/` target. Use when adding or refining a security knowledge module that ships with Lagune, against the native layout (`spec/skills/*.md` plus the catalog).

wellwelwelgithub.com/wellwelwelGitHub ↗
claude-codecodexcopilotcursorMIT
Install
npx skills add wellwelwel/lagune --skill specialize --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: .claude/skills/specialize/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 89
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Authoring a built-in Lagune sub-skill (development workspace) The end-user command `@spec/commands/lagune.specialize.md` writes into a **scaffolded target project**: `.lagune/skills/<name>.md` and `.lagune/skills.json`. Neither path exists here. This repo is the **Lagune source**, where built-in sub-skills live in `spec/skills/<name>.md` and the catalog is a hardcoded TypeScript array, not a runtime JSON file. There is also no "user" registry: a built-in is registered in code, compiled, scaffolded, and tested. So you reuse the command'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 end-user command never has to. ## Step 1: Run the command's authoring steps, with redirected paths Read and follow `@spec/commands/lagune.specialize.md` in full. Its authoring steps hold unchanged. The one thing that does not is where files are read and written, since the command targets a scaffolded project and you are in the source. Remap every path it names: | Command path (end-user target) | Native path (use this instead) | | ---------------------------

What's inside
Steps it walks through
  1. Step 1: Run the command's authoring steps, with redirected paths
  2. Step 2: Decide the category (group)
  3. Step 3: Write and register, then verify
  4. Required (a sub-skill is broken without these)
  5. Tests (the suite asserts the catalog and the docs stay in sync)
  6. Documentation (the built-in catalog is enumerated by hand in the website)
  7. Not touched
  8. Quick checklist
  9. Summary to the user
More from lagune
All skills →
About this skill
What does the specialize skill do?

Author a new built-in Lagune sub-skill inside the Lagune source, not a scaffolded `.lagune/` target. Use when adding or refining a security knowledge module that ships with Lagune, against the native layout (`spec/skills/*.md` plus the catalog).

How do I install it?

Run `npx skills add wellwelwel/lagune --skill specialize --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From wellwelwel/lagune, a repository with 89 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going