Name: new-sloth
Rating: 48.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

new-sloth

New Sloth integration. Manage Organizations. Use when the user wants to interact with New Sloth data.

Quality

53%

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

Quality

Content

56%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 delivers strong executable CLI guidance and a clear connection workflow, but is undermined by AI-refusal filler in the opening and thin overview content. Removing the filler and tightening the overview would notably improve token efficiency and structure.

Suggestions

Delete the two opening filler paragraphs ('I don't have enough information...', 'I am sorry, but I cannot provide an API...') — they are pure anti-content that wastes context.

Fix the dangling references to a non-existent 'Step 2' (e.g. 'skip to Step 2') by relabeling sections or removing the pointers.

Expand the thin 'New Sloth Overview' with concrete action names per entity rather than the placeholder line 'Use action names and parameters as needed'.

Dimension	Reasoning	Score
Conciseness	The opening paragraphs ("I don't have enough information about New Sloth...", "I am sorry, but I cannot provide an API...") are filler that wastes tokens, and "Use action names and parameters as needed" is vague padding, pulling this below anchor 3 despite the efficient command sections.	2 / 5
Actionability	It provides concrete, copy-paste-ready `membrane` commands with flags and JSON output, plus a proxy options table, with only minor gaps (unfilled CONNECTION_ID placeholders).	4 / 5
Workflow Clarity	The connection flow is well sequenced (ensure -> poll state -> handle CLIENT_ACTION_REQUIRED -> search -> run) with an explicit re-poll feedback loop, though dead references like 'skip to Step 2' are minor gaps keeping it below 5.	4 / 5
Progressive Disclosure	It is a single well-sectioned file with no nested references, but the proxy options table and state-handling detail could live in separate files, and the 'New Sloth Overview' entity list is thin with minor organization gaps (dangling 'Step 2').	3 / 5
	Total	13 / 20 Passed

Description

50%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' clause and is anchored to a named app, which supports completeness and distinctiveness, but its actions and trigger phrasing are vague and generic. Tightening the verbs and adding natural user keywords would raise it.

Suggestions

Replace the generic verb 'Manage Organizations' with concrete actions a user would perform (e.g. 'list, create, and update Organizations and Notes').

Add natural trigger keywords users would actually say (e.g. 'Use when the user asks about New Sloth Organizations, Notes, Notebooks, Tags, or Workspace data').

Specify the file/entity extensions or object names (Notes, Notebooks, Workspaces) to improve keyword coverage and specificity.

Dimension	Reasoning	Score
Specificity	"New Sloth integration. Manage Organizations." names the domain but the only action ("Manage Organizations") is minimal and generic, matching anchor 2; it does not list concrete actions so it is not a 3.	2 / 5
Completeness	It states both a 'what' (New Sloth integration / Manage Organizations) and an explicit 'when' clause, but neither is concrete enough for anchor 5's specific trigger phrases.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with New Sloth data" relies on the proper noun and abstract phrasing rather than natural user keywords, and lacks synonyms; this sits noticeably below the midpoint (anchor 2).	2 / 5
Distinctiveness Conflict Risk	Binding to the named app 'New Sloth' gives it a clear niche with minimal conflict risk, though 'Manage Organizations' is generic enough to keep it just below anchor 5.	4 / 5
	Total	12 / 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/new-sloth/SKILL.md
Commit: f484c82

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