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

75%

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

Quality

Content

76%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 content is highly actionable with executable multi-language code and clear connection-method sequences, well-organized for a self-contained skill. Its main weakness is missing validation/verification around the destructive disconnect operation, which caps workflow clarity.

Suggestions

Add an explicit verification step to the disconnect-user workflow (e.g., call get_user_info afterward to confirm the user is no longer connected) so the destructive operation has a validation checkpoint.

Treat the connection_error webhook as a feedback loop: document a retry/escalation path (e.g., re-authenticate the user) rather than only showing the payload.

Consider moving the provider catalog, webhook payload examples, and DB schema into separate reference files under references/ to slim the main body and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean, code-first body with no padding about what OAuth/wearables/CGM are; minor over-length from the inlined provider catalog and DB schema keeps it just below the fully lean anchor 5.	4 / 5
Actionability	Fully executable copy-paste code in Python, Swift, Kotlin, and JS plus concrete function definitions (connect_user, disconnect_user, get_user_info) covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Clear numbered sequences exist for each connection method, but the destructive disconnect-user operation ('revokes access, removes data') has no validation/verification checkpoint, so workflow_clarity is capped at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist; the body is self-contained with clear section headers and a Related Skills pointer list, matching anchor 4; some inlined content (provider catalog, DB schema, webhook payloads) could be split into reference files, so below a 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is specific, well-triggered, and answers both what and when with concrete wearable-provider names. It is a strong, mostly-distinct description that would reliably activate for the right user requests.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terra API device and provider connections') and several concrete actions ('connecting users to wearables', 'managing user sessions', 'handling disconnections'), matching anchor 4; not the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicit 'what' (Terra API device and provider connections) and explicit 'when' (Use when connecting users to wearables..., managing user sessions, or handling disconnections) are both present and concrete; the 'when' is a solid action list but not the maximally explicit trigger phrasing of a 5.	4 / 5
Trigger Term Quality	Strong natural keyword coverage with named wearables users actually say ('Fitbit', 'Garmin', 'Apple Health', 'Oura', 'WHOOP') plus action phrases; a few synonyms/extensions (e.g., 'health data', 'connect devices') are missing, so below a 5.	4 / 5
Distinctiveness Conflict Risk	'Terra API' plus named wearables forms a clear, distinct niche with low conflict risk; minor overlap risk with closely related sibling skills (terra-auth, terra-sdk) keeps it just below a clean 5.	4 / 5
	Total	16 / 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-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.