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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/terra-auth/SKILL.md

Quality

Content

65%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 with executable code for every operation, but undermined by redundant hardcoded credentials, a destructive operation lacking validation, and a single-file structure with a broken bundle reference that limits progressive disclosure.

Suggestions

Remove the triple-redundant hardcoded credentials (Quick Start, Environment Variables, and setup-environment) — load them once via the helper to cut bloat and avoid leaking real-looking keys in the skill body.

Add a validation/confirmation checkpoint before the destructive deauthenticate-user call (e.g., confirm the user_id and verify active integrations first) so the destructive-operation feedback-loop requirement is satisfied.

Create the referenced bundle file (scripts/terra_client.py) and move the bulk per-operation code into it, keeping SKILL.md an overview with one-level-deep references so progressive disclosure is real rather than a broken import.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with useful SDK-specific guidance, but the full credential set (six values) is hardcoded and repeated across Quick Start, Environment Variables, and the setup-environment operation, and Quick Start overlaps heavily with setup-environment.	3 / 5
Actionability	Provides copy-paste-ready, executable Python and cURL covering the common cases — client setup, widget sessions, mobile tokens, deauthentication, and listing integrations — with concrete response examples.	5 / 5
Workflow Clarity	Operations are documented individually but the destructive deauthenticate-user call (removes user and revokes data access) has no validation or confirmation checkpoint before execution, capping workflow clarity per the destructive-operation rule.	3 / 5
Progressive Disclosure	The body is well-sectioned but is a single 270-line file with all API reference inline, no bundle files exist, and the referenced 'scripts.terra_client' helper import points to a file that is not present in the bundle.	3 / 5
	Total	14 / 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, third-person description that concretely states capabilities and provides an explicit 'Use when' trigger clause covering the main scenarios. It is specific, actionable, and clearly scoped to Terra authentication with only minor overlap risk against related terra skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'authentication, credentials management, and environment configuration' plus 'setting up Terra integration, managing API keys, generating widget sessions, or configuring testing/staging/production environments' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (Terra API authentication, credentials management, environment configuration) and 'when' via a concrete 'Use when…' clause listing trigger scenarios.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Terra integration', 'API keys', 'widget sessions', 'credentials', 'testing/staging/production environments'), but a few natural synonyms like 'auth tokens' or 'mobile SDK' are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Terra auth/credentials/environment config) with distinct triggers, but has minor overlap risk with closely related sibling skills like terra-sdk and terra-connections.	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: 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.