| name | standalone-bundler |
| description | Plan, preview, and generate focused AI context bundles without requiring repo-local CLIs, MCP servers, apps, web search, memories, or project-specific tooling. Use when a user asks for a reusable or standalone bundling workflow, a compact code bundle, or a bundle-quality rubric independent of project-specific tools. |
Standalone Bundler
Use this skill to create compact, reproducible file bundles without depending on a project-local bundling CLI.
Contract
- Do not assume any project-local bundling CLI is installed.
- Prefer the bundled helper at
../../scripts/bundle_files.py, resolved relative to this SKILL.md.
- Use only local filesystem reads unless the user asks for something else.
- Keep bundle planning read-only by default.
- Use deterministic includes, excludes, search terms, and cwd assumptions.
- Exclude generated files, build output, lock caches, binaries, vendored dependencies, secrets,
node_modules, dist, build, .next, .git, and coverage by default.
- Do not write bundle output unless the user asks for a file artifact.
Helper Usage
From the plugin root:
python3 scripts/bundle_files.py --root /path/to/project --include 'src/**/*.ts' --search auth --preview
python3 scripts/bundle_files.py --root /path/to/project --include 'src/**/*.ts' --search auth --format markdown --output /tmp/context.md
Use multiple --include, --exclude, and --search flags as needed. The helper uses Python stdlib only.
Output Shape
Return this concise structure when planning:
## Bundle Plan
- objective: one sentence
- cwd: absolute path
- preview_command: one helper command
- bundle_command: one helper command
- fallback_command: one narrower or broader helper command
## Manifest
| path_or_pattern | why included | mode |
| --- | --- | --- |
## Quality Rubric
- relevance: target >= 0.80; files with explicit reason divided by total included files.
- coverage: target 1.00 for required categories; list each required surface and the path or pattern that covers it.
- token_efficiency: target <= 0.90 of requested budget; use narrower includes, search terms, or max byte limits when needed.
- redundancy: target duplicate path count 0 and generated/build-output matches 0 unless explicitly requested.
- safety: unsafe file matches and secret-like matches must be 0; exclude sensitive paths by default.
- path_validity: every explicit path must exist or be marked fallback.
- reproducibility: commands must include cwd, deterministic filters, and no interactive steps.
- fallback: define behavior for no files found, no search matches, over-budget output, and safety hits.
## Verification
- local_checks: exact commands to run
- expected_receipts: file count, byte estimate, top files, intentional omissions
- risks: short list
Rubric Details
Treat a good bundle as relevant, complete enough for the task, token-efficient, non-redundant, safe, path-valid, reproducible, and recoverable.
Use --preview first when practical. It prints selected paths and byte estimates without emitting full file contents.
