terra-auth

Terra API authentication, credentials management, and environment configuration. Use when setting up Terra integration, managing API keys, generating widget sessions, or configuring testing/staging/production environments.

Quality

73%

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 ./.claude/skills/terra-auth/SKILL.md

Quality

Content

57%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 body is actionable and well-structured with concrete code for each operation, but suffers from redundant/conflicting credential examples, missing validation checkpoints for destructive operations, and dangling references to non-existent bundle files.

Suggestions

Reconcile the two credential-loading approaches (env-file .env.terra.<env> vs. TERRA_DEV_ID_<ENV> env vars) into one canonical pattern to remove the contradiction and duplicate env-var blocks.

Add an explicit validation/verification checkpoint to destructive operations (e.g., confirm a connection check before deauthenticate-user, and verify deauth succeeded beyond a boolean return).

Create the referenced scripts/terra_client (or remove the reference) and move stable reference material (API base URLs, session-lifecycle table) into references/ files with one-level-deep links from the body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but redundancy pads it: two conflicting get_terra_client implementations (env-file vs. TERRA_DEV_ID_TESTING env vars) and duplicated env-var blocks (.env.terra.testing table vs. .env.testing vars) that could be tightened.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready Python functions with usage examples for each operation plus a cURL example; minor gaps come from the conflicting credential-loading patterns.	4 / 5
Workflow Clarity	Operations are documented individually but not sequenced into a setup flow, and the destructive deauthenticate-user operation has no validation/verification step; per rubric guidance, missing validation for destructive ops caps this at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and links to related skills, but references are dangling (scripts/terra_client is cited yet scripts/ and references/ directories do not exist), and referenceable content like API base URLs and session-lifecycle tables is inlined rather than split out.	3 / 5
	Total	13 / 20 Passed

Description

88%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, specific description that clearly states capabilities and provides an explicit trigger clause. It is concise, third-person, and avoids vague fluff, with only minor room to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'authentication, credentials management, and environment configuration' and 'managing API keys, generating widget sessions, or configuring testing/staging/production environments' — giving comprehensive coverage of the niche.	5 / 5
Completeness	Explicitly answers both 'what' (Terra API authentication, credentials, environment config) and 'when' via a concrete 'Use when setting up Terra integration, managing API keys, generating widget sessions...' trigger clause.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('API keys', 'widget sessions', 'Terra integration', 'testing/staging/production environments'); a few synonyms or extension-style variants are missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct Terra-auth niche with specific triggers and minimal overlap risk; the related terra-* skills are named in the body, leaving only minor overlap with those siblings.	4 / 5
	Total	18 / 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: fernandezbaptiste/Skrillz
Path: .claude/skills/terra-auth/SKILL.md
Commit: 93ed392

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.