skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

secret-handling

Enforce secret-handling policies that prohibit reading live credential files.

3|3|Updated Apr 13, 2026
Search Tags:#security#secrets#environment-variables#guardrails#git-commit#secret-handling#credential-leak
One-click install
npx skills add https://github.com/quaid-app/quaid --skill secret-handling-quaid-app
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-handling
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/secret-handling
Command: npx skills add https://github.com/quaid-app/quaid --skill secret-handling-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies absolute prohibitions on reading and writing secrets from repository files, preventing credential leaks by agents.

Core Features & Use Cases

  • Prohibits reading live secret files (e.g., .env, .env.*) and writing secrets to committed files.
  • Encourages safe alternatives like .env.example, .env.sample, and .env.template for configuration references.
  • Provides clear workflow guidance for obtaining credentials safely (ask users when needed) and documenting config rules.

Quick Start

Configure the agent to refuse reading real secret files and to consult .env.example for schema when needed.

Frequently Asked Questions about secret-handling

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

FAQPage Schema
How do I prevent credentials from leaking into git commits?▼

Preventing credential leaks in git commits requires enforcing strict guardrails that block agents from reading live secret files like .env and writing exposed credentials into repository workflows.

What is the safest way to manage environment variables in a repository?▼

Safe environment variable management uses .env.example or .env.template files to define configuration schemas without exposing live secrets, while agents interactively request actual credentials from users.

Can an agent read .env files when handling secret configurations?▼

No, agents are prohibited from reading .env files or .env.* variants under strict secret-handling policies, ensuring live credentials remain inaccessible during automated repository workflows.

How do I configure an agent to safely handle secrets and environment variables?▼

Configuring safe secret handling involves setting the agent to refuse reading real secret files and directing it to consult .env.example for configuration schemas when schema references are needed.

When should I use .env.example instead of .env for configuration?▼

Use .env.example, .env.sample, or .env.template when you need to document configuration schemas in committed files, as .env files contain live credentials that must never be read or committed.

Related Skills

Explore More Software Engineering Skills→
robpitcherrobpitcher

secret-handling

Block agents from reading live .env credentials and writing secrets to committed files.

Community
Advanced
oioio-spaceoioio-space

secret-guard

Scan staged Git diffs for credentials, PII, and sensitive data.

Community
Advanced
mikegogulskimikegogulski

abase-ubs

Detect AI-introduced bugs and security vulnerabilities in code before commit.

Community
Advanced
Camilo8902Camilo8902

env-secrets-manager

Manage environment variables and secrets with encryption, rotation, and provider integration.

Community
Advanced