Name: guru
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

guru

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

Quality

65%

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

Quality

Content

65%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 skill is highly actionable with executable commands and a solid connection workflow, but it is held back by some explanatory padding, missing validation around destructive actions, and a large inline reference table that could be split out.

Suggestions

Add an explicit validation/confirmation step before destructive actions like delete-card and delete-folder (e.g. fetch and confirm the target exists, or require user confirmation) to lift workflow clarity.

Move the popular-actions table and proxy-flag reference into a separate references/ file and link to it, keeping SKILL.md a lean overview.

Trim the introductory Guru description and Membrane auth narrative to only what Claude needs to execute the commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary explanatory prose (the Guru intro paragraph and Membrane auth plumbing narrative) that could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste ready CLI commands for install, login, connection, action search/run, and proxying, plus a concrete table of action keys covering common cases.	5 / 5
Workflow Clarity	The connection setup is well sequenced with state validation and a poll/retry feedback loop, but destructive operations (delete-card, delete-folder) are listed without any verification step before execution, capping the score.	3 / 5
Progressive Disclosure	Content is organized into clear sections, but with no bundle files the large inline popular-actions table and proxy-flag reference table are candidates for a separate reference file rather than living entirely in SKILL.md.	3 / 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 clear and distinct, explicitly stating both what the skill does and when to use it, but it is light on concrete capability coverage and natural trigger variations.

Suggestions

Replace the generic 'Manage Organizations' with the actual entities the skill handles, e.g. 'Manage Guru cards, boards, collections, groups, and users.'

Expand the 'Use when' clause with concrete triggers users would naturally say, such as 'searching Guru cards', 'finding answers in Guru', or 'updating knowledge base content'.

Add file-format or object synonyms (e.g. 'Guru cards', 'Guru boards') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Guru integration') and one concrete action ('Manage Organizations'), but offers no comprehensive list of the actual capabilities (cards, boards, collections, groups, users) shown in the body.	3 / 5
Completeness	Provides a clear 'what' ('Guru integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Guru data.'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the relevant brand keyword 'Guru' and the phrase 'interact with Guru data', but misses common natural variations users would say such as 'Guru cards', 'search Guru', or 'knowledge base'.	3 / 5
Distinctiveness Conflict Risk	Anchored to a specific named platform (Guru) with a distinct trigger phrase, giving it a clear niche and minimal conflict risk with 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/guru/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.