Name: starton
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

starton

Starton integration. Manage Projects, Users, Roles. Use when the user wants to interact with Starton data.

Quality

71%

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

Quality

Content

76%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 copy-paste CLI commands and a clear connection state machine, but its workflow lacks validation before destructive blockchain operations and carries an orphaned 'Step 2' reference. Structure is clean for a single-file skill.

Suggestions

Add an explicit validation/verification step before running actions that mutate blockchain state (e.g. confirm parameters and inspect outputSchema before 'membrane action run'), since transactions are irreversible.

Fix the orphaned 'Step 2' reference — either label the 'Searching for actions' section as Step 2 or remove the dangling cross-reference.

Deduplicate the action-list command (present in both 'Searching for actions' and 'Popular actions') and trim the introductory product paragraph to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with brief context, but the introductory product paragraph and the duplicated action-list command (once in 'Searching for actions', once in 'Popular actions') are minor over-explanation that could be trimmed, fitting the 'efficient, minor instances' anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure/get with --wait, action list/run with --input, request with a full flag table), matching the 'fully executable, specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	A sequence exists (install -> auth -> connect -> poll state -> search -> run) with state-based checkpoints, but there is no validation/verification step before running actions on irreversible blockchain state, and the 'skip to Step 2' reference is orphaned with no labeled Step 2 — the destructive/batch cap holds it at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single file is well-organized with clear section headers and no nested references, so it sits at the 'good structure, most content appropriately placed' anchor rather than the under-50-line exception that would score 5.	4 / 5
	Total	16 / 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 third-person, concise, and answers both what and when with an explicit trigger clause, but relies on one generic verb and a single brand-name keyword. Expanding the action verbs and trigger synonyms would lift specificity and trigger-term quality.

Suggestions

Replace the generic 'Manage' with specific verbs, e.g. 'Create, list, update, and delete Projects, Users, and Roles'.

Add natural trigger synonyms such as 'Starton API', 'blockchain data', 'smart contracts', or 'webhooks' so users phrasing the need differently still match.

Tighten the 'when' clause to concrete scenarios, e.g. 'Use when the user wants to manage Starton projects, users, roles, wallets, or NFTs'.

Dimension	Reasoning	Score
Specificity	It names the domain (Starton) and concrete entities ('Manage Projects, Users, Roles'), but a single generic verb 'Manage' applied to three nouns is not the 'several specific actions' anchor at 4.	3 / 5
Completeness	Both 'what' ('Manage Projects, Users, Roles') and 'when' ('Use when the user wants to interact with Starton data') are present and explicit, but the 'when' clause is broad and could name concrete scenarios, landing just below the 5 anchor.	4 / 5
Trigger Term Quality	The only natural trigger is the brand 'Starton' in 'interact with Starton data'; common variations or synonyms (Starton API, blockchain data, smart contracts, webhooks) are absent, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Starton brand name plus 'interact with Starton data' carves a clear niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche, minimal conflict risk' anchor.	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/starton/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.