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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/get-env-var/SKILL.md

The canonical home for this skill is get-env-var in different-ai/openwork

Quality

Content

93%Weight 40%Scale 1-5

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

The content is tight, fully executable, and well-structured for a simple single-purpose skill, with a clear error-handling checkpoint for missing secrets. The only minor gap is the absence of an explicit post-fetch validation step.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what Infisical or env vars are, and every line (install, auth, fetch, inject, rules) earns its place.	5 / 5
Actionability	Copy-paste-ready commands like `export NAME="$(infisical secrets get NAME --plain --silent)"` and `infisical run -- <command>` cover the common fetch and inject cases with fully executable syntax.	5 / 5
Workflow Clarity	Setup and fetch are clearly sequenced with an error feedback loop ("If a secret does not exist, STOP..."), but there is no explicit verify step confirming the fetched value is non-empty before use, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	This is a short single-purpose skill with no bundle files and well-organized sections (When to use, Setup, Fetch, Inject, Rules), satisfying the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

65%Weight 40%Scale 1-5

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 has strong distinctiveness and good trigger-term coverage, but the lack of an explicit "Use when..." clause and the keyword-stuffing style of the trigger list keep completeness capped. Specificity is adequate but limited to a single action.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when a command needs an env var or secret that isn't set") to raise completeness above 3.

Lead with the descriptive sentence and move the keyword list into a clearly framed trigger clause so it reads as guidance rather than search-term stuffing.

Consider mentioning additional capabilities (e.g., injecting all project secrets into a command) to broaden specificity beyond a single fetch action.

Dimension	Reasoning	Score
Specificity	"Fetch secrets from the team's Infisical workspace into the shell environment" names the domain and one concrete action, but offers no broader coverage of capabilities, matching the 1-2-action anchor.	3 / 5
Completeness	The "what" is stated clearly, but the "when" appears only as a comma-separated keyword dump with no explicit "Use when..." clause, so per the cap guidance completeness stays at 3.	3 / 5
Trigger Term Quality	Natural trigger terms like "get an env var", "missing token/API key", and "load secrets from Infisical" give good keyword coverage with synonyms, though a few natural variants (credential, password) are absent.	4 / 5
Distinctiveness Conflict Risk	The Infisical-specific niche ("team's Infisical workspace") with distinct triggers gives a clear scope and minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 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: Devin-AXIS/iPolloWork
Path: .opencode/skills/get-env-var/SKILL.md
Commit: 5dd8875

Reviewed: 1 day 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.