Name: successeve
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

successeve

Successeve integration. Manage Organizations, Users. Use when the user wants to interact with Successeve data.

Quality

61%

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

Quality

Content

61%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 a concrete, executable Membrane CLI workflow with good sectioning, but it pads the intro with speculation, omits verification checkpoints around potentially destructive action/proxy calls, and does not enumerate the actual Successeve actions. It is actionable and organized but not maximally tight or validated.

Suggestions

Replace the speculative opening paragraph ('It likely provides...') with a one-line factual statement or remove it, since Claude does not need SaaS HR speculation.

Add an explicit validation checkpoint after connect (e.g., verify the connectionId appears in `membrane connection list`) and before destructive proxy/action runs, to satisfy the workflow feedback-loop requirement.

Enumerate a few concrete Successeve actions (e.g., list organizations, get/create users) inline so the common cases are covered rather than only pointing to `action list`.

Dimension	Reasoning	Score
Conciseness	The opening speculative paragraph ("It likely provides tools for goal setting... HR departments...would be the primary users.") is unnecessary padding Claude does not need, while the rest of the CLI guidance is tight, placing this at mostly-efficient-with-some-unneeded-explanation rather than the lean 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connect, action list/run, request with a flags table), but it stops short of enumerating actual Successeve domain actions and relies on placeholders, leaving minor gaps versus the fully-coverage anchor at 5.	4 / 5
Workflow Clarity	The sequence (install → login → connect → discover → run/proxy) is clearly ordered, but there are no validation or verification checkpoints, and proxy/action runs can be destructive — the missing-feedback-loop rule caps this at 3.	3 / 5
Progressive Disclosure	As a single well-sectioned file with no bundle files and no nested references it is well-organized and navigable, but the slight redundancy between 'Searching for actions' and 'Popular actions' (both point to action list) keeps it from a clean 5.	4 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly answers both what and when with a named platform and an explicit Use-when clause, but the action and keyword coverage are somewhat thin and generic. It is solid but not comprehensive.

Suggestions

Expand the what with a couple more concrete actions (e.g., '...manage Goals, Key Results, Organizations, and Users') to lift specificity and trigger coverage.

Add natural synonyms in the when clause (e.g., 'Use when the user wants to query or update Successeve employee performance data') to improve trigger-term quality.

Keep third person and avoid the generic verb 'Manage' alone — pair each entity with a sharper action verb.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users" names the Successeve domain plus two concrete entity-actions, matching the domain-plus-1-2-actions anchor; it is not comprehensive enough for a 4 and more concrete than the single-generic-action anchor at 2.	3 / 5
Completeness	It states a concrete what ("Successeve integration. Manage Organizations, Users.") and an explicit when ("Use when the user wants to interact with Successeve data."), matching the both-what-and-when anchor; it falls short of 5 because the trigger phrase is singular and not comprehensive.	4 / 5
Trigger Term Quality	Relevant keywords appear ("Successeve", "Organizations", "Users", "interact with Successeve data") but the set is limited with no synonyms or variations, fitting the some-relevant-keywords anchor rather than the good-coverage anchor at 4.	3 / 5
Distinctiveness Conflict Risk	The "Successeve" proper noun gives it a mostly-distinct niche with only minor overlap risk against other HR/SaaS integrations, while the generic "Manage Organizations, Users" action language keeps it from a clean minimal-conflict 5.	4 / 5
	Total	14 / 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/successeve/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.