Name: logsnag
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

logsnag

LogSnag integration. Manage Insights, Users, Projects. Use when the user wants to interact with LogSnag data.

Quality

63%

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

Quality

Content

61%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 highly actionable with concrete, executable Membrane CLI commands and a solid connection-state feedback loop. Weaknesses are a padded marketing intro, inconsistent step numbering with a dangling "Step 2" reference, and no validation guidance for destructive proxy calls.

Suggestions

Delete the opening product-marketing paragraph ("LogSnag is a simple notification tracking tool...") and the "so you can focus on the integration logic" aside; Claude does not need this background.

Fix the step numbering: replace the dangling "Skip to Step 2" with a concrete section reference and renumber the "1b" sub-step so the workflow sequence is unambiguous.

Add a validation/verification note before destructive proxy requests (e.g., confirm the method and target before running POST/PUT/DELETE) to satisfy the destructive-operations feedback-loop expectation.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening marketing paragraph ("LogSnag is a simple notification tracking tool... used by developers, product managers, and marketers") and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed, matching the score-3 anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a full options table, matching the score-4 anchor of mostly executable guidance; minor gaps are the unsubstituted CONNECTION_ID placeholders and the absence of one fully-filled end-to-end example.	4 / 5
Workflow Clarity	The connection flow has a real validation/feedback loop (poll until state changes; branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the section numbering is inconsistent (a "1b" sub-step and a dangling "Skip to Step 2" with no labeled Step 2) and there are no validation steps for potentially destructive proxy operations (POST/PUT/DELETE), so it caps at 3.	3 / 5
Progressive Disclosure	The content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested or buried references and no bundle files present, matching the score-4 anchor of good structure with minor organization gaps; some content like the proxy options table could live in a reference file.	4 / 5
	Total	14 / 20 Passed

Description

66%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 concise, third-person, and covers both what the skill does and when to use it, anchored to a distinct product niche. Its main weakness is generic action wording ("Manage") and a single trigger phrase rather than varied natural terms.

Suggestions

Replace the generic verb "Manage" with concrete operations (e.g., "Create, list, and update Insights, Users, and Projects") to lift specificity.

Expand the "Use when" clause with more natural trigger phrases (e.g., "Use when the user mentions LogSnag, notification tracking, or wants to query Insights/Users/Projects").

Dimension	Reasoning	Score
Specificity	Names the domain ("LogSnag integration") and three concrete entities ("Insights, Users, Projects"), but the action verb "Manage" is generic rather than enumerating specific operations, matching the score-3 anchor of naming the domain with limited concrete actions.	3 / 5
Completeness	It states a clear "what" ("LogSnag integration. Manage Insights, Users, Projects.") and an explicit "when" ("Use when the user wants to interact with LogSnag data."), but the trigger clause lists only a single condition rather than multiple concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The primary natural trigger is the product name "LogSnag" (repeated in "interact with LogSnag data"); entity names like Insights/Users/Projects are data objects more than user-spoken trigger phrases, and no synonyms or variations are included, matching the score-3 anchor of some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill explicitly to the named product "LogSnag" gives it a clear niche with a distinct trigger and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	15 / 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/logsnag/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.