Name: logdna
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

logdna

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

Quality

60%

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

Quality

Content

63%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 actionable with concrete Membrane CLI commands and a clear connection state machine, but it carries unnecessary background prose and inlines everything in one ~140-line file with no progressive disclosure to deeper references.

Suggestions

Remove the opening "LogDNA, now Mezmo, is a centralized log management platform…" paragraph and other filler Claude already knows to tighten token use.

Fix the step numbering (label the connection step "1a" to match "1b", and label the referenced "Step 2") so the workflow sequence is unambiguous.

Move the proxy flag table and connection-state details into a separate reference file and link to it, so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but opens with background Claude already knows ("LogDNA, now Mezmo, is a centralized log management platform…"), includes filler ("Use action names and parameters as needed."), and repeats the action-list command, matching anchor 3.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands with --json flags and a real input example ("--input '{\"key\": \"value\"}'"), with only minor placeholder gaps like CONNECTION_ID, fitting anchor 4.	4 / 5
Workflow Clarity	The connect→poll→state-check sequence is clear with a feedback loop (CLIENT_ACTION_REQUIRED → user acts → re-poll), but step numbering is inconsistent ("1b" with no 1a, an unlabeled "Step 2"), so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	There are no bundle files; the ~140-line skill is a single monolithic file with decent section headers but everything inline and no signaled references, matching anchor 3 rather than the reference-split anchor 4.	3 / 5
	Total	14 / 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 pairs a what-clause with an explicit Use-when trigger and ties everything to the distinct LogDNA niche. Its main weakness is generic action verbs and missing natural synonyms like "logs" and "Mezmo".

Suggestions

Replace generic verbs with concrete LogDNA actions, e.g. "Search and filter logs, create Views and Boards, and alert on log patterns."

Add natural trigger synonyms users actually say, e.g. "Use when the user wants to search LogDNA/Mezmo logs, build Views or Boards, or query log data."

Mention Mezmo (LogDNA's current name) so the skill triggers on both terms.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the LogDNA domain but the verbs are generic (manage/automate) with no concrete LogDNA-specific actions, matching anchor 2 rather than the more concrete anchor 3.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with LogDNA data") are present, though the what is somewhat vague, matching anchor 4 rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	It includes the natural term "LogDNA" plus "data/records/workflows", but misses common variations a user would actually say such as "logs", "Mezmo", or "log search", fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	"LogDNA" is a clear niche with a distinct trigger phrase, but the generic "manage data/records/workflows" tail creates minor overlap risk with other data skills, placing it at anchor 4 instead of 5.	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/logdna/SKILL.md
Commit: f484c82

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