โ† All skills
Tencent SkillHub ยท Developer Tools

Devtools Secrets

Knowledge and guardrails for the mise + fnox + infisical secrets toolchain. Use when the user asks to "configure secrets", "set up fnox", "infisical", "mise...

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Knowledge and guardrails for the mise + fnox + infisical secrets toolchain. Use when the user asks to "configure secrets", "set up fnox", "infisical", "mise...

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
SKILL.md, references/fnox-configuration.md, references/infisical-patterns.md, references/mise-integration.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 9 sections Open source page

DevTools Secrets

Knowledge and guardrails for the mise + fnox + infisical secrets toolchain.

Toolchain Validation

IMPORTANT: Check tool availability before proceeding with any guidance. mise: !command -v mise >/dev/null 2>&1 && echo "INSTALLED ($(mise --version 2>/dev/null | head -1))" || echo "MISSING โ€” install with: curl https://mise.run | sh" fnox: !command -v fnox >/dev/null 2>&1 && echo "INSTALLED ($(fnox --version 2>/dev/null | head -1))" || echo "MISSING โ€” install with: mise use -g fnox" infisical: !command -v infisical >/dev/null 2>&1 && echo "INSTALLED ($(infisical --version 2>/dev/null | head -1))" || echo "MISSING โ€” install with: mise use -g infisical" If any tool above shows MISSING, stop and help the user install it before proceeding. Do not provide configuration guidance for tools that aren't installed.

Project Config State

fnox.toml: !test -f fnox.toml && echo "YES" || echo "NO (run: fnox init)" .infisical.json: !test -f .infisical.json && cat .infisical.json || echo "NO (run: infisical init)" mise.toml env section: !grep -A5 '^\[env\]' mise.toml 2>/dev/null || echo "No env section"

System/Global Config

mise global config: !test -f ~/.config/mise/config.toml && head -10 ~/.config/mise/config.toml || echo "No global mise config" fnox global config: !test -f ~/.config/fnox/config.toml && head -10 ~/.config/fnox/config.toml || echo "No global fnox config" infisical logged in: !infisical user get 2>/dev/null | head -3 || echo "Not logged in or not installed"

Tool Roles

ToolRolemiseTask runner + env manager. Orchestrates dev tooling, runs tasks, manages env vars through plugins.fnoxUnified secret interface. Abstracts over multiple secret backends (infisical, age, env files) with a single CLI.infisicalRemote secrets backend. Stores, syncs, and injects secrets from a central server. These tools complement each other: infisical stores secrets remotely, fnox provides a unified local interface to them, and mise orchestrates tasks that consume secrets via fnox.

Integration Chain

The typical flow: fnox.toml defines infisical as a provider with project/environment config fnox exec -- resolves secrets from the provider and injects them as env vars mise tasks can wrap fnox exec to run commands with secrets injected Alternatively, mise env plugins can call fnox directly for auto-injection on cd

Secrets Enforcement

This project enforces secrets hygiene via always-on hooks in .claude/settings.json (not scoped to this skill): block-hardcoded-secrets.py โ€” Blocks Edit/Write operations containing hardcoded API keys, tokens, passwords, or known secret prefixes (sk-, ghp_, AKIA, xox[bpras]-) block-bare-secret-exports.py โ€” Blocks Bash commands that export secret-like env vars without wrapping in fnox exec or infisical run These hooks are always active regardless of whether this skill is loaded.

Configuration Patterns

Detailed configuration for each tool is in the reference files: @references/mise-integration.md โ€” mise env plugins, tasks, fnox integration @references/fnox-configuration.md โ€” fnox.toml structure, providers, profiles @references/infisical-patterns.md โ€” infisical CLI, scanning, CI/CD

Gotchas

Order matters: fnox.toml must exist before fnox exec works. Run fnox init if missing. Profile mismatches: fnox profiles (dev/staging/prod) must match infisical environment slugs. A mismatch silently returns empty secrets. .infisical.json is safe to commit โ€” it contains project IDs and workspace config, not secrets. fnox.toml may contain sensitive paths โ€” review before committing if using age-encrypted file provider. mise env plugins run on cd โ€” if a plugin calls fnox and fnox is misconfigured, you get errors on every directory change. infisical auth expires โ€” infisical login tokens have a TTL. CI/CD should use INFISICAL_TOKEN (service token) instead. Token path scope is explicit โ€” a service token scoped to / cannot access secrets in child paths like /git_actions. Each path requires its own token or use --recursive with the CLI directly.

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
4 Docs
  • SKILL.md Primary doc
  • references/fnox-configuration.md Docs
  • references/infisical-patterns.md Docs
  • references/mise-integration.md Docs