Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Knowledge and guardrails for the mise + fnox + infisical secrets toolchain. Validates tool availability before giving any configuration guidance. Covers the integration chain from remote secret storage through fnox's unified interface to mise task execution, including common failure modes like profile mismatches and token scope limits.
Layering these three tools means secret storage, local abstraction, and task orchestration are each handled separately, and always-on hooks enforce that no hardcoded credentials can reach the editor or shell before the toolchain can intercept them.
When to use it
- Configuring infisical as the remote secrets provider for a new project
- Running dev commands with secrets injected via fnox exec without touching .env files
- Wrapping mise tasks with fnox to keep credentials out of task definitions
- Setting up CI/CD to use service tokens instead of developer login sessions
- Diagnosing silent empty-secrets failures when fnox profile names don't match infisical environment slugs
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: how do I run my dev server with secrets injected from Infisical?
- 1Check that mise, fnox, and infisical are installed using the toolchain validation commands
- 2Verify fnox.toml exists in the project root, prompt user to run fnox init if missing
- 3Check .infisical.json for project and workspace config, prompt infisical init if absent
- 4Show user how to wrap the dev server command with fnox exec -- to inject secrets as env vars
- 5Add a mise task that calls fnox exec so the workflow is repeatable with a single command
Dev server runs with Infisical secrets injected as environment variables, no credentials in source files or task definitions
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.