Set up a dev environment in an existing worktree (make dev + copy secrets)
77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Prepare the worktree at $ARGUMENTS for development.
bash tools/setup_worktree_env.sh <worktree-path>The script runs make dev and copies secrets without exposing credentials in the conversation. If it fails, report the error and stop.
Parse the script output for SECRETS_SOURCE= to determine what was used:
repo_root: Full credentials available — all destinations including remote (snowflake, bigquery, etc.)dev_template: Local only — duckdb, dummy, filesystem, and container-based destinations (postgres, clickhouse, etc.)none: No secrets found — warn the userDev environment ready: <worktree-path>
- make dev: done
- secrets.toml: <source>e3e58fe
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.