Agent skill

Specialize

Author a new built-in Lagune sub-skill inside the Lagune source, not a scaffolded .lagune/ target.

MITAuto-check passedDevelopment

Install Specialize

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/specialize .claude/skills/specialize && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .claude/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/specialize .agents/skills/specialize && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .agents/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/specialize .cursor/skills/specialize && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .cursor/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/wellwelwel/lagune.git --path .claude/skills/specialize

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/specialize .gemini/skills/specialize && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .gemini/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/specialize .github/skills/specialize && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .github/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wellwelwel/lagune --skill specialize -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wellwelwel/lagune specialize --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wellwelwel/lagune.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/specialize .opencode/skills/specialize && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "specialize" agent skill from https://github.com/wellwelwel/lagune/tree/main/.claude/skills/specialize into .opencode/skills/specialize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specialize", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: specialize
GitHub stars: 173
Token cost: ~1.7k tokens
SKILL.md length: 752 words
Files: 1
Skills in repo: 8
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Author a new built-in Lagune sub-skill inside the Lagune source, not a scaffolded .lagune/ target.

Works in 3 steps: Run the command's authoring steps, with… → Decide the category (group) → Write and register, then verify
Refining a security knowledge module that ships with Lagune
SKILL.md covers Step 1: Run the command's…, Step 2: Decide the category…, Step 3: Write and register,… and Quick checklist, plus 1 more section
Calls npx and npm

What it does

Specialize is an agent skill from wellwelwel/lagune. 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).

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Project scaffolding. The repository describes itself as: 🌊 Lagune is your security copilot as you build, your Blue Team when you audit, whether you're a developer or not (no API key needed). The licence is MIT.

When your agent uses it

Refining a security knowledge module that ships with Lagune
Against the native layout (spec/skills/.md plus the catalog)

Example prompts

“/specialize”

Requirements

Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Run the command's authoring steps, with redirected paths
Decide the category (group)
Write and register, then verify

What it can do on your machine

Read from SKILL.md and the folder at commit c97ddfc. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Specialize loads about 1.7k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 752 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wellwelwel/lagune at commit c97ddfc, republished under its MIT licence (© wellwelwel). 752 words, ~1,719 tokens.

Download SKILL.mdSave it as .claude/skills/specialize/SKILL.md (or your agent's skills folder).

name: specialize
description: 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).
user-invocable: true
metadata.internal: true

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)
`.lagune/skills/{regex,javascript,browser}.md` (worked examples)	every `*.md` already in `spec/skills/` (list the directory, mirror the closest one)
`.lagune/templates/specialize-template.md`	`spec/templates/specialize-template.md`
`@.lagune/specializations.md` (list what exists)	read `spec/skills/` and `SKILLS_CATALOG` in `src/hooks/skills/catalog.ts`
`.lagune/skills/<name>.md` (the sub-skill file)	`spec/skills/<name>.md`
`.lagune/skills.json` (catalog entry)	a `BuiltinSkillEntry` in `src/hooks/skills/catalog.ts`

One path it names stays put: a hook reference inside the .md body keeps the ./.lagune/hooks/<x>.mjs form, because that body ships verbatim to the end user and must point at their scaffolded path, not the source.

Step 2: Decide the category (group)

Every built-in belongs to a category (group), which is how npx lagune add --skills <category> bundles it into a target project. Categories live in SKILL_GROUPS in src/hooks/skills/groups.ts.

A language sub-skill goes under its language key (python under python, and so on).
A sub-skill about an application-security risk OWASP tracks goes under owasp.
Match the sub-skill to the category that actually describes it. If none fits, that is a signal a new category may be needed, adding a SkillGroup to SKILL_GROUPS (key, label, description). Ask the user before inventing one, do not force an unrelated module into owasp to avoid the question.

The end-user skills.json has no groups field by default, but the built-in catalog 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 sub-skill is broken without these)

Write the authored module to spec/skills/<name>.md (Step 1). src/core/assets.ts reads spec/skills/ by directory listing, so the file loads automatically once it is on disk, with no code change.
Add the BuiltinSkillEntry { name, tags, groups } to src/hooks/skills/catalog.ts. Without this row the file scaffolds, but .lagune/specializations.md never lists it and add --skills cannot bundle it.
Add a SkillGroup to src/hooks/skills/groups.ts, but only when you introduced a new category.

Show full SKILL.md (296 more words)Show less

Tests (the suite asserts the catalog and the docs stay in sync)

test/integration/skills/skills.test.ts iterates SKILLS_CATALOG (e.g. "never repeats the name inside its own tags"), so a new entry is exercised automatically. Check that no count-based or hardcoded-list assertion now fails.
test/e2e/init/skills-hook.test.ts and test/e2e/init/manage-cli.test.ts assert scaffold and listing behavior, sometimes by sub-skill name. Update any hardcoded expectation that should now include the new one.
test/integration/cli/manifest.test.ts and test/integration/cli/scaffold-groups.test.ts reference specific skill paths like .lagune/skills/regex.md. Update them only when your change alters what a given category scaffolds.
Run the full suite: npm test. Its pretest hook runs scripts/build.sh first, so the compiled lib/hooks/*.mjs the e2e tests exercise are rebuilt automatically, no separate build step needed. All green before you call it done.

Documentation (the built-in catalog is enumerated by hand in the website)

Add a row to the "set that ships with Lagune" table in website/docs/commands/skills.mdx (around line 48), giving the built-in its category and focus. This table is maintained by hand and drifts silently when a built-in is missing.
The example listing output in website/docs/hooks/skills.mdx (# => regex: ...) is illustrative. Update it only when it should showcase the new one.
Update README.md only when it enumerates built-ins.

Not touched

src/core/skills-catalog.ts (the empty user catalog factory), src/hooks/skills/discover.ts (reads the user's .lagune/skills.json), and .lagune/skills.json itself: these are the end-user registry. A built-in never writes there.

Quick checklist

[ ] spec/skills/<name>.md            authored from spec/templates/specialize-template.md (reconciled on a refine)
[ ] src/hooks/skills/catalog.ts      BuiltinSkillEntry added { name, tags, groups }
[ ] src/hooks/skills/groups.ts       only if a new category was introduced
[ ] tests updated + npm test green
[ ] website/docs/commands/skills.mdx table row added

Summary to the user

As Step 8 of the command: state the name, tags, category, what it covers, and that the phases now load it on demand once shipped (end users import it with @.lagune/skills/<name>.md). Note it shadows any same-named entry on a refine. 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.

Files

Just SKILL.md in .claude/skills/specialize of wellwelwel/lagune.

Open the folder on GitHubat commit c97ddfc

Compare with similar skills

Specialize next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Specialize compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Specialize this skillwellwelwel/lagune	173	—	~1.7k	Automated safety check: Pass	MIT	yesterday
Nx Generatenomcopter/react-mosaic	4.8k	7 repos	~1.9k	Automated safety check: Pass	Custom licence	10 days ago
PonytailDavidObando/gsharp	564	8 repos	~1.7k	Automated safety check: Pass	MIT	today
Run Nx Generatornrwl/nx	29k	2 repos	~592	Automated safety check: Notes	MIT	today
Conductor Setupgemini-cli-extensions/conductor	3.8k	—	~4.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Mirage VFS Adapter Authoringstrukto-ai/mirage	3.7k	—	~2.5k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Nx Generate
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
4.8k GitHub starsUsed in 7 repos~1.9k tokens
DevelopmentAuto-check passed
Ponytail
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
564 GitHub starsUsed in 8 repos~1.7k tokens
DevelopmentAuto-check passed
Run Nx Generator
nrwl/nx
Run Nx generators with prioritization for workspace-plugin generators.
29k GitHub starsUsed in 2 repos~592 tokens
DevelopmentAuto-check: notes
Conductor Setup
gemini-cli-extensions/conductor
Scaffolds the project and sets up the Conductor environment.
3.8k GitHub stars~4.2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Mirage VFS Adapter Authoring
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
3.7k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Siteboon Backend Module Standards
siteboon/claudecodeui
Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.
14k GitHub stars~1.2k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Specialize

What does Specialize do?

Author a new built-in Lagune sub-skill inside the Lagune source, not a scaffolded .lagune/ target. Specialize is an agent skill from wellwelwel/lagune.lagune/ target.

When should I use Specialize?

Specialize fits situations like: refining a security knowledge module that ships with Lagune; against the native layout (spec/skills/.md plus the catalog).

How do I install Specialize in Claude Code?

Run `npx skills add wellwelwel/lagune --skill specialize -a claude-code`. Or copy the skill folder (.claude/skills/specialize in wellwelwel/lagune) into .claude/skills/specialize in your project. Claude Code loads it when a task matches its description.

How do I install Specialize in Codex?

Run `npx skills add wellwelwel/lagune --skill specialize -a codex`. Or copy the skill folder (.claude/skills/specialize in wellwelwel/lagune) into .agents/skills/specialize in your project. Codex loads it when a task matches its description.

Can I use Specialize in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wellwelwel/lagune --skill specialize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specialize, .gemini/skills/specialize, .github/skills/specialize and .opencode/skills/specialize in your project.

What does Specialize need to run?

Going by SKILL.md and its folder, Specialize needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.

Does Specialize access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Specialize safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Specialize use?

Specialize is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Specialize use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Specialize?

Skills that share tags, products or a category with Specialize: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 564 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Specialize?

wellwelwel (a GitHub user) maintains it in wellwelwel/lagune, which has 173 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.

Source: wellwelwel/lagune on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Specialize

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Authoring a built-in Lagune sub-skill (development workspace)

Step 1: Run the command's authoring steps, with redirected paths

Step 2: Decide the category (group)

Step 3: Write and register, then verify

Required (a sub-skill is broken without these)

Tests (the suite asserts the catalog and the docs stay in sync)

Documentation (the built-in catalog is enumerated by hand in the website)

Not touched

Quick checklist

Summary to the user

Files

Compare with similar skills

Similar skills

More from wellwelwel/lagune

Related

Questions about Specialize