skills.rest
4e696b6f
4e696b6fCOMMUNITY
Explore all skills by this author →
GitHub

clawsec-env

Scan repositories for credential exposure risks and missing security configurations.

Updated Mar 9, 2026
Search Tags:#security#secrets#credentials#sandboxing#env files#ci security
One-click install
npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-env
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clawsec-env
Source: https://github.com/4e696b6f/clawsec-agent/tree/main/skills/clawsec-env
Command: npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies and helps mitigate risks associated with credential exposure, such as unignored environment files, missing security checks, and inadequate agent isolation.

Core Features & Use Cases

  • Credential Exposure Detection: Scans for .env files that are not properly ignored by version control.
  • Security Best Practices: Verifies the presence of pre-commit hooks, SECURITY.md files, and CI workflows for agent security.
  • Agent Isolation: Checks for seccomp profiles to ensure agents run in a sandboxed environment.
  • Use Case: Ensure that sensitive API keys and database credentials stored in .env files are never accidentally committed to your code repository.

Quick Start

Run the clawsec-env skill to scan for credential exposure risks in the current directory.

Frequently Asked Questions about clawsec-env

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

FAQPage Schema
How do I check if my .env files are exposed in version control?▼

To check .env file exposure, scan your repository for environment files and verify .gitignore coverage using grep. This identifies credentials and secrets that are not properly ignored by version control and risk being committed.

What security best practices should a code repository have for credential management?▼

Repository security best practices include adding pre-commit hooks, maintaining a SECURITY.md file, and configuring CI workflows for agent security. These checks prevent accidental credential exposure and enforce security policies.

How do I scan my agent environment for missing seccomp sandboxing profiles?▼

Scanning for seccomp sandboxing profiles involves checking the agent environment configuration to ensure agents run in an isolated state. This verifies that adequate seccomp profiles are present to restrict system calls and enforce isolation.

Can I run a security audit on my repository without installing dependencies?▼

Yes, you can run a repository security audit using only shell commands for file system checks and grep for .gitignore coverage. No external dependencies are required to scan for missing security files and credential exposure risks.

What is the best way to prevent API keys and database credentials in .env files from being committed?▼

The best way to prevent credential exposure is scanning for unignored .env files and verifying .gitignore coverage. This detects sensitive API keys and database credentials before they are accidentally committed to your code repository.

Related Skills

Explore More Software Engineering Skills→
dennisonbertramdennisonbertram
1

dotenv-audit

Scans .env files and code for exposed secrets and missing entries.

Community
Intermediate
rocklambrosrocklambros
2

scaffolding-security-research-repo

Scaffold empty security-research repositories with governance, disclosure, and hardening files.

Community
Advanced
TeiNamTeiNam
12

security-scan

Scan agent configurations for security vulnerabilities and misconfigurations.

Community
Intermediate
cwinvestmentscwinvestments
412

memstack-security-secrets-scanner

Scan source code and git history for hardcoded secrets and leaked API keys.

Community
Intermediate