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

Blog Docs Log in Get started

ritekit

Ritekit integration. Manage Hashtags, Images, Texts. Use when the user wants to interact with Ritekit 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ritekit/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 is highly actionable with executable Membrane CLI commands and a clear connection-readiness workflow, but it is padded with marketing prose and lacks a concrete end-to-end Ritekit action example. Trimming the intro and adding one real action walkthrough would lift the weakest dimensions.

Suggestions

Cut the marketing intro and filler phrases (e.g. "so you can focus on the integration logic rather than auth plumbing") to improve token efficiency.

Add one complete end-to-end example, e.g. calling the hashtag-generation action with a real --input and showing the output field, to close the actionability gap.

Normalize the step numbering (label Step 1/Step 2 explicitly) so the "skip to Step 2" and "1b" references resolve cleanly.

Dimension	Reasoning	Score
Conciseness	The marketing intro ("Ritekit is a hashtag analytics and optimization tool. It helps social media marketers...") and padding like "so you can focus on the integration logic rather than auth plumbing" explain value Claude already infers, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides many copy-paste executable commands (install, login, connection ensure, action list/run, request) but never shows a concrete Ritekit-specific action invocation with real input and output, leaving a minor gap versus fully-covered common cases.	4 / 5
Workflow Clarity	A clear sequence (install -> authenticate -> ensure connection -> poll until READY -> handle clientAction/error states -> search -> run/proxy) includes a polling feedback loop, but step numbering is loose ("1b", "skip to Step 2" with unlabeled steps), a minor gap.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no bundle files and no nested references; the ~140 lines are appropriately inline for a single-file skill, with only minor organization gaps.	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 clearly identifies a distinct product niche and provides an explicit 'Use when' trigger, but its action verbs are generic and its trigger phrasing lacks concrete synonyms. Tightening the verbs and adding concrete trigger phrases would raise specificity and completeness.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Generate hashtags, get hashtag analytics, enhance text, and fetch URL metrics".

Expand the trigger clause with concrete phrases users would say, e.g. "Use when the user wants to generate or analyze hashtags, enhance social text, or get URL metrics via Ritekit".

Reconcile the description's "Images" with the body, which covers Hashtag/Text/URL capabilities rather than images.

Dimension	Reasoning	Score
Specificity	"Manage Hashtags, Images, Texts" lists three resource areas but relies on a single generic verb ("Manage"), matching the anchor that names the domain with limited concrete actions rather than the several-specific-actions anchor above.	3 / 5
Completeness	It answers both what ("Manage Hashtags, Images, Texts") and when ("Use when the user wants to interact with Ritekit data"); the when clause is explicit but not as concrete with specific trigger phrases as the 5 anchor requires.	4 / 5
Trigger Term Quality	Concrete nouns ("Hashtags", "Images", "Texts", "Ritekit") are present, but the trigger phrase "interact with Ritekit data" is generic and misses common variations/synonyms, fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	"Ritekit" names a specific product, giving the skill a clear niche with distinct triggers and minimal overlap 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/ritekit/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.