Skip to main content
skill CX Codex

varlock-claude-skill — Claude Code skill: secrets and setup

The varlock-claude-skill skill adds explicit checks for environment variables and secret exposure across Claude sessions, terminals, logs, and Git commits.

MIT ★ 50,109 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill varlock-claude-skill -a claude-code
Open on GitHub

What varlock-claude-skill does

The skill helps an agent define which environment files and variable names are in scope before work begins. Real values stay in an approved local secret store; prompts, terminal output, and generated reports should use placeholders instead. That keeps sensitive values out of routine checks.

Its procedure uses synthetic canary values to test handling, then reviews destination permissions and ignore rules. The result records the checks performed and the exposure paths that remain. Varlock itself is not bundled, and secret redaction is not enforced, so the installed version and its schema still need separate review.

What it helps with

  • define the environment files and variable names under review
  • keep real secrets out of test prompts and reports
  • test whether values reach logs or Git commits
  • check destination permissions and ignore rules
  • record remaining secret exposure paths

Example prompts for the agent

  • Use @varlock-claude-skill to review environment-variable handling without printing real values.
  • Test a synthetic canary value and check whether it appears in terminal logs, reports, or Git commits.
  • List the environment files and variable names in scope, then report the checks performed and remaining exposure paths.

How to install varlock-claude-skill

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill varlock-claude-skill -a claude-code

2Manually: put the files in place

~/.claude/skills/varlock-claude-skill/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/varlock-claude-skill/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about varlock-claude-skill

How do I install varlock-claude-skill in Claude Code?

Run npx skills add sickn33/agentic-awesome-skills --skill varlock-claude-skill -a claude-code, then inspect ~/.claude/skills/varlock-claude-skill/SKILL.md.

What does varlock-claude-skill do?

It guides explicit checks around environment variables, including scope, placeholder use, synthetic canaries, destination permissions, and Git ignore rules. It also records exposure paths that remain.

Does the skill install Varlock or redact secrets automatically?

No. The entrypoint does not bundle Varlock or enforce redaction, so review the installed version and its schema separately.

Source text

SKILL.md · MIT
---
name: varlock-claude-skill
description: "Secure environment variable management with explicit checks to reduce secret exposure in Claude sessions, terminals, logs, or git commits"
risk: safe
source: "https://github.com/wrsmith108/varlock-claude-skill"
date_added: "2026-02-27"
---

# Varlock Claude Skill

## Overview

Secure environment variable management with explicit checks to reduce secret exposure 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 with explicit checks to reduce secret exposure in claude sessions, terminals, logs, or git commits.

## Procedure

This entrypoint does not bundle Varlock or enforce secret redaction. Inspect a reviewed installed version and its schema using non-secret examples. Establish which environment files and variable names are in scope; never dump values into the conversation, terminal logs or generated reports. Keep real secrets in the authorized local secret store and use placeholders in tests. Verify handling with synthetic canary values and check the destination permissions and ignore rules. Report the actual checks and remaining exposure paths; no guide can guarantee that secrets are never exposed.

Source: [Varlock Claude Skill](https://github.com/wrsmith108/varlock-claude-skill).

## Example

**User request:**

> Use @varlock-claude-skill for this task: Secure environment variable management with explicit checks to reduce secret exposure in Claude sessions, terminals, logs, or git commits.

## 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.

© sickn33 · MIT · sickn33/agentic-awesome-skills

Similar skills

All skills for Git and GitHub →

From the same set187

The whole set →
llm-application-dev-ai-assistant llm-application-dev-ai-assistant — a skill for designing conversational AI assistants: dialogue context, integration boundaries, validation. Fits projects where the bot calls tools and keeps memory of a user. CX Codex +1 ★ 50,109repo stars seo-content-auditor seo-content-auditor reads the draft you hand it, scores depth, E-E-A-T, readability and keyword use, then lists fixes. Useful before a post goes live. CX Codex +1 ★ 50,109repo stars pci-compliance pci-compliance traces payment data through your project and gathers control evidence for a scoped PCI assessment. It does not certify compliance. CX Codex +1 ★ 50,109repo stars security-compliance-compliance-check security-compliance-compliance-check guides regulatory compliance checks for GDPR, HIPAA, SOC2, and PCI-DSS, generating gap analyses, checklists, and technical control code. CX Codex +1 ★ 50,109repo stars secrets-management secrets-management — a skill that walks an agent through secret handling in CI/CD: picking a backend, scoping access, rotating credentials and proving values never reach logs or artifacts. CX Codex +1 ★ 50,109repo stars security-scanning-security-sast security-scanning-security-sast — a skill for static code analysis (SAST) that detects vulnerabilities, hardcoded secrets, and security policy violations across multiple languages and frameworks. CX Codex +1 ★ 50,109repo stars distributed-debugging-debug-trace distributed-debugging-debug-trace sets up debugging and distributed tracing: trace boundaries, key spans, correlation IDs, and a check that traces actually cover the request path. CX Codex +1 ★ 50,109repo stars distributed-tracing Guides distributed tracing setup with OpenTelemetry, Jaeger, and Tempo across microservices. Prevents leaking secrets into spans and verifies collector error handling. CX Codex +1 ★ 50,109repo stars

Project sponsors

Companies that keep this analytics open