Name: terra
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

terra

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

Quality

68%

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/terra/SKILL.md

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 body is a well-structured, largely executable guide to driving Terra via the Membrane CLI, with a clear sequenced workflow and explicit connection-state validation. It is held back from top marks only by minor over-explanation, a command-form inconsistency, and slightly irregular step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command/table-driven with sectioned structure, containing only minor over-explanation (e.g. "so you can focus on the integration logic rather than auth plumbing" and the opening background sentence) that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and request plus a flags table, with only minor gaps such as the inconsistent `membrane` vs `npx @membranehq/cli` invocation form and placeholder substitution, placing it just below the fully-comprehensive level 5.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence has explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops (poll again after the user acts), but the numbering is slightly irregular (a "1b" with no clear "1a", an unlabeled "Step 2"), keeping it below a 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clearly headed sections; however some inlined reference detail (the proxy flags table and the clientAction field breakdown) could live in separate files, fitting 'good structure; minor organization gaps' rather than the ideal one-level-deep split of a 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 cleanly states both what the skill does and when to use it, anchored by the distinctive Terra brand. Its weakness is generic action verbs and a thin set of trigger phrases that under-serve specificity and trigger-term coverage.

Suggestions

Replace vague verbs ("Manage data, records") with concrete Terra capabilities, e.g. "query datasets, browse workspace columns, launch workflow submissions".

Add natural synonyms and format terms users actually say, e.g. "Terra workspaces, submissions, method configs, data tables".

Expand the "Use when" clause to enumerate multiple concrete triggers, e.g. "Use when the user wants to query Terra datasets, launch submissions, or manage workspace records".

Dimension	Reasoning	Score
Specificity	It names the Terra domain and a couple of actions ("Manage data, records, and automate workflows"), but "manage" is generic and the actions are not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the more specific level 4.	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Terra data") are present, but the trigger guidance is a single phrase rather than the comprehensive multi-trigger enumeration of a level 5.	4 / 5
Trigger Term Quality	Relevant keywords are present ("Terra", "data", "records", "workflows", "interact with Terra data") but it lacks synonyms, file/format variations, or common phrasings users would naturally say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Terra integration" and "interact with Terra data" carve a clear niche with low conflict risk, but the generic action verbs ("manage data/records") leave minor overlap with broad data-management skills, keeping it just below a 5.	4 / 5
	Total	14 / 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/terra/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.