Name: terminus-app
Rating: 61.6 (1 reviews)
Author: membranedev

terminus-app

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

Quality

72%

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

Quality

Content

82%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 strong, executable guide: concrete Membrane CLI commands, a clear connection-readiness state machine with a feedback loop, and a useful proxy table. Its main weaknesses are a dangling 'Step 2' reference and a small amount of trimmable prose.

Suggestions

Define or remove the undefined 'Step 2' anchor so the connection workflow does not reference a missing section.

Trim atmospheric prose ('Think of it as Git for data', 'focus on the integration logic rather than auth plumbing') to tighten token use.

Consider moving the clientAction field reference and the proxy flag table into reference files and linking to them for a leaner SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, leaning on executable commands and a flag table with only minor over-explanation ('Think of it as Git for data', 'so you can focus on the integration logic rather than auth plumbing'); it fits anchor 4 (efficient, minor trimmable instances) and not 5 because a few prose asides do not fully earn their tokens.	4 / 5
Actionability	Commands are copy-paste ready and cover the common cases end to end ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run ... --input', the proxy flag table); it matches anchor 5 (fully executable, specific examples cover common cases) rather than 4 since there are no real gaps.	5 / 5
Workflow Clarity	The connect-to-ready flow is a clear sequence with an explicit state machine and a poll-again feedback loop (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the dangling 'skip to Step 2' reference points to a Step 2 that is never defined, a minor gap that caps it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained file with clear section headers and easy navigation, fitting anchor 4 (good structure, well-placed content); it does not reach 5 because some inline material (the clientAction field reference and the proxy flag table) could be split into reference files to keep SKILL.md leaner.	4 / 5
	Total	17 / 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 is competent: it names a specific product, states capabilities, and includes an explicit 'Use when' trigger. It is held back by generic action verbs and thin trigger-term coverage that lacks synonyms or natural variations.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query and update knowledge graphs, manage records, and run GraphQL/WOQL queries'.

Broaden trigger terms with natural phrases users say, e.g. 'Use when the user mentions Terminus, knowledge graphs, WOQL/GraphQL queries, or Terminus App data'.

Tie the 'when' clause to specific nouns users actually name rather than the generic 'interact with Terminus App data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Terminus App integration') and lists actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations; it sits at anchor 3 (names domain + 1-2 actions, not comprehensive) and not 4 because the actions lack specific concrete coverage.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Terminus App data'); matching anchor 4, it does not reach 5 because the 'when' clause is generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Terminus App data' provides a relevant trigger ('Terminus App data') but misses common synonyms and natural variations users might say; it fits anchor 3 (some relevant keywords, missing variations) rather than 4 which requires broader keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The named-product trigger ('Terminus App data') gives it a clear niche with low conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing creates minor overlap risk with other data skills, fitting anchor 4 rather than 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/terminus-app/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.