Name: tettra
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

tettra

Tettra integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tettra 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tettra/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 content is a well-structured, actionable guide with executable commands, a clear multi-step connection workflow, and state-based checkpoints. Weaknesses are minor over-explanation and no explicit post-action validation step.

Suggestions

Trim conversational prose like 'so you can focus on the integration logic rather than auth plumbing' to keep the guide lean.

Add a brief validation/confirm step after `membrane action run` (e.g. inspect the `output` field and verify the expected Tettra entity was created) for write operations.

Consider moving the clientAction state enum and proxy flag reference table into a separate reference file to keep SKILL.md a focused overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and a flag table, but includes unnecessary prose such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection...' that could be trimmed, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete, runnable commands appear throughout (install, login, connection ensure/wait, action list/run, request proxy) with a flag reference table and JSON input/output examples, but placeholders like CONNECTION_ID and the lack of concrete response-parsing examples leave minor gaps versus fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	The install → login → ensure connection → poll for READY → search → run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop; the gap is the absence of an explicit verify/confirm step after running an action, matching 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	A single self-contained SKILL.md with well-organized sections (Overview, Working with Tettra, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references; the inline clientAction enum and proxy flag table are borderline material that could live in a reference, keeping it just below the 'ideally split' 5.	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 names the target app and includes an explicit 'Use when' trigger, satisfying the what/when structure. Its main weakness is generic action language ('Manage data, records') that lacks Tettra-specific verbs and natural user synonyms.

Suggestions

Replace generic verbs with Tettra-specific actions, e.g. 'Search the Tettra wiki, create and edit pages, manage categories and assignments.'

Add natural trigger phrases users would say, such as 'wiki', 'knowledge base', 'search Tettra', or 'Tettra pages'.

Tie the 'Use when' clause to concrete intents like 'Use when the user wants to search or update their Tettra knowledge base.'

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Tettra domain plus a few action verbs, but the actions are generic ('Manage data, records') with no Tettra-specific operations like creating pages or searching the wiki; closer to the 'names domain but actions minimal/generic' anchor than the comprehensive one.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Tettra data') are present; the trigger is explicit but generic rather than tied to concrete Tettra use-cases, so it sits at 'both present, when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	'Tettra' and 'interact with Tettra data' provide some relevant keywords, but common natural synonyms a user would say ('wiki', 'knowledge base', 'pages', 'search Tettra') are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app Tettra gives a clear niche with minimal conflict risk; the generic 'Manage data, records' verbs add only minor overlap risk with other data-integration skills, matching 'mostly distinct; minor overlap risk'.	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/tettra/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.