arkenv

Answer questions about ArkEnv and help implement environment variable validation. Use when developers: (1) Ask about environment variable validation or typesafety, (2) Want to setup ArkEnv in a project, (3) Need to define or update schemas using ArkType or Standard Schema, (4) Are integrating with Vite, Bun, or other runtimes. Triggers on: 'ArkEnv', 'env validation', 'typesafe env', 'createEnv', 'env.ts', '@arkenv/cli'.

Quality

89%

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

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

Highly actionable content with executable examples and a clear, validated setup workflow, but it is a long single-file document that does not use progressive disclosure to push detailed framework and CLI-protocol material into referenced files.

Suggestions

Split the per-framework integration recipes (Next.js/Vite/Bun config + type augmentation) into references/ files and link to them from the body to reduce SKILL.md length and apply progressive disclosure.

Make the Setup workflow's final validation step an explicit validate-fix-retry loop ('if pnpm check fails, fix the reported schema/type errors and re-run').

Move the full --agent JSON protocol and refusal-code catalog into a references/cli-protocol.md, keeping only the escalation pattern summary in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable snippets and specific commands, but includes a few restating sentences (e.g., the Capabilities bullets restate the intro) that could be trimmed; assumes Claude's competence on ArkEnv-specific details.	4 / 5
Actionability	Provides copy-paste-ready, executable code and commands for the common cases across Node, Next.js (codegen + withArkEnv), Vite, and Bun, plus a precise CLI command with flags — fully actionable coverage.	5 / 5
Workflow Clarity	The Setup workflow is a clear six-step sequence with an explicit validation checkpoint (step 6) and the refusal-handling section supplies a feedback loop, but the workflow's own validation step does not spell out the fix-and-retry loop as explicitly as anchor 5.	4 / 5
Progressive Disclosure	Well-organized with section headers, but at ~245 lines it is a single monolithic file with no references to separate files; framework-integration and CLI-agent-protocol detail that could live one level deep is all inlined, and no references/ or scripts/ bundle exists.	3 / 5
	Total	16 / 20 Passed

Description

100%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, third-person description that concretely states capabilities, gives explicit when-to-use guidance with both scenario and keyword triggers, and occupies a distinct niche. No notable gaps.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Answer questions about ArkEnv', 'help implement environment variable validation', 'define or update schemas using ArkType or Standard Schema', 'integrating with Vite, Bun, or other runtimes' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' ('Answer questions about ArkEnv and help implement environment variable validation') and 'when' (a four-item 'Use when developers' list plus an explicit 'Triggers on' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Comprehensive trigger coverage including product name, natural phrases ('env validation', 'typesafe env'), function names ('createEnv'), file paths ('env.ts'), and package identifiers ('@arkenv/cli'), spanning synonyms and extension forms.	5 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche (ArkEnv / typesafe env validation) with product-specific triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	20 / 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: onmax/nuxt-skills
Path: skills/arkenv/SKILL.md
Commit: bc438e5

Reviewed: 6 days 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.