terra-troubleshooting

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

Quality

82%

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

Quality

Content

82%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, well-structured troubleshooting reference with executable examples spanning multiple languages and clear per-issue checklists. The main gaps are a duplicated health-check section and the absence of any file-level progressive disclosure for the longer reference material.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean cause->solution->code with little concept padding, but the standalone 'Health Check Script' largely duplicates the 'Quick Diagnostics' block and could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready executable code across Python, JavaScript, Swift, Kotlin, and bash covering the common issue cases, with only minor thin spots such as the comment-only Garmin section.	5 / 5
Workflow Clarity	Per-issue sequences are clear with numbered checklists and validation loops (signature debug-and-compare, retry-with-backoff), though the top-level diagnostic routing is implicit rather than an explicit decision tree.	4 / 5
Progressive Disclosure	Section hierarchy is well organized with no nested or dead references, but ~500 lines are fully inline; reference material like the historical-limits table, IP list, and per-SDK code could be split into separate files.	4 / 5
	Total	17 / 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.

A strong description that clearly pairs a 'what' with an explicit, multi-trigger 'when' clause tied to a specific named API. Its main weakness is the generic action verbs, which keep specificity below the top anchor.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Diagnose Terra API connection, webhook, and data-sync failures; verify webhook signatures; retry flaky providers.'

Add 1-2 natural synonyms a user might say (e.g. 'webhooks not firing', 'data not syncing') to push trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain (Terra API) and two actions ('troubleshooting and debugging'), but both are generic verbs rather than concrete operations like verifying signatures or retrying failed requests.	3 / 5
Completeness	It explicitly states what the skill does ('Terra API troubleshooting and debugging') and when to use it, with a concrete multi-trigger 'Use when...' clause that exceeds the specificity of the anchor-4 example.	5 / 5
Trigger Term Quality	The 'Use when' clause lists natural terms across five categories ('connection issues, data sync problems, webhook failures, SDK errors, provider-specific issues'); a few synonyms are missing but coverage is good.	4 / 5
Distinctiveness Conflict Risk	The named Terra API niche plus distinct issue-type triggers make conflict with other skills unlikely; voice is appropriately third-person with no first/second-person penalty.	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: .claude/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.