CtrlK
BlogDocsLog inGet started
Tessl Logo

use-native-credential-proxy

Opt out of the OneCLI gateway and supply Anthropic credentials from .env instead. For users who want simple .env-based credential management without the OneCLI agent vault. Reads the API key or OAuth token from .env and injects it into the container's API requests.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/use-native-credential-proxy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

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

The skill body is concise, highly actionable, and clearly sequenced with validation checkpoints, troubleshooting, and removal guidance. Its one gap is progressive disclosure — at ~156 lines it could offload the .env.example stub and removal steps into a real bundled reference rather than keeping them inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explaining of basic concepts — and every section earns its tokens with concrete commands and exact paths; the only long passage (the credential-home inversion callout) is justified as a genuine anti-pattern warning.

3 / 3

Actionability

It provides fully executable, copy-paste-ready bash and TypeScript snippets with exact file paths, grep/sed one-liners, and precise insertion points, matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

Four phases are clearly sequenced with a pre-flight idempotency check and an explicit validate step (pnpm build + vitest) with failure feedback, plus troubleshooting and removal sections providing recovery loops.

3 / 3

Progressive Disclosure

The body is well-sectioned but has no bundle directory and no clearly signaled one-level-deep references — details like the .env.example stub and removal procedure stay inline, and the only external pointer (REMOVE.md) is to a non-bundle repo file rather than a structured reference.

2 / 3

Total

11

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 and well-differentiated but lacks an explicit "Use when..." trigger clause and leans on product-specific jargon for its trigger terms. Adding a concrete trigger sentence would lift completeness and trigger_term_quality.

Suggestions

Append an explicit trigger clause such as "Use when you want to bypass the OneCLI gateway and manage Anthropic credentials via .env, or when the OneCLI vault is unavailable."

Soften jargon in the trigger terms — add natural phrasings a user might say (e.g., "API key", "OAuth token", "credentials") alongside "OneCLI gateway".

Move the audience rationale ("For users who want simple .env-based credential management...") into the trigger clause so the "when" is explicit rather than implied.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Opt out of the OneCLI gateway", "supply Anthropic credentials from .env", "Reads the API key or OAuth token from .env", "injects it into the container's API requests" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers "what" but the "when" is only an implied audience clause ("For users who want...") rather than an explicit "Use when..." trigger, which the guideline caps at 2.

2 / 3

Trigger Term Quality

Contains relevant terms ("credentials", ".env", "API key", "OAuth token") but leans on product jargon ("OneCLI gateway", "agent vault") and misses common natural user phrasings, so it is not the full-coverage level 3.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche — the NanoClaw native .env credential path as an explicit opt-out of the OneCLI gateway — making it unlikely to trigger for an unrelated skill.

3 / 3

Total

10

/

12

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
nanocoai/nanoclaw
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.