setup-env

Configure .env files with GitHub credentials and verify tokens via the GitHub API.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill setup-env-nicolehaugen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-env
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.github/skills/setup-env
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill setup-env-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of setting up and verifying GitHub credentials and environment variables, eliminating manual steps and potential errors.

Core Features & Use Cases

  • Automate .env Configuration: Automatically creates or updates the .env file with GitHub Personal Access Tokens (PAT), organization, repository, and enterprise slugs.
  • Token Verification: Checks the validity of the GitHub token against the GitHub API to ensure proper permissions and access.
  • Use Case: When setting up the CustomMetricsDashboard, this Skill simplifies the process by guiding users through credential configuration and verification, making the initial setup faster and more secure.

Quick Start

Execute the setup-env skill to automatically configure your GitHub credentials and verify your token.

Frequently Asked Questions about setup-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub credentials setup for my environment configuration?

You can automate GitHub credentials setup by executing a script that creates or updates the .env file with your Personal Access Token, organization, repository, and enterprise slugs, eliminating manual configuration errors.

Do I need curl to verify a GitHub Personal Access Token?

Yes, you need curl or a similar tool capable of making API requests, along with write access to the .env file, to successfully configure credentials and verify token authenticity.

Can I use this setup to configure .env files with GitHub enterprise slugs?

Yes, the environment configuration process automatically populates the .env file with GitHub Personal Access Tokens, organization details, repository names, and enterprise slugs for secure automated access.

Why does my GitHub token verification fail during environment configuration?

Token verification fails when the GitHub API rejects the Personal Access Token due to insufficient permissions, expired credentials, or incorrect organization and repository slug entries in the .env file.

What is the best way to configure a .env file for GitHub access tokens?

The best way to configure a .env file for GitHub access tokens is through an automated setup script that writes the PAT, organization, repository, and enterprise slugs directly and verifies them via the API.