Name: logit-io
Rating: 47.2 (1 reviews)
Author: membranedev

logit-io

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

Quality

50%

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

Quality

Content

38%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 CLI usage guidance is genuinely actionable, but it is buried under a massive, truncated entity-enum that consumes nearly the entire token budget for no navigational value. Structure is minimal and there is no progressive disclosure via reference files.

Suggestions

Delete the ~850-line entity enumeration (or move it to a references/ENTITY_CATALOG.md with a one-line pointer); it is padding and is even truncated mid-document.

Add explicit validation checkpoints before running actions or proxy requests, e.g. verify `state: READY` before `action run` and confirm pagination/error responses before treating output as complete.

Split the guide into a concise SKILL.md overview (connect -> search -> run) and reference files for the proxy flag table and clientAction handling, with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body opens with ~850 bullet-list entries enumerating every conceivable Logit.io entity, with roughly 600 of them being repetitive 'Security Finding Remediation Task X' word-salad (e.g. 'Security Finding Remediation Task FAQ', '...Task Wireframe'); this is severe padding that Claude does not need and the list is even truncated mid-line, matching the score-1 'Severely verbose; heavily padded' anchor.	1 / 5
Actionability	The Membrane CLI sections give concrete, copy-paste-ready commands (`npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://logit.io/" --json`, `membrane action run <actionId> ...`) with parameters and flags explained, matching 'Mostly executable guidance; concrete code with minor gaps'.	4 / 5
Workflow Clarity	There is a rough sequence (install -> login -> connection ensure -> wait/poll -> search actions -> run), and the connection-state branching (READY/CLIENT_ACTION_REQUIRED) is explained, but there are no explicit validation checkpoints before destructive/batch action runs and the feedback loop on CONFIGURATION_ERROR is only loosely described ('Check the error field'); the destructive/batch cap and missing checkpoints hold this at 3.	3 / 5
Progressive Disclosure	The file is a near-monolithic wall of text with the giant inlined entity enumeration that clearly belongs in a separate reference file, no bundle files exist, and there are no signaled one-level-deep references, matching the score-2 anchor 'content that clearly belongs in separate files is inlined'.	2 / 5
	Total	10 / 20 Passed

Description

62%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 gives a clear third-person statement of what the skill does and when to use it, anchored to a specific platform. It is weakened by vague action verbs ('Manage data') and limited natural trigger-term coverage.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Search logs, manage saved objects and alerts, run Logit.io API actions'.

Expand the 'Use when...' clause with natural phrasing users would say, e.g. 'Use when the user mentions Logit.io logs, observability, dashboards, or alerts'.

Avoid the catch-all 'Manage data, records' which overlaps with broad data-management skills.

Dimension	Reasoning	Score
Specificity	It names the domain ("Logit.io integration") and a few generic actions ("Manage data, records, and automate workflows") but the actions are abstract ("Manage data") rather than concrete, mirroring the score-3 anchor 'Processes PDF files and extracts content'.	3 / 5
Completeness	It states both the 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Logit.io data"), so it has both; the trigger could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The phrase "interact with Logit.io data" gives one relevant natural term ("Logit.io") but misses common variations, synonyms, or file extensions, matching the 'Some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming Logit.io pins it to a specific platform with distinct triggers, giving mostly-distinct usage with only minor overlap risk against generic data-management skills; it is not as comprehensively scoped as the score-5 example.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1003 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/logit-io/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.