varlock-claude-skill
Security tool for environment variable management, preventing secret leaks in development workflows.
Install
mkdir -p .claude/skills/varlock-claude-skill-anhvu1107 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16675" && unzip -o skill.zip -d .claude/skills/varlock-claude-skill-anhvu1107 && rm skill.zipInstalls to .claude/skills/varlock-claude-skill-anhvu1107
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
ALWAYS use this when the request matches Varlock Claude Skill: Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commitsKey capabilities
- →Manage secure environment variables
- →Prevent exposure of secrets in Claude sessions
- →Prevent exposure of secrets in terminals
- →Prevent exposure of secrets in logs
- →Prevent exposure of secrets in git commits
How it works
This skill provides guidance and patterns for secure environment variable management, ensuring that secrets are not exposed in Claude sessions, terminals, logs, or git commits.
Inputs & outputs
When to use varlock-claude-skill
- →Secure environment variables
- →Hide secrets from logs
- →Prevent credential leaks in git
- →Manage secure keys
About this skill
Varlock Claude Skill
Selective Reading Rule
Start with:
references/senior-master-standard.mdreferences/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
Overview
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
When to Use This Skill
Use this skill when you need to work with secure environment variable management ensuring secrets are never exposed in claude sessions, terminals, logs, or git commits.
Instructions
This skill provides guidance and patterns for secure environment variable management ensuring secrets are never exposed in claude sessions, terminals, logs, or git commits.
For more information, see the source repository.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
When not to use it
- →When the task does not involve secure environment variable management
- →When the task does not involve preventing secret exposure in Claude sessions
- →When the task does not involve preventing secret exposure in terminals, logs, or git commits
Limitations
- →Limited to secure environment variable management
How it compares
This skill focuses specifically on preventing secret exposure in various development contexts, including AI sessions, which is a specialized aspect of environment variable management.
Compared to similar skills
varlock-claude-skill side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| varlock-claude-skill (this skill) | 0 | 4mo | No flags | Beginner |
| security-ownership-map | 2 | 6mo | Review | Advanced |
| github-archive | 1 | 4mo | Review | Advanced |
| auditing-pre-release-security | 1 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Anhvu1107
View all by Anhvu1107 →You might also like
security-ownership-map
openai
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
github-archive
gadievron
Investigate GitHub security incidents using tamper-proof GitHub Archive data via BigQuery. Use when verifying repository activity claims, recovering deleted PRs/branches/tags/repos, attributing actions to actors, or reconstructing attack timelines. Provides immutable forensic evidence of all public GitHub events since 2011.
auditing-pre-release-security
OneKeyHQ
Audits security and supply-chain risk between two git refs, 预发布安全审计
security-scan
redpanda-data
Resolve npm dependency vulnerabilities detected by security scans.
windsurf-dependency-management
jeremylongshore
Analyze and update dependencies with vulnerability scanning. Activate when users mention "update dependencies", "security audit", "npm audit", "vulnerability scan", or "dependency updates". Handles dependency analysis and updates. Use when working with windsurf dependency management functionality. Trigger with phrases like "windsurf dependency management", "windsurf management", "windsurf".
github-recon
zebbern
Scan Git repositories, GitHub organizations, and source code for leaked secrets, API keys, credentials, and sensitive data. Use when analyzing source code security, when checking for credential exposure, or when the user mentions secret scanning or credential leaks.