secret-handling

Enforce secret-read prohibitions and safe alternatives like .env.example.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill secret-handling-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-handling
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/secret-handling
Command: npx skills add https://github.com/sytone/botnexus --skill secret-handling-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies absolute prohibitions and safe alternatives to prevent agents from reading live secrets in the repository and from writing credentials to .squad/ committed files.

Core Features & Use Cases

  • Enforce restrictions on sensitive file reads (e.g., .env) and provide safe alternatives like .env.example.
  • Guide Scribe pre-commit validation to block risky content, redact secrets, and emit remediation guidance.
  • Offer prompts and best practices for securely obtaining configuration data without exposing credentials in committed history.

Quick Start

Ask the user to use .env.example for schema and guidance instead of reading live secrets.

Frequently Asked Questions about secret-handling

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

FAQPage Schema
How do I prevent AI agents from reading live secrets in my repository?

To prevent AI agents from reading live secrets, enforce restrictions on sensitive files like .env and provide safe alternatives such as .env.example for schema and configuration guidance.

How do I stop credentials from being written to committed files?

Stop credentials from being written to committed files by applying pre-commit validation to block risky content, redact exposed secrets, and emit remediation guidance before artifacts are committed.

What is a safe alternative to using .env files for agent configuration?

A safe alternative to using .env files for agent configuration is .env.example, which provides the required schema and guidance without exposing live credentials or sensitive data to the agent.

How does pre-commit validation detect and remediate secret leakage?

Pre-commit validation detects secret leakage by scanning generated decisions, logs, and histories for risky content, blocking the commit and emitting guidance to redact secrets and use safe alternatives.

Can I use this for secure coding across any codebase with agent access?

Yes, you can use this for secure coding across any codebase where agents access repository files, ensuring safe non-secret data is used in generated decisions, logs, and workflows.