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

sematext

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sematext/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 solid, executable guide to driving Sematext via the Membrane CLI, with strong command coverage and a well-handled connection state machine. Its main weaknesses are minor verbosity from a redundant action-list example and a conceptual intro paragraph, plus inconsistent workflow step labeling.

Suggestions

Remove the duplicated action-list command in "Popular actions" or fold it into "Searching for actions" to avoid restating the same `membrane action list` invocation twice.

Trim the opening "Sematext is a monitoring and logging platform..." paragraph or convert it to a one-line context note, since it explains background Claude can infer.

Label the connection workflow consistently (Step 1: ensure, Step 2: wait/ready, Step 3: search and run) so the "skip to Step 2" references resolve unambiguously.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the introductory "Sematext is a monitoring and logging platform..." paragraph and the duplicated action-list command ("Searching for actions" vs "Popular actions") are padding that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxy requests with a full flag table, with only minor gaps (e.g. placeholder substitution guidance for CONNECTION_ID).	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state handling and a re-poll feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though inconsistent step labeling ("1b", "Step 2" without a labeled Step 1) is a minor gap.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections and self-contained with no external references, but at ~148 lines everything is inlined with no offloading of reference material (e.g. the proxy flag table) into bundle files.	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 states what the skill does and includes an explicit use-trigger, but its actions are generic and it leans on a single product-name keyword rather than concrete capability and trigger terms. It is competent but not exemplary.

Suggestions

Replace generic verbs with concrete Sematext capabilities, e.g. "Query logs, run synthetics checks, and inspect browser sessions".

Expand the trigger to cover natural phrasings users say: "Use when the user wants to query Sematext logs, run synthetics checks, or monitor infrastructure."

Mention key sub-products (Logs, Synthetics, Experience) in the description to sharpen distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Sematext domain but the actions are generic and abstract rather than concrete (contrast with anchors listing specific operations like "extract text", "fill forms").	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger are present, but the when-clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The single trigger phrase "Use when the user wants to interact with Sematext data" supplies the product name but misses natural variations users would say (logs, monitoring, infrastructure, query).	3 / 5
Distinctiveness Conflict Risk	The Sematext product name gives it a clear niche with low conflict risk, though the generic action verbs (manage, automate) leave minor overlap with other data-integration skills.	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/sematext/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.