Name: slite
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

slite

Slite integration. Manage Documents. Use when the user wants to interact with Slite data.

Quality

66%

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/slite/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 body delivers concrete, executable CLI guidance with a clear connection-state workflow and good section organization. It is held back by a padded intro paragraph and inconsistent step numbering that slightly undermine conciseness and workflow clarity.

Suggestions

Cut the marketing-style intro paragraph ('Slite is a collaborative knowledge base...') and the filler line 'Use action names and parameters as needed.' to improve token efficiency.

Make step numbering consistent: define explicit 'Step 1', 'Step 2' labels so the 'skip to Step 2' references resolve unambiguously.

Add one concrete Slite-specific action example (e.g., a real action list/run invocation) to move actionability from mostly-executable to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ('Slite is a collaborative knowledge base...centralize knowledge and improve internal communication') and the filler line 'Use action names and parameters as needed' are unnecessary explanation, making it mostly efficient but in need of tightening rather than the lean score-4 or score-5 anchors.	3 / 5
Actionability	Concrete executable commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flag table, but generic placeholders like CONNECTION_ID/actionId and absent Slite-specific action examples leave minor gaps versus the fully copy-paste-ready score-5 anchor.	4 / 5
Workflow Clarity	The setup sequence (install -> authenticate -> connect -> discover -> run) is clearly ordered with explicit state-polling feedback loops (handle READY/CLIENT_ACTION_REQUIRED, re-poll after action), fitting the score-4 anchor; it stops short of score 5 due to inconsistent step labels ('Step 2' referenced without a clear definition).	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections (Overview, Working with Slite, Install, Auth, Connecting, Searching, Popular actions, Best practices) with no external references needed for a CLI skill, matching the good-structure score-4 anchor rather than the one-level-deep-references score-5 anchor.	4 / 5
	Total	15 / 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 has an explicit 'Use when' trigger and names the distinct Slite niche, but its capability and trigger vocabulary are thin and generic. Tightening 'Manage Documents' into several concrete actions and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace the broad 'Manage Documents' with 2-3 concrete actions (e.g., 'Create, search, and update Slite documents').

Expand the trigger clause with natural phrasings users would actually say, e.g., 'Use when the user mentions Slite, wants to search or edit Slite docs, or share team knowledge.'

Add concrete trigger nouns/synonyms (Slite docs, Slite notes, team knowledge base) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage Documents' and 'interact with Slite data' name the domain with one broad concrete action, but coverage is not comprehensive and the second verb is generic, fitting the score-3 anchor better than score 2 (which requires minimal/generic actions) or score 4 (which requires several specific actions).	3 / 5
Completeness	'Slite integration. Manage Documents.' states the what and 'Use when the user wants to interact with Slite data.' provides an explicit when clause, but the when is somewhat generic so it is not the fully concrete trigger-phrasing of score 5.	4 / 5
Trigger Term Quality	'Slite', 'Documents', and 'Slite data' provide some relevant keywords a user would say, but common variations, synonyms, and concrete trigger phrases are missing, matching the score-3 anchor rather than the comprehensive coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	'Slite' is a uniquely named product and the triggers 'interact with Slite data' / 'Slite integration' pin it to a clear niche with minimal conflict risk against other skills.	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/slite/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.