Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config…
Install Lpm Config
$ npx skills add gug007/lpm --skill lpm-config -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gug007/lpm lpm-config --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/lpm-config .claude/skills/lpm-config && rm -rf skills-srcUse ~/.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/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .claude/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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 install https://github.com/gug007/lpm/tree/main/lpm-configType 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.
$ npx skills add gug007/lpm --skill lpm-config -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gug007/lpm lpm-config --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/lpm-config .agents/skills/lpm-config && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .agents/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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.
$ npx skills add gug007/lpm --skill lpm-config -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gug007/lpm lpm-config --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/lpm-config .cursor/skills/lpm-config && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .cursor/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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 https://github.com/gug007/lpm.git --path lpm-config--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gug007/lpm --skill lpm-config -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gug007/lpm lpm-config --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/lpm-config .gemini/skills/lpm-config && rm -rf skills-srcUse ~/.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/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .gemini/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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.
$ gh skill install gug007/lpm lpm-configInstalls 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).
$ npx skills add gug007/lpm --skill lpm-config -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .github/skills && cp -r skills-src/lpm-config .github/skills/lpm-config && rm -rf skills-srcUse ~/.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/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .github/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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.
$ npx skills add gug007/lpm --skill lpm-config -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gug007/lpm lpm-config --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gug007/lpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/lpm-config .opencode/skills/lpm-config && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lpm-config" agent skill from https://github.com/gug007/lpm/tree/main/lpm-config into .opencode/skills/lpm-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lpm-config", 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
lpm-config- GitHub stars
- 152
- Token cost
- ~1.6k tokens
- SKILL.md length
- 719 words
- Files
- 9 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config…
- The user explicitly asks to configure lpm
- SKILL.md covers Load only the relevant reference, Resolve the target, Choose the shape and Apply the change
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Add an lpm service/action/button/zone/terminal
What it does
Lpm Config is an agent skill from gug007/lpm. Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config layers. Use when the user explicitly asks to configure lpm, add an lpm service/action/button/zone/terminal, edit .lpm.yml, or manage lpm templates or global config. For creating or removing linked Git worktrees and operating running projects, use lpm-cli.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `README.md`, `agents/openai.yaml` and `references/actions.md`).
It sits in Development, covering Git worktrees. The repository describes itself as: Start, stop, and duplicate dev projects with one click. The best workspace for running Claude Code, Codex, and other AI agents alongside your services. The licence is MIT.
When your agent uses it
- The user explicitly asks to configure lpm
- Add an lpm service/action/button/zone/terminal
- Manage lpm templates
Example prompts
- “/lpm-config”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 764e997. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Lpm Config loads about 1.6k tokens when it runs, and up to ~9.6k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 719 words of instructions outside code blocks.
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 gug007/lpm at commit 764e997, republished under its MIT licence (© gug007). 719 words, ~1,551 tokens.
Download SKILL.mdSave it as
.claude/skills/lpm-config/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- lpm-config
- description
- Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config layers. Use when the user explicitly asks to configure lpm, add an lpm service/action/button/zone/terminal, edit `.lpm.yml`, or manage lpm templates or global config. For creating or removing linked Git worktrees and operating running projects, use `lpm-cli`.
- version
- 1.3.0
Configure lpm
Create and modify lpm config on macOS exclusively through lpm config get and lpm config apply. Never modify a live project, repo, global, or template config directly with an editor, filesystem tool, patch, redirection, or script. The CLI validates the candidate before the app atomically replaces the destination.
Load only the relevant reference
- Read references/core.md for project identity, services, dependencies, profiles, duplicates, linked Git worktrees, and project creation.
- Read references/actions.md when adding or changing actions, buttons, terminals, inputs, ports, shortcuts, colors, agent prompts, or nested menus.
- Read references/zones.md when creating, filling, rearranging, or removing button zones or zone layers.
- Read references/sharing.md for
.lpm.yml, global config, templates,extends, layering, and sparse overrides. - Read references/ssh.md for remote projects or
mode: sync. - Read references/validation.md before preparing a candidate and follow its transactional workflow.
Resolve the target
Honor an explicit project or layer from the user. Otherwise run:
lpm config resolve --cwd . --jsonInterpret the result:
- One match: use the returned project name with
lpm config get; never edit the returnedpath. A match locates the file even when the app cannot load it; validation reports what to fix. - Multiple matches: ask which candidate to use.
- No match: offer to create a project for the current directory or configure one of the returned
availableprojects.
Use these explicit layer overrides:
- “globally” or “all my projects” →
~/.lpm/global.yml - “share with the team”, “check it in”, or “for everyone” →
<root>/.lpm.yml - “template” or “reuse across projects” →
~/.lpm/templates/<name>.yml
When lpm config resolve is unavailable, inspect the YAML project files read-only. Match the current directory against expanded root paths by path components; the deepest root wins. An SSH project never matches by root or ssh.dir (a path on the host); only its local sync mirror ~/.lpm/sync/<project> matches, where <project> is the project's file name (~/.lpm/projects/<project>.yml), not its name: field. Do not parse YAML with line-oriented tools and do not write a config without lpm config apply.
Choose the shape
| Intent | Config shape |
|---|---|
| Long-running process started with the project | services |
| One-shot command or button | actions |
| Persistent interactive shell | actions with type: terminal |
| Start prerequisites first | service dependsOn |
| Ask for parameters | action inputs |
| Default action plus alternatives | parent cmd plus nested actions |
| Split button whose main segment repeats the last used option | parent primary: last-used plus nested actions |
| Menu with no default | nested actions without parent cmd |
| Framed group of buttons in the header or footer | zones entry with rows, plus display: <zone> on each button |
| Several button sets in one zone, switched with dots | zone layers, plus layer: <key> on each button |
| Put a button declared elsewhere into a zone or layer | sparse override with display, layer, and position only |
| Colored button or terminal tab | action color |
| Agent terminal that starts with a task | type: terminal with an agent cmd plus prompt |
| Hidden command with completion notification | type: background |
| Send command into the focused terminal | type: command |
| Reused visible pane | type: terminal plus reuse: true |
| Team-shared config | <root>/.lpm.yml |
| Reusable action set | template plus extends |
| Remote execution | project ssh block |
Ask only when the requested shape is genuinely ambiguous. For “button with options,” distinguish a split button, dropdown, and input prompt. For a terminal action, distinguish one reused pane from a fresh pane each run.
Show full SKILL.md (189 more words)Show less
Apply the change
For a new project, inspect repo signals such as package.json, Makefile, docker-compose.yml, Procfile, and mise.toml. Detect long-running services separately from one-shot test, lint, build, migration, and deploy actions.
Read the selected layer and its revision:
lpm config get --layer project --project <name> --json
lpm config get --layer repo --project <name> --json
lpm config get --layer global --json
lpm config get --layer template --template <name> --jsonUse --create with both get and apply when intentionally creating a missing project or template. Build the candidate from the returned content in a temporary file, preserving unrelated fields and formatting where practical. Use shorthand only when an entry needs no options. Set confirm: true for destructive operations.
Apply the candidate using the exact returned revision:
lpm config apply --layer <layer> <target-args> \
--if-revision <revision> --file <candidate-path> --jsonThe command must return applied: true before reporting success. Fix validation errors in the temporary candidate and retry. On a revision conflict, run get again and reapply the intended change to the new content instead of forcing an overwrite.
Confirm only before replacing an existing config during intentional creation. Do not confirm an unambiguous edit. Config deletion must go through the lpm app; never delete a config file directly.
If the app is not running or config get/apply is unavailable, tell the user to start or update lpm. Do not fall back to direct writes.
© gug007, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (references) in lpm-config of gug007/lpm.
- SKILL.md
- README.md
- agents/openai.yaml
- references/actions.md
- references/core.md
- references/sharing.md
- references/ssh.md
- references/validation.md
- references/zones.md
Open the folder on GitHubat commit 764e997
Compare with similar skills
Lpm Config 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lpm Config this skillgug007/lpm | 152 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Build Px4 macOSPX4/PX4-Autopilot | 13k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| Git Worktree IsolationjnMetaCode/superpowers-zh | 8.3k | 1 repos | ~982 | Automated safety check: Pass | MIT | |
| WorktreeAgentsMesh/AgentsMesh | 2.4k | — | ~553 | Automated safety check: Notes | Custom licence | |
| Cursor Composer Task DelegateChachamaru127/claude-code-harness | 3.2k | — | ~4.4k | Automated safety check: Notes | MIT |
Similar skills
Build Px4 macOS
PX4/PX4-Autopilot
Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.
Git Worktree Isolation
jnMetaCode/superpowers-zh
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Worktree
AgentsMesh/AgentsMesh
Creates or reuses an isolated AgentsMesh Git worktree from a verified base branch, preserves existing changes, and optionally starts the worktree-scoped development environment.
Cursor Composer Task Delegate
Chachamaru127/claude-code-harness
Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.
Git Worktree Setup
k8zdev/k8z
Automate git worktree creation and copy private files (not tracked in git) to new workdirs.
More from gug007/lpm
All 12 skills in this repoShort
gug007/lpm
Make a short vertical (9:16) lpm lesson that feels native to TikTok, Reels and Shorts: a payoff-first hook, fast push-ins that follow the action, word-by-word burned-in captions, numbered step…
Short Game
gug007/lpm
Make a short vertical (9:16) video where two AI models build the same self-playing game in lpm, side by side, and both games then play live in lpm's browser.
Short Race
gug007/lpm
Make a short vertical (9:16) video that races two AI models on the same prompt in lpm, side by side: Run in duplicates puts each model in its own copy of the project, shown as side-by-side columns…
App Store Screenshots
gug007/lpm
Make the App Store screenshots for lpm Link (iPhone 6.3" 1206x2622 and iPad 13" 2064x2752) from the current mobile/ source: a screenshot build of the app opens each screen straight into Demo Mode…
Short Publish
gug007/lpm
Post a finished vertical lesson from ~/Movies/lpm-lessons/tiktok/<slug/ to YouTube Shorts (LPM channel, through Chrome) and TikTok (@lpm06557, from the user's iPhone through iPhone Mirroring) in…
App Review Video
gug007/lpm
Record the App Store review demo video for lpm Link: the lpm desktop app and lpm Link on a physical iPhone (live through iPhone Mirroring) side by side, pairing and then controlling the Mac from the…
Related
Categories
Questions about Lpm Config
What does Lpm Config do?
Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config…. Lpm Config is an agent skill from gug007/lpm. Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config layers.
When should I use Lpm Config?
Lpm Config fits situations like: the user explicitly asks to configure lpm; add an lpm service/action/button/zone/terminal; manage lpm templates.
How do I install Lpm Config in Claude Code?
Run `npx skills add gug007/lpm --skill lpm-config -a claude-code`. Or copy the skill folder (lpm-config in gug007/lpm) into .claude/skills/lpm-config in your project. Claude Code loads it when a task matches its description.
How do I install Lpm Config in Codex?
Run `npx skills add gug007/lpm --skill lpm-config -a codex`. Or copy the skill folder (lpm-config in gug007/lpm) into .agents/skills/lpm-config in your project. Codex loads it when a task matches its description.
Can I use Lpm Config 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 gug007/lpm --skill lpm-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lpm-config, .gemini/skills/lpm-config, .github/skills/lpm-config and .opencode/skills/lpm-config in your project.
What does Lpm Config need to run?
SKILL.md names no scripts, command-line tools or credentials: Lpm Config is instructions for the agent only. Our summary lists: Docker.
Does Lpm Config access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lpm Config 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 Lpm Config use?
Lpm Config 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 Lpm Config use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.1k tokens, read only when the agent opens those files.
What are the alternatives to Lpm Config?
Skills that share tags, products or a category with Lpm Config: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Build Px4 macOS (PX4/PX4-Autopilot, 13k stars), Git Worktree Isolation (jnMetaCode/superpowers-zh, 8.3k stars) and Worktree (AgentsMesh/AgentsMesh, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lpm Config?
gug007 (a GitHub user) maintains it in gug007/lpm, which has 152 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: gug007/lpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.