CtrlK
BlogDocsLog inGet started
Tessl Logo

nhost

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

59

Quality

68%

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 ./skills/nhost/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is an efficient, actionable guide to driving Nhost through the Membrane CLI, with a well-sequenced connection workflow and real validation checkpoints. Minor tightening, consistent step numbering, and a slightly less thin Popular actions section would push it to excellent.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and lean, with only minor over-explanation (the opening "open-source Firebase alternative" paragraph and a few "so you can focus on integration logic" asides) that could be trimmed, fitting the efficient-with-minor-padding anchor.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands (membrane login, connection ensure, action list/run, request) with a clear options table, but relies on placeholders like CONNECTION_ID and the Popular actions section mostly repeats the list command, leaving minor gaps.

4 / 5

Workflow Clarity

There is a clear install → authenticate → connect → wait-for-ready → search → run sequence with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the step numbering is inconsistent ("skip to Step 2" and "1b" without a labeled Step 1/2), a minor clarity gap.

4 / 5

Progressive Disclosure

As a single self-contained SKILL.md with no bundle files, it is organized into clear headed sections (Overview, Authentication, Connecting, Actions, Proxy, Best practices) with no nested references; structure is good though slightly long for one file, so 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

62%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 pairs a what and a when clause tied to a distinct product, but its action vocabulary is generic and trigger coverage is limited to the single term "Nhost". Tightening the actions and adding concrete Nhost feature terms would lift it from adequate to strong.

Suggestions

Replace generic verbs with concrete Nhost capabilities, e.g. "Query and mutate data via GraphQL, manage auth users, and upload storage files."

Expand the trigger clause to include natural feature terms users say: "Use when the user wants to interact with Nhost data, auth, storage, or GraphQL API."

Drop the filler opener "Nhost integration." since the actions already imply it, making the description leaner and more specific.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Nhost domain and several actions, but the verbs are generic ("manage", "automate") rather than concrete, matching the anchor for 1-2 concrete-but-not-comprehensive actions.

3 / 5

Completeness

It explicitly answers what ("Nhost integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Nhost data"), but the what is generic and the when could be more specific about Nhost features, so it sits at 4 rather than 5.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Nhost data" surfaces the core keyword "Nhost", but misses natural variations a user might say (GraphQL, Hasura, auth, storage), fitting the "some relevant keywords, missing common variations" anchor.

3 / 5

Distinctiveness Conflict Risk

The Nhost product name and Nhost-specific trigger make it largely distinct, but the generic "manage data / automate workflows" framing leaves minor overlap risk with other backend-as-a-service skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.