wearables-setup

Samsung Galaxy Watch integration via Google Drive for Dr. Sophia AI. Covers Health Sync app setup, OAuth configuration, multi-user management, data sync verification. Use when setting up Samsung Health wearables, adding new users to wearables system, troubleshooting Samsung Health sync, or configuring Google Drive OAuth.

Quality

75%

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 ./skill-builder-package/examples/wearables-setup/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 body is a well-structured, actionable setup guide with concrete commands, a numbered workflow, and a verification step, but it is padded with time-sensitive status info and redundant footers, and its single external reference points to a missing file.

Suggestions

Remove time-sensitive status lines ('33,636 steps tracked as of Sept 30, 2025', '✅ Fully implemented') or move them to a deprecated/status section so they stop penalizing conciseness.

Create references/oauth-setup-guide.md (or drop the link) so the one offloaded reference is not a broken navigation path.

Add a validate-after step to the add-user workflow (e.g. re-run list-users and curl the new user's health-data endpoint) to close the workflow_clarity feedback-loop gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with lists and code blocks, but it carries time-sensitive fluff ('33,636 steps tracked as of Sept 30, 2025', '✅ Fully implemented') not placed in a deprecated section, and the footer repeats Quick Setup Overview fields (sync interval, cost, setup time), so it lands at score 3 rather than the leaner 4.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (curl endpoints, 'node multi-user-health-sync.js add-user ...', Railway env vars, file paths), with only minor gaps such as the truncated refresh token, fitting score 4 over the fully-complete score 5.	4 / 5
Workflow Clarity	The Quick Setup Steps are clearly sequenced 1-4 with an explicit verification checkpoint in step 4 ('Verify Data Sync' with expected response) and a troubleshooting section for error recovery, matching score 4; it is not 5 because user-add has no explicit validate-after feedback loop.	4 / 5
Progressive Disclosure	The body is well-sectioned and offloads OAuth detail to one clearly-signaled reference ('See references/oauth-setup-guide.md'), but that references/ directory does not exist, so the lone reference is a broken link that undermines navigation, placing it at score 3 rather than 4.	3 / 5
	Total	14 / 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.

The description is third-person, specific, and supplies a strong explicit 'Use when...' trigger clause covering several natural phrases. It clearly answers both what the skill does and when to invoke it, with a distinct niche that minimizes conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions — 'Health Sync app setup, OAuth configuration, multi-user management, data sync verification' — which is multiple specific actions with only minor coverage gaps, matching the score-4 anchor rather than the comprehensive score-5 anchor.	4 / 5
Completeness	It explicitly answers both 'what' ('Samsung Galaxy Watch integration via Google Drive... Covers Health Sync app setup, OAuth configuration, multi-user management, data sync verification') and 'when' with concrete 'Use when...' trigger phrases, matching the score-5 anchor; it is not score 4 because the when-clause is fully explicit with multiple triggers.	5 / 5
Trigger Term Quality	The 'Use when setting up Samsung Health wearables, adding new users to wearables system, troubleshooting Samsung Health sync, or configuring Google Drive OAuth' clause provides good natural keyword coverage, though a few common synonyms (e.g. 'Galaxy Watch setup') are missing, fitting score 4 over score 5.	4 / 5
Distinctiveness Conflict Risk	The combination of 'Samsung Galaxy Watch', 'Google Drive', 'Health Sync', and OAuth triggers carves a clear niche with minimal overlap risk against other skills, matching the score-5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skill-builder-package/examples/wearables-setup/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.