skills.rest
lewing
lewingCOMMUNITY
Explore all skills by this author →
𝕏@lewingGitHub

stealth-squad

Set up a stealth Squad using a side repository, symlinks, and git excludes.

4|1|Updated Feb 19, 2026
Search Tags:#symlinks#squad#stealth#repository-automation#git-exclude#side-repo
One-click install
npx skills add https://github.com/lewing/agent-plugins --skill stealth-squad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stealth-squad
Source: https://github.com/lewing/agent-plugins/tree/main/plugins/lewing/skills/stealth-squad
Command: npx skills add https://github.com/lewing/agent-plugins --skill stealth-squad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set up a stealth Squad on any repo without modifying tracked files — side-repo + symlinks + git exclude.

Core Features & Use Cases

  • Invisible integration: symlinked agent definitions and configuration live in a separate side repo.
  • Safe experimentation: run Squad in client or third-party repos without committing artifacts.
  • Reconnecting and reusing: easily reattach to new worktrees or forks without touching the target repo.

Quick Start

Create a side repo, then symlink the Squad files into the target project and configure local git excludes.

Frequently Asked Questions about stealth-squad

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up agent configuration files in a repository without modifying tracked files?▼

To set up agent configuration without modifying tracked files, you create a separate side repository, symlink the configuration files into your target project, and configure local git exclude entries to hide them.

Can I run an AI squad in a third-party or client repository without committing artifacts?▼

Yes, you can run an AI squad in a third-party or client repository without committing artifacts by using a stealth setup that coordinates a side repository, symlinks, and git exclude entries.

What is the best way to hide local repository files from version control while keeping them functional?▼

The best way to hide local repository files from version control while keeping them functional is configuring git exclude entries to make untracked files invisible, combined with symlinks pointing to a separate side repository.

How do I reconnect agent files to new git worktrees or forks without touching the target repository?▼

You reconnect agent files to new git worktrees or forks by reattaching the existing symlinks from your side repository to the new working directory, leaving the target repository entirely untouched.

Does using symlinks for side repository configuration work with any git repository scale or context?▼

Using symlinks for side repository configuration works with any git repository scale, including repos you do not own, consulting engagements, and trials where stealth setup is required without leaving artifacts.

Related Skills

Explore More Software Engineering Skills→
tae0ytae0y
14

localdocs-til-link

Create and verify a symlink from localdocs/ to a TIL repository folder.

Community
Intermediate
giang6283623giang6283623
4

agentshield-security-review

Audit AI coding agent configurations and execution surfaces for security vulnerabilities.

Community
Advanced
jchildreejchildree
1

using-git-worktrees

Create and isolate Git worktrees to prevent workspace contamination.

Community
Advanced
mthlimthli
4

sparse-checkout

Hide tracked files locally using Git sparse-checkout patterns.

Community
Intermediate