skills.rest
Vel-Labs
Vel-LabsOFFICIAL
Explore all skills by this author →
GitHub

credential-safety

Detect exposed credentials and unsafe environment configurations in ClearIntent workflows.

Updated Apr 26, 2026
Search Tags:#security#auditing#credentials#secret-management#onchain#wallets#env-files
One-click install
npx skills add https://github.com/Vel-Labs/ClearIntent --skill credential-safety
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: credential-safety
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/credential-safety
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill credential-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use before any work that touches credentials, local environment files, wallet keys, live provider config, or operator setup for 0G, ENS, KeeperHub, wallets, or testnet execution.

Core Features & Use Cases

  • Never print, paste, commit, summarize, or transform private keys, seed phrases, API keys, wallet secrets, session cookies, wallet state, or auth tokens.
  • Prefer .env.local only for non-secret runtime config. Keep .env.example as the tracked runtime template.
  • Stop and report before proceeding if secret material is exposed or live writes are enabled unexpectedly.

Quick Start

Run npm run clearintent -- credentials status to verify your credentials posture in the workspace.

Frequently Asked Questions about credential-safety

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

FAQPage Schema
How do I prevent exposing private keys and wallet secrets in ClearIntent workflows?▼

To prevent exposing private keys and wallet secrets in ClearIntent workflows, you must never print, paste, commit, or transform sensitive credentials. The system stops and reports the issue before proceeding if secret material is exposed or live writes are unexpectedly enabled.

What is the correct way to manage .env files for 0G, ENS, and KeeperHub operator setups?▼

Managing .env files for 0G, ENS, and KeeperHub setups requires using .env.local only for non-secret runtime config. You must keep .env.example as the tracked runtime template while ignoring local secrets in a separate operator secrets file.

How do I check my credentials posture before running testnet execution?▼

You can check your credentials posture before testnet execution by running the npm run clearintent -- credentials status command. This verifies your workspace configuration and ensures no sensitive environment variables are improperly exposed.

When should I use a separate operator secrets file for provider tokens?▼

You should use a separate operator secrets file for provider tokens whenever handling live provider config or operator setup for 0G, ENS, KeeperHub, or wallets. This isolates sensitive authentication data from tracked runtime templates like .env.example.

Why does my workflow stop before proceeding with live writes enabled?▼

Your workflow stops before proceeding with live writes enabled because credential safety mechanisms automatically halt execution to prevent accidental exposure. This safeguard triggers when unexpected live writes or exposed secret material like session cookies are detected.

Related Skills

Explore More Software Engineering Skills→
nghiahsgsnghiahsgs
32

env-manager

Generate and validate .env.local and .env.example templates for taw-kit projects.

Community
Intermediate
Vel-LabsVel-Labs

adapter-scaffold

Create and validate ClearIntent adapters with typed success, degraded, and failure states.

Official
Intermediate
idchain-worldidchain-world
16

wallet

Access OWS wallet addresses, sign messages, and broadcast transactions without exposing private keys.

Official
Intermediate
bennybennisonbennybennison

environment-management

Manage typed settings and encrypted .env files for Python applications.

Community
Intermediate