Name: commcare
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

commcare

CommCare integration. Manage data, records, and automate workflows. Use when the user wants to interact with CommCare data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/commcare/SKILL.md

Quality

Content

57%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 skill is highly actionable with concrete CLI commands and a clear connection workflow, but it is weighed down by a bloated inline entity catalog, missing validation around destructive operations, and no progressive disclosure into reference files.

Suggestions

Move the ~160-item entity catalog into a separate references file (e.g. ENTITIES.md) and link to it from a short overview, keeping SKILL.md lean.

Add an explicit validation/verification checkpoint before running destructive or batch actions (e.g. 'list-cases' to confirm scope before 'update-case' or bulk export), with a fix-and-retry loop.

Trim or summarize the entity list to the categories users actually act on, removing the combinatorial 'Search/Export/Import/Schedule' repetitions that pad the body.

Dimension	Reasoning	Score
Conciseness	The CLI command sections are lean and efficient, but the ~160-line bare enumeration of entity names (lines 23-183) is substantial padding that does not earn its token cost against Claude's existing competence.	3 / 5
Actionability	It provides concrete, copy-paste bash commands for install, login, connection, action search/run, and proxying, plus a flags table and popular-actions table, with only minor placeholder gaps (CONNECTION_ID, intent string).	4 / 5
Workflow Clarity	The connect workflow has clear state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but running actions covers destructive and batch operations (update-case, create-case, bulk migration/export) with no validation or verification steps, capping the score at 3.	3 / 5
Progressive Disclosure	The body is sectioned reasonably, but no bundle files exist and the large entity-name catalog is inlined directly in SKILL.md rather than split into a one-level-deep reference file, leaving structure that could be better organized.	3 / 5
	Total	13 / 20 Passed

Description

66%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 cleanly covers what and when and is anchored to a distinct named platform, but its capability phrasing ('manage data, records, automate workflows') is generic and would benefit from more concrete, specific actions and trigger synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CommCare actions, e.g. 'List and update cases, submit forms, export data, and manage mobile workers'.

Add trigger synonyms and file/format cues users might say, e.g. 'Use when the user mentions CommCare cases, forms, mobile workers, or CommCare data exports.'

Dimension	Reasoning	Score
Specificity	Names the CommCare domain and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete, matching the anchor for naming the domain with limited concrete actions.	3 / 5
Completeness	It states both what ('CommCare integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with CommCare data'), with the 'when' explicit though it could name more concrete trigger phrases.	4 / 5
Trigger Term Quality	The primary keyword 'CommCare' and a natural trigger ('interact with CommCare data') are present, but common synonyms or variations of the trigger phrasing are missing.	3 / 5
Distinctiveness Conflict Risk	'CommCare' is a specific named platform forming a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/commcare/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.