get-env-var

get an env var, fetch a secret, missing env var, missing token/API key, load secrets from Infisical, infisical. Fetch secrets from the team's Infisical workspace into the shell environment so subsequent commands can use them.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is exemplary: concise, fully executable, well-sequenced with explicit stop/validation checkpoints, and appropriately organized for a simple single-task skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence; it never explains what env vars or secrets are and every line is directly actionable, matching the score-3 anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands with concrete flags (e.g., 'export NAME="$(infisical secrets get NAME --plain --silent)"' and 'infisical run -- <command>').	3 / 3
Workflow Clarity	Sections are clearly sequenced (When to use, Setup, Fetch, Inject) and include explicit validation checkpoints such as the 'If a secret does not exist, STOP' rule and the auth-check feedback loop.	3 / 3
Progressive Disclosure	A simple under-50-line single-task skill with no external references; its well-organized labeled sections satisfy the simple-skill allowance for a top score.	3 / 3
	Total	12 / 12 Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and clearly niche-bound to Infisical, but it stops short of listing multiple distinct actions and lacks an explicit 'Use when...' clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when a command needs an env var that is unset, or a token/API key is missing from the environment') to lift completeness to 3.

Broaden the action list beyond a single fetch action (e.g., mention injecting all project secrets into a single command) to reach the multi-action specificity anchor.

Dimension	Reasoning	Score
Specificity	Names a concrete action and domain ('Fetch secrets from the team's Infisical workspace into the shell environment') but describes essentially a single action rather than multiple distinct concrete actions, so it does not reach the score-3 anchor.	2 / 3
Completeness	It clearly answers 'what' but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied via keyword-style phrases, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes natural phrases users would say such as 'get an env var', 'missing env var', 'missing token/API key', and 'load secrets from Infisical', giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The Infisical-specific niche ('Infisical workspace', 'load secrets from Infisical') with distinct triggers makes it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: different-ai/openwork
Path: .opencode/skills/get-env-var/SKILL.md
Commit: 1345d51

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.