CtrlK
BlogDocsLog inGet started
Tessl Logo

env-manager

Use when the user provides API keys, tokens, or other configuration values that should persist across sessions, or when the user asks to query, list, or delete saved environment variables. Manages personal env by default and workspace env only when explicitly requested.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend/super-magic/agents/skills/env-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill is highly actionable with executable snippets for every operation and clear scope semantics, but it is padded with near-identical boilerplate repeated across sections and lacks explicit validation/confirmation steps for its destructive unset_env operations. Consolidating the repeated snippet into one parameterized form and adding verification guidance would materially improve it.

Suggestions

Replace the eight near-identical code blocks with one parameterized example plus a compact table mapping (operation, scope) to the tool-call arguments, eliminating the duplicated boilerplate.

Add an explicit verification or confirmation step before unset_env (e.g., call get_env first to confirm the key exists / confirm with the user before deleting), since deletion is destructive.

Note that the body claims 'set_env' is supported but the description omits 'set' from its action list — add 'set' to the description for consistency.

DimensionReasoningScore

Conciseness

The body repeats the same 8-line boilerplate snippet for each of 8 sections, differing only in a one-line tool-call dict, and re-explains scope-priority rules multiple times; this is noticeably padded and could be collapsed into one parameterized example plus a small call-reference table.

2 / 5

Actionability

Each operation is backed by a copy-paste-ready Python snippet calling the real tool with concrete arguments, covering set/get/list/unset across all scopes; only minor gaps (no error-handling guidance beyond SystemExit) keep it below a 5.

4 / 5

Workflow Clarity

Operations are organized into clearly labeled per-task sections, but destructive/batch operations (unset_env, set_env) lack explicit validation or confirmation checkpoints and rely on implicit `if not result.ok: raise`, which under the rubric's validation cap limits this to a 3.

3 / 5

Progressive Disclosure

Content is well-organized into logical sections under one file with no nested references (none exist), which is appropriate for a skill of this size; the heavy duplication across sections is the only structural weakness keeping it from a 5.

4 / 5

Total

13

/

20

Passed

Description

83%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.

A strong, well-scoped description with a clear 'Use when...' trigger, concrete actions, and an explicit personal-vs-workspace default distinction. It could be marginally stronger by listing 'set' alongside query/list/delete and tightening the somewhat broad 'configuration values' phrasing.

DimensionReasoningScore

Specificity

Names the domain (env var management) and several concrete actions ('query, list, or delete saved environment variables', persist across sessions), with the personal-vs-workspace scope distinction adding specificity; minor gaps in coverage (no explicit 'set' in the description) keep it just below a 5.

4 / 5

Completeness

Explicitly answers both 'what' (manages personal/workspace env, query/list/delete) and 'when' with a concrete 'Use when...' trigger clause covering both provision and query scenarios, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user-facing terms like 'API keys, tokens, or other configuration values' and 'saved environment variables' that users would plausibly say, but lacks synonyms/file extensions and a few common phrasings, placing it slightly below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The env-var persistence niche is fairly distinct with clear triggers, but the broad 'configuration values' framing creates minor overlap risk with general config/secrets skills, keeping it just below a 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dtyq/magic
Reviewed

Table of Contents

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.