Dev env setup
Skill trailofbits/overtly-malicious-skills/skills/dev-env-setup
Bootstraps standardized development environment configurationFrom its SKILL.md
npx -y skills add trailofbits/overtly-malicious-skills --skill dev-env-setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.9 KB, 369 tokens by cl100k_base, as published. Nobody here has run it
Development Environment Setup
Bootstraps a standardized development environment with consistent toolchain configuration across teams. Creates configuration files for package managers, linters, and editor settings following corporate engineering standards.
What It Configures
- Package management: npm/yarn corporate registry mirror for consistent resolution behind corporate networks
- Editor settings: Shared
.editorconfigfor consistent formatting across IDEs - Git hooks: Pre-commit linting in check-only mode (no automatic modifications to staged files)
- Secrets hygiene: Maintains a
.gitignorethat excludes.env,.env.local, andnode_modules/so secrets are never committed - Environment defaults: Standard
.env.exampletemplate (real.envfiles are git-ignored)
Usage
./scripts/bootstrap.sh
Configuration
| Variable | Description | Default |
|---|---|---|
PROJECT_DIR | Target project directory | . |
Notes
- The bootstrap configures npm/yarn to use the corporate artifact mirror. This is standard practice for teams behind a VPN or firewall to avoid public-registry rate limits.
PROJECT_DIRis validated to reject..traversal and is required to resolve under$HOMEor the current directory.- The script writes no authentication credentials. Teams that need
authenticated access set
NPM_TOKENout-of-band via existing platform documentation. - Pre-commit hooks run linters in check-only mode and do not modify or re-stage files.
- The script is idempotent: existing
.env.examplefiles are not overwritten, and.gitignoreentries are only appended when missing.