CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wellally-tech

Integrate multiple digital health data sources, connect to [WellAlly.tech](https://www.wellally.tech/) knowledge base, providing data import and knowledge reference for personal health management systems.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wellally-tech/SKILL.md

The canonical home for this skill is wellally-tech in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

31%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 well-sectioned and covers the right topics, but it is severely over-inflated: ~690 lines dominated by pseudocode, decorative output templates, and duplicated trigger lists, while the actual executable artifacts it points to (import scripts, knowledge-base index files) are missing from the bundle. It reads like design documentation for a tool that was never shipped rather than operational instructions.

Suggestions

Ship the referenced files or remove the references: either provide scripts/import_apple_health.py, import_fitbit.py, import_oura.py, import_generic.py and knowledge-base/*.md in the bundle, or replace the bash/pseudocode sections with actual executable guidance (e.g., real Python or explicit file-manipulation steps using Read/Write/Glob).

Cut the padding: delete the verbatim description repeat, the decorative box-drawing output templates, the FAQ, and the 'Performance Optimization'/'Extensibility' sections — keep the trigger list, workflows, and data-source tables that carry unique signal.

Make validation concrete: replace the empty validateImportedData() comment shell with explicit rules (e.g., 'skip steps < 0 or > 100,000; reject heart rate outside 30-220 bpm; require ISO-8601 timestamps') so the checkpoint is real, and fix the '140/90' bug (evaluates to ~1.556 in JS).

DimensionReasoningScore

Conciseness

The body (~690 lines) duplicates the frontmatter description verbatim, re-lists trigger conditions already covered, includes decorative output templates with box-drawing lines and emoji, a FAQ, extensibility and performance sections, and JavaScript pseudocode that explains workflows Claude can already reason about. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') — there is real signal here, so it is above 1, but the padding is pervasive rather than minor, so it does not reach 3.

2 / 5

Actionability

The shell commands ('python scripts/import_apple_health.py ...') point to scripts that do not exist in the bundle (no scripts/ directory), and the JavaScript workflows are pseudocode built on undefined functions like identifySource(), readAppleHealthExport(), saveToLocalFile(), and findArticlesForCondition(). A few genuinely concrete pieces exist (Apple Health export steps, the mapping_config.json example), which lifts it above 1, but the executable core of the skill is non-functional as shipped, matching anchor 2 ('minimal concrete guidance; high-level hints but missing the specific steps to execute') more than 3.

2 / 5

Workflow Clarity

The four workflows (import, knowledge-base query, recommendation, data management) are sequenced with numbered steps and a Data Validation step plus error-handling guidance for file/API/validation failures, satisfying the batch-operation validation requirement and avoiding the cap-below-3 case. However, the validation step is an empty shell of comments ('// Check required fields / // Validate data types') with no actual checkpoint criteria, and the knowledge-base path ('.claude/skills/wellally-tech/knowledge-base/index.md') does not resolve. This matches anchor 3 ('steps listed but validation gaps; sequence present but checkpoints missing or implicit') rather than 4, which requires most checkpoints to be concretely present.

3 / 5

Progressive Disclosure

The skill is a monolithic single file: content that clearly belongs in separate bundle files — knowledge-base indexes and article mappings, per-platform integration guides, output templates, the data-source table — is all inlined, and the files it does reference (knowledge-base/*.md, scripts/import_*.py, integrations/, data-sources.md) do not exist in the bundle. Per the guideline to score against the actual bundle structure, this matches anchor 2 ('content that clearly belongs in separate files is inlined') — the section headers give it more structure than a 1, but broken references and heavy inlining keep it below 3.

2 / 5

Total

9

/

20

Passed

Description

50%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 communicates the domain and a rough sense of purpose but omits any usage trigger, names no concrete platforms or data types, and leans on generic verbs ('integrate', 'connect', 'provide'). It falls at the midpoint of the rubric: a clear 'what' with no 'when'.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user wants to import Apple Health, Fitbit, or Oura Ring data, or asks for WellAlly articles on sleep, nutrition, or blood pressure').

Name the supported platforms and data types in the description (Apple Health XML export, Fitbit OAuth2/CSV, Oura API v2; steps, sleep, heart rate, weight) instead of the generic 'multiple digital health data sources'.

Use third-person concrete action verbs ('Imports...', 'Recommends...') and drop the marketing-tinged 'providing knowledge reference for personal health management systems' padding.

DimensionReasoningScore

Specificity

The description names the domain ("digital health data sources", "WellAlly.tech knowledge base") and lists 2-3 actions ("integrate multiple digital health data sources", "data import", "knowledge reference"), but the actions are high-level and never name the concrete platforms (Apple Health, Fitbit, Oura) or data types covered. It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') better than anchor 4, which requires several specific actions like 'Extracts text from PDF files, fills forms, converts pages to images'.

3 / 5

Completeness

The 'what' is stated (integrate health data sources, connect to the knowledge base, provide import and reference), but there is no 'Use when...' or equivalent trigger clause anywhere in the description, so per the judging guidelines completeness is capped at 3. It is not a 2 because the 'what' is clearly stated rather than vague.

3 / 5

Trigger Term Quality

Keywords like "digital health data", "knowledge base", and "personal health management" are relevant to the domain, but the natural phrases a user would actually say ("import my Apple Health data", "sync my Fitbit", "Oura Ring", "health data CSV") are absent, as are synonyms and extensions. This sits at anchor 3 ('some relevant keywords but missing common variations or synonyms'), not 4, which requires good coverage with only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

"WellAlly.tech" is a distinctive anchor, but the surrounding language ("health data sources", "personal health management systems") is broad and would overlap with generic health/fitness-tracking skills, so it could trigger for the wrong health skill. Anchor 3 ('somewhat specific but could still overlap with similar skills') is the best fit; it lacks the clear niche triggers needed for 4.

3 / 5

Total

12

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (687 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

13

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wellally-tech/SKILL.md

Reviewed

Table of Contents

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.