> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Work on the Command Line Part 2 Environment templates
> Configuring `/etc/skel` defines default files and settings for new user accounts, streamlining onboarding and enforcing policies.
Configuring the `/etc/skel` directory allows you to define default files and environment settings for every new user account. When you create a user with the `-m` flag, all contents of `/etc/skel` are copied into the new home directory—making it easy to enforce policies, defaults, and customizations.
## Table of Common Skeleton Files
| File | Purpose | Description |
| --------------- | ------------------------------------ | ----------------------------------------------------------------------------- |
| `.bashrc` | Shell configuration | Defines aliases, functions, and environment variables for interactive shells. |
| `.bash_profile` | Login shell startup | Exports user-specific environment variables and initializes the login shell. |
| `README` | Onboarding notice or policy document | Displays a default message or policy for every new user. |
## 1. Adding a Default README for All New Users
To inform new users about your site policy or housekeeping rules, place a `README` file in `/etc/skel`:
```bash theme={null}
sudo vim /etc/skel/README
```
Add your message, for example:
```text theme={null}
Please don’t run CPU-intensive processes between 8 am and 10 pm.
```
Save and exit. Every future user will see this notice in their home directory.
Files in `/etc/skel` are only applied when a home directory is created (e.g., via `useradd -m`). Existing users are unaffected.
## 2. Testing with a New User
Create a new user named **trinity** and verify that the `README` was copied:
```bash theme={null}
sudo useradd -m trinity
ls -a /home/trinity
# . .. .bash_logout .bash_profile .bashrc README
```
Confirm the contents:
```bash theme={null}
cat /home/trinity/README
# Please don’t run CPU-intensive processes between 8 am and 10 pm.
```
## 3. Setting Up a Custom `PATH` for One User
If **trinity** needs access to tools in `/opt/bin`, prepend that directory to her `PATH`. Edit her `.bashrc`:
```bash theme={null}
sudo vim /home/trinity/.bashrc
```
Add or modify the `PATH` line:
```bash theme={null}
PATH="$HOME/.local/bin:$HOME/bin:/opt/bin:$PATH"
```
Save and exit. For immediate effect, have Trinity run:
```bash theme={null}
source ~/.bashrc
echo $PATH
# /home/trinity/.local/bin:/home/trinity/bin:/opt/bin:/usr/local/bin:/usr/bin:...
specialtool # runs /opt/bin/specialtool
```
Always ensure each entry is separated by a colon (`:`) and that `$PATH` remains at the end.
## 4. Customizing the Default `.bashrc` for All New Users
To apply the same `PATH` change (or any other environment tweaks) site-wide, modify the skeleton `.bashrc`:
```bash theme={null}
sudo vim /etc/skel/.bashrc
```
Insert your custom lines—such as the `PATH` definition—then save. Now, every new account created on this system will inherit these settings automatically.
Be careful when editing `/etc/skel/.bashrc`. Errors in this file may prevent newly created users from logging in correctly.
***
Now you’re ready to manage default user environments using `/etc/skel`. Practice by adding more config files or policies to streamline onboarding for every new account!