One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill secret-handling-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-handling
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/secret-handling
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill secret-handling-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawned agents have read access to the repository, including .env files containing live credentials. This skill codifies absolute prohibitions and safe alternatives.

Core Features & Use Cases

  • Prohibits reading production secrets from .env files by agents and enforces safe alternatives
  • Prevents writing secrets to .squad/ files and requires redaction or placeholder references
  • Provides pre-commit validation (Scribe) to scan staged changes for secrets and block commits when found, with remediation guidance

Quick Start

Follow the guardrails to configure the system so agents never read live secrets and enable pre-commit checks.

Frequently Asked Questions about secret-handling

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

FAQPage Schema
How do I prevent agents from reading environment secrets in .env files?

To prevent agents from reading environment secrets, enforce absolute prohibitions that block access to live .env files and require consulting .env.example for schema references or asking the user for safe alternatives.

What is the best way to stop secret leaks in Squad workflows?

The best way to stop secret leaks in Squad workflows is to prohibit writing secret data to .squad/ files during decision making and enforce redaction or placeholder references for sensitive values.

How do I set up pre-commit validation to scan staged changes for secrets?

Set up Scribe pre-commit validation to scan staged changes for secrets, block commits containing secret data, and provide remediation guidance to safely remove the leaked credentials.

Does Scribe pre-commit validation block commits containing secrets?

Yes, Scribe pre-commit validation blocks commits containing secrets by scanning staged changes and providing remediation steps to ensure no secret data is committed.

Why must agents consult .env.example instead of reading live .env files?

Agents must consult .env.example instead of live .env files because spawned agents have repository read access, and reading live credentials risks secret leaks, so .env.example provides a safe schema reference.