terra-sdk

Terra SDK integration for Python, JavaScript, iOS, Android, React Native, and Flutter. Use when implementing Terra in applications, choosing SDKs, or integrating mobile health sources.

Quality

70%

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

Quality

Content

53%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 thorough, actionable multi-SDK reference that scores well on actionability but is undermined by a monolithic single-file structure with no progressive disclosure and no validation checkpoints in its workflows.

Suggestions

Split the per-SDK method references into one-level-deep files under references/ (e.g. references/python.md, references/javascript.md) and keep SKILL.md as an overview with clearly signaled links, raising progressive_disclosure.

Add validation/verification checkpoints to the backend token-generation and mobile connection workflows (e.g. confirm token freshness before use, verify connection success before reading data) to lift workflow_clarity above 3.

Remove the repeated hard-coded dev_id/api_key credential strings from examples and reference a single placeholder pattern to reduce token waste and avoid leaking secrets.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code and tables without concept re-explanation, but it inlines ~580 lines of complete method references for six SDKs and repeats the same hard-coded dev_id/api_key strings, so a meaningful amount of bulk could be trimmed or externalized.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready code across all six platforms with installation, setup, read, and write examples, but some snippets use placeholders ('...', 'VERSION') leaving minor gaps.	4 / 5
Workflow Clarity	Each SDK follows a consistent Install -> Setup -> Read -> Write sequence, but there are no validation or verification checkpoints and no feedback loops, so the sequence is present but checkpoints are missing.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the entire per-SDK complete method reference is inlined into a single monolithic SKILL.md rather than split into one-level-deep referenced files, so content that belongs in separate files is inlined.	2 / 5
	Total	12 / 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, well-formed description that clearly states both capabilities and explicit trigger conditions in third person. Minor specificity could be gained by using more concrete action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terra SDK integration') and enumerates six concrete platforms plus three actions ('implementing Terra in applications, choosing SDKs, or integrating mobile health sources'), but the verbs are somewhat generic compared to extract/fill/merge-style concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Terra SDK integration for Python, JavaScript, iOS, Android, React Native, and Flutter') and when ('Use when implementing Terra in applications, choosing SDKs, or integrating mobile health sources') with concrete trigger phrases, in third person.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Terra', 'SDK', platform names, 'mobile health sources') with good coverage, but a few common synonyms or phrasings are missing so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Terra SDK / mobile health sources) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (583 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/terra-sdk/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.