# Li Pack Create

> Use to create a blank, inherited, or cloned Lintel pack and validate it before activation.

- Skill: `jokerman89/li-pack-create` (Agent Skill)
- Install (CLI): `npx get-skill add jokerman89/li-pack-create`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jokerman89/li-pack-create/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jokerman89 (https://skillmd.com/u/jokerman89)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jokerman89/li-pack-create

---


> **Lintel on GitHub Copilot.** Generated from `skills/pack-create/SKILL.md`; edit the canonical file, then run
> `li-copilot init`.
> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,
>   `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`
>   tree, never into the resource root.
> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a
>   `<base>` that the workflow defines as its own directory) mean
>   `../../../skills/pack-create/` in the Lintel source, not this generated folder.
>   `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step
>   runs in the working repository, so use `$LINTEL_SKILLS_DIR/pack-create/` there.
> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never
>   `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run
>   `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`
>   and the profile context.
> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,
>   Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`
>   with that custom agent, WebFetch=`web_fetch`.
> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their
>   files. Named roles such as `CodeReviewer` are custom agents.

# Pack create

Retained front door to [pack lifecycle: create](../../../skills/pack-switch/references/lifecycle.md#create).
Follow that complete method for blank, inherited (`--extends`) or cloned-manifest
(`--from`) creation, explicit `--scope repo|home`, collision refusal, validation,
pattern assets and extension-skeleton limits.

This publishes a reviewed manifest, not a new active profile. No automatic
activation, private synchronization or host installation follows. Existing pack
edits and one-off workflow choices do not require creating another pack.

