Skip to content
Back to skills

Config Setup

ASecurity

Sets up configuration files, environment variables, and project configuration. Use when setting up project configuration, environment setup, or configuration management. Creates config files, .env examples, and configuration documentation.

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
developmentjavascriptjavabashnodeapidatabasedocumentation

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill config-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Config Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Config Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-config-setup/badge)](https://www.skillsdirectory.com/skills/majiayu000-config-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: config-setup
description: Sets up configuration files, environment variables, and project configuration. Use when setting up project configuration, environment setup, or configuration management. Creates config files, .env examples, and configuration documentation.
---

# Config Setup Skill

## Instructions

1. Analyze configuration requirements from task
2. Identify what needs to be configured (database, API keys, environment, etc.)
3. Create configuration files
4. Set up environment variable management
5. Create .env.example file
6. Document configuration
7. Return implementation with:
   - Configuration files
   - Environment variable setup
   - .env.example file
   - Configuration documentation

## Examples

**Input:** "Set up environment configuration"
**Output:**
```javascript
// config/index.js
require('dotenv').config();

module.exports = {
    port: process.env.PORT || 3000,
    database: {
        host: process.env.DB_HOST || 'localhost',
        port: process.env.DB_PORT || 5432,
        name: process.env.DB_NAME,
        user: process.env.DB_USER,
        password: process.env.DB_PASSWORD
    },
    jwt: {
        secret: process.env.JWT_SECRET,
        expiresIn: process.env.JWT_EXPIRES_IN || '24h'
    },
    nodeEnv: process.env.NODE_ENV || 'development'
};
```

```bash
# .env.example
PORT=3000
NODE_ENV=development

DB_HOST=localhost
DB_PORT=5432
DB_NAME=myapp
DB_USER=postgres
DB_PASSWORD=

JWT_SECRET=your-secret-key-here
JWT_EXPIRES_IN=24h
```

## Configuration Areas

- **Environment Variables**: .env files, environment setup
- **Application Config**: App configuration, feature flags
- **Database Config**: Database connection, migration config
- **API Config**: External API keys, endpoints
- **Build Config**: Build tools, bundlers, compilers
- **Deployment Config**: Deployment-specific settings
- **Development Config**: Local development setup

## Best Practices

- **No Secrets in Code**: Use environment variables for secrets
- **.env.example**: Provide example file with all required variables
- **Documentation**: Document all configuration options
- **Validation**: Validate configuration on startup
- **Defaults**: Provide sensible defaults where appropriate
- **Environment-Specific**: Different configs for dev/staging/prod

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.