terra-connections

Terra API device and provider connections. Use when connecting users to wearables (Fitbit, Garmin, Apple Health, Oura, WHOOP), managing user sessions, or handling disconnections.

Quality

80%

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-connections/SKILL.md

Quality

Content

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

A highly actionable, code-rich API reference with lean prose, but it is a monolithic SKILL.md that inlines reference material better split into bundle files, and its destructive disconnect path lacks validation checkpoints. It also embeds what appear to be live API credentials, which should be removed.

Suggestions

Add a validation/feedback loop to disconnect-user (e.g., verify the user exists, confirm intent before revoking, check response.success and surface a failure message) — this lifts workflow_clarity past the destructive-operation cap of 3.

Split reference material into one-level-deep bundle files (e.g., references/providers.md for the 150+ provider list, references/operations.md for the full operation API, references/webhooks.md for event payloads) and link them from SKILL.md to improve progressive disclosure.

Remove the hardcoded dev_id and api_key from the code examples and replace with placeholders (e.g., os.environ['TERRA_DEV_ID']) — embedding real credentials in a skill is a security risk.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes Claude's competence — most tokens are executable code, provider lists, and tables that earn their place; minor trimming possible where the provider list and Provider-Specific Notes repeat info already implied by the SDK sections, so it sits above the 'mostly efficient' 3-anchor but short of fully lean.	4 / 5
Actionability	Provides copy-paste-ready, complete functions in Python plus full iOS/Android/React-Native snippets covering the common connection cases (widget, custom UI, mobile SDK, connect/disconnect/get/list), matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The widget flow lists a clear 1-5 user sequence, but destructive operations lack validation: disconnect-user revokes access and removes data yet calls deauthenticateuser and returns success with no confirm/verify/failure-handling checkpoint, so per the destructive-operation cap it cannot exceed 3.	3 / 5
Progressive Disclosure	Section headers give decent structure, but no bundle files exist and large reference material (the 150+ provider list, full operation API, webhook payloads, DB schema) is inlined in SKILL.md rather than split into one-level-deep reference files; fits the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	15 / 20 Passed

Description

87%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 description that clearly states what the skill does and when to use it, with concrete provider-name triggers and third-person voice. Minor room to broaden trigger synonyms and provider coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terra API device and provider connections') and lists several concrete actions — 'connecting users to wearables', 'managing user sessions', 'handling disconnections' — with only minor gaps (data retrieval/webhooks omitted), matching the 'lists several specific actions; minor gaps' anchor rather than the 3-anchor's 1-2 actions.	4 / 5
Completeness	Explicitly answers both 'what' ('Terra API device and provider connections') and 'when' ('Use when connecting users to wearables..., managing user sessions, or handling disconnections') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms users would say — 'wearables', 'Fitbit', 'Garmin', 'Apple Health', 'Oura', 'WHOOP', 'user sessions', 'disconnections' — giving good keyword coverage; not a 5 because it lists only 5 of 150+ providers and omits synonyms like 'fitness tracker' or 'health data'.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Terra wearable/provider connections) with distinct provider-name triggers and minimal overlap risk; the connection focus is well separated from sibling skills terra-data/terra-webhooks.	5 / 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-connections/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.