terra-troubleshooting

Terra API troubleshooting and debugging. Use when experiencing connection issues, data sync problems, webhook failures, SDK errors, or provider-specific issues.

Quality

73%

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

Quality

Content

63%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 a highly actionable troubleshooting catalog with executable, multi-language code and a clear Cause/Solution structure. Its main weaknesses are length/redundancy and a lack of progressive disclosure — everything is inlined in SKILL.md rather than split into reference files.

Suggestions

Move large reference material (provider-specific issues, per-platform SDK fixes, the standalone health-check script) into files under references/ and link to them from SKILL.md to reduce the inline token footprint.

De-duplicate the credential blocks and the health-check script, which appears both in 'Quick Diagnostics' and again as the full 'Health Check Script'.

Add an explicit validation/verify step to the webhook signature and UPSERT workflows (e.g., 'confirm signature passes before parsing JSON; confirm no duplicate rows after upsert') to strengthen feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, actionable code with minimal prose padding, but ~500 lines includes redundancy such as the duplicated health-check script and repeated credential blocks that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready code across Python, JavaScript, Swift, Kotlin, and bash covering common cases (signature verification, retry/backoff, UPSERT), with minor gaps like the Garmin section that offers only comment hints.	4 / 5
Workflow Clarity	Consistent Cause/Solution structure with numbered checklists (e.g., the webhook 'Checklist' and signature debug flow) gives a clear sequence; no destructive/batch validation gap significant enough to cap the score.	4 / 5
Progressive Disclosure	Section headings are well-organized and navigable, but the skill is a monolithic ~500-line file with no bundle-file references; provider-specific and SDK content that could live in separate reference files is inlined.	3 / 5
	Total	14 / 20 Passed

Description

82%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 well-structured with an explicit 'Use when' clause and concrete, Terra-specific trigger phrases that make it highly distinct. Its only weakness is that the stated actions ('troubleshooting and debugging') are generic verbs, even though the enumerated issue categories add specificity.

Suggestions

Replace the generic verbs 'troubleshooting and debugging' with concrete actions (e.g., 'Diagnose, reproduce, and resolve Terra API connection, sync, webhook, and SDK errors').

Add a few common synonyms users might say (e.g., 'data not syncing', 'webhooks not firing') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Terra API") and enumerates concrete issue categories ("connection issues, data sync problems, webhook failures, SDK errors, or provider-specific issues"), but the action verbs "troubleshooting and debugging" are generic rather than a comprehensive list of concrete actions.	3 / 5
Completeness	Explicitly answers both what ("Terra API troubleshooting and debugging") and when ("Use when experiencing connection issues, data sync problems, webhook failures, SDK errors, or provider-specific issues") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Phrases like "connection issues", "data sync problems", "webhook failures", "SDK errors", and "provider-specific issues" are natural terms users would say; good coverage with a few common synonyms missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to the Terra API niche with provider/SDK-specific triggers, making it clearly distinguishable from generic debugging skills with minimal conflict risk.	5 / 5
	Total	17 / 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 (508 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

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