Name: rillet
Rating: 60 (1 reviews)
Author: membranedev

rillet

Rillet integration. Manage Organizations, Pipelines, Projects, Users, Filters. Use when the user wants to interact with Rillet data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/rillet/SKILL.md

Quality

Content

68%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 content is highly actionable with executable CLI commands and a solid connection workflow, but it opens with unneeded product background and lacks verification steps for destructive record-creating actions.

Suggestions

Trim the opening marketing paragraph and explanatory asides (e.g., "so you can focus on the integration logic rather than auth plumbing") to assume Claude's competence.

Add an explicit verification step after running create/update actions (e.g., re-fetch the created record or check the `output` for an id) to satisfy the destructive-operation validation requirement.

Resolve the factual mismatch: the intro describes Rillet as social-media marketing software while the actions list accounting entities (invoices, bills, vendors) — align the overview with the real capabilities.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but opens with unnecessary background ("Rillet is a SaaS application used by businesses to manage and automate their social media marketing efforts...") and includes padded commentary like "so you can focus on the integration logic rather than auth plumbing".	3 / 5
Actionability	It provides fully executable, copy-paste-ready `membrane` commands (install, login, connection ensure/get, action list/run, request) plus a concrete popular-actions table with real keys covering common cases.	5 / 5
Workflow Clarity	The connection sequence is well-checked (state inspection, --wait polling, clientAction feedback loop), but write/destructive actions like create-invoice run with no verification step, capping workflow clarity per the destructive-operation rule.	3 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices); no bundle files exist, and the inline actions/flags tables are the only minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

71%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 answers both what and when and is anchored to a distinct named product, but its trigger vocabulary is thin and the action verb "Manage" is generic rather than enumerating concrete operations.

Suggestions

Replace the generic "Manage" with specific verbs (e.g., "Create, list, and update invoices, bills, vendors, and customers") to lift specificity toward 5.

Add natural trigger synonyms/phrases users might say (e.g., "Rillet data", "Rillet records", "accounting entities") to broaden trigger-term coverage.

Make the "Use when" clause more concrete, e.g. "Use when the user wants to query or modify Rillet accounting records such as invoices, bills, or vendors."

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Projects, Users, Filters" lists several concrete capability targets, though the single generic verb "Manage" keeps it just short of fully comprehensive action coverage.	4 / 5
Completeness	Both "what" (Rillet integration; manage the listed entities) and "when" ("Use when the user wants to interact with Rillet data") are present, with the "when" clause explicit but somewhat generic.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Rillet data" supplies the core domain keyword "Rillet" but lacks synonyms, variations, or file extensions users might naturally say.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific named product "Rillet" gives a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/rillet/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.