Name: google-cloud-healthcare-api
Rating: 55.2 (1 reviews)
Author: membranedev

google-cloud-healthcare-api

Google Cloud Healthcare API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Cloud Healthcare API data.

Quality

62%

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/google-cloud-healthcare-api/SKILL.md

Quality

Content

67%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 strongly actionable with executable Membrane CLI commands, a useful flags table, and a sequenced connection workflow that includes state-polling feedback loops. The main weakness is an unnecessary introductory paragraph that explains the Healthcare API and its audience rather than instructing Claude.

Suggestions

Delete or condense the opening overview paragraph ('The Google Cloud Healthcare API allows developers to build healthcare solutions ...') since it explains a concept Claude already knows.

Label the post-connection section as 'Step 2' (or remove the 'Skip to Step 2' reference) so the workflow's cross-references resolve.

Consider moving the clientAction field breakdown and the proxy flags table into a short REFERENCE.md so SKILL.md stays a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ('The Google Cloud Healthcare API allows developers to build healthcare solutions ... Healthcare providers, researchers, and technology companies use it ...') explains what the API is and who uses it — concept/marketing padding Claude does not need — pushing it to anchor 3 rather than 4.	3 / 5
Actionability	It provides copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus a flags table, matching anchor 4; it is not 5 because placeholders like CONNECTION_ID and generic intent=QUERY leave minor gaps.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll sequence includes a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR states), matching anchor 4; it is not 5 because 'Skip to Step 2' references an unlabeled target and some checkpoints are implicit.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no bundle files present and no external references needed for this single-purpose CLI skill, matching anchor 4; it is not 5 because inline reference-like detail (the clientAction field breakdown and flags table) is fairly long and could be split into a reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when' trigger and names a distinct, specific API niche, but its capability language is generic ('manage data, records, automate workflows') and it omits natural domain synonyms like FHIR or DICOM. Specificity and trigger coverage are the weakest areas.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create and query FHIR stores, ingest HL7v2 messages, and retrieve DICOM studies' instead of 'Manage data, records, and automate workflows'.

Add natural trigger synonyms so users saying 'FHIR', 'DICOM', 'HL7v2', or 'healthcare data' match the skill.

Tighten the 'when' clause to reference concrete tasks (e.g. 'Use when the user wants to query FHIR resources, read DICOM imaging studies, or ingest HL7v2 messages').

Dimension	Reasoning	Score
Specificity	It names the domain ('Google Cloud Healthcare API integration') but the actions are minimal and generic — 'Manage data, records, and automate workflows' uses vague verbs with no concrete operations, matching the anchor 2 example 'Processes PDF files'.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Google Cloud Healthcare API data'), matching anchor 4; it is not 5 because the 'what' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The phrase 'Google Cloud Healthcare API' is a relevant keyword a user might say, but it lacks natural variations and synonyms like FHIR, DICOM, or HL7v2, so it sits at anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The named API carves a clear niche with low conflict risk, but the trigger phrasing ('interact with ... data') is generic, so it lands at anchor 4 ('mostly distinct; minor overlap risk') rather than 5.	4 / 5
	Total	13 / 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/google-cloud-healthcare-api/SKILL.md
Commit: f484c82

Reviewed: 5 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.