Name: txt-werk
Rating: 55.2 (1 reviews)
Author: membranedev

txt-werk

TXT Werk integration. Manage data, records, and automate workflows. Use when the user wants to interact with TXT Werk 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/txt-werk/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 provides a concrete, well-sequenced Membrane CLI workflow with genuine validation feedback loops during connection setup and a useful proxy fallback. Main weaknesses are minor prose padding, a 'Popular actions' section that lists no actions, and missing output/destructive-operation validation guidance.

Suggestions

Trim padded prose (the intro paragraph, 'auth plumbing' commentary, and the cryptic overview bullets) so every line earns its place.

Populate the 'Popular actions' section with 2-3 concrete TXT Werk actions with example input/output, or remove the empty header.

Add a verification step after running actions and a validation caution for destructive proxy methods (POST/PUT/DELETE).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and an options table, but includes unnecessary prose ('so you can focus on the integration logic rather than auth plumbing', the marketing-style intro paragraph, and the cryptic 'File / Content / Session' overview bullets) that could be trimmed. It is not level 4 because several padded passages remain.	3 / 5
Actionability	Concrete, executable commands are provided throughout (install, login, connection ensure, action list/run, proxy) with a flags table, matching 'mostly executable guidance; concrete commands with minor gaps'. It is not level 5 because commands rely on unfilled placeholders and the 'Popular actions' section lists no actual actions or worked example.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with an explicit validation feedback loop (poll state, handle CLIENT_ACTION_REQUIRED, re-poll, check CONFIGURATION_ERROR/SETUP_FAILED), matching 'clear sequence with most checkpoints present'. It is not level 5 because action execution has no output verification and the proxy's destructive HTTP methods lack validation guidance.	4 / 5
Progressive Disclosure	The single ~130-line file is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no external references, which is appropriate for this scope. It is not level 5 because the 'Popular actions' header is empty and the 'TXT Werk Overview' bullets are cryptic noise.	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 has an explicit 'Use when' trigger and is anchored to a specific product, giving it reasonable completeness and distinctiveness. Its weakness is specificity: the actions listed are generic boilerplate that does not describe TXT Werk's actual text-processing capabilities.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete TXT Werk capabilities (e.g. text extraction, summarization, keyword/tag extraction, categorization).

Add natural trigger synonyms users would say, such as 'text analysis', 'summarize text', or 'extract keywords', alongside the product name.

Tighten the 'when' clause to reference specific tasks (e.g. 'Use when the user wants to analyze, summarize, or tag text via TXT Werk').

Dimension	Reasoning	Score
Specificity	The description names the TXT Werk domain but the actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor. It does not reflect TXT Werk's actual text-analysis capabilities, so it is not at level 3 which requires concrete actions.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TXT Werk data') are present, satisfying the level-4 anchor of having both. It is not level 5 because the 'what' is generic boilerplate rather than concrete capabilities with specific trigger phrases.	4 / 5
Trigger Term Quality	The product name 'TXT Werk' / 'TXT Werk data' is a usable trigger, but there are no natural synonyms or variations for what users want to do (e.g. text analysis, summarization, keyword extraction), matching the 'some relevant keywords but missing common variations' anchor. It is above level 2 because a specific natural keyword is present.	3 / 5
Distinctiveness Conflict Risk	Being tied to the named product 'TXT Werk' makes it mostly distinct with a clear trigger, but the generic 'manage data/records/automate workflows' phrasing overlaps with other Membrane app-integration skills sharing this boilerplate, 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/txt-werk/SKILL.md
Commit: f484c82

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