Name: tools4ever
Rating: 55.2 (1 reviews)
Author: membranedev

tools4ever

Tools4ever integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tools4ever data.

Quality

62%

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

Quality

Content

63%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 strong, executable command guidance with a well-handled connection-state flow, but it carries minor padding, broken cross-references ("Step 2"), and makes no use of progressive disclosure despite its length. Tightening the intro and splitting detailed reference material into bundled files would lift it further.

Suggestions

Move the connection-state reference (READY/BUILDING/CLIENT_ACTION_ERROR handling) and the proxy flags table into a references/ file, linking from the body to shorten SKILL.md.

Fix the broken "skip to Step 2" / "#### 1b" references by adding explicit numbered Step 1 and Step 2 headings.

Trim the introductory concept explanation ("Think of it as a way to manage user identities...") and replace the vague "Use action names and parameters as needed" with a concrete example.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but lines like "Think of it as a way to manage user identities and permissions across different systems" and the thin "Use action names and parameters as needed" pad the doc without earning their tokens.	3 / 5
Actionability	Copy-paste-ready commands with placeholders cover the common cases (install, login, connection ensure, action list/run, request proxy) plus a flags table, with only minor gaps such as an unresolved CONNECTION_ID placeholder and a "Popular actions" section that repeats the search command instead of listing actions.	4 / 5
Workflow Clarity	A clear install-authenticate-connect-search-run sequence with explicit connection-state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) is present; minor gaps include references to a "Step 2" heading that does not exist and an unlabeled "1b" subsection.	4 / 5
Progressive Disclosure	The ~140-line skill is organized into sections but has no bundle files at all, and inline content such as the connection state machine and the proxy flags table could reasonably live in separate reference files; structure is present but references are not used.	3 / 5
	Total	14 / 20 Passed

Description

61%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 successfully pairs a what-and-when structure around a distinctive named product, but its capability phrasing is generic and its trigger terms lack natural synonyms. It is solid but could be sharpened with concrete operations and richer trigger vocabulary.

Suggestions

Replace generic verbs ("manage data, records") with concrete capabilities such as "provision user accounts, manage access rights, and review compliance reports".

Expand the trigger clause to include natural phrasings like "Use when the user asks about Tools4ever, identity governance, user provisioning, or access management."

Add a short list of the most common Tools4ever entities (User, Group, Resource) to sharpen what the skill acts on.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names several activity areas but the actions are generic ("manage data", "manage records") rather than concrete operations, fitting the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Tools4ever integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Tools4ever data.") are present, though the trigger clause could be more specific.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Tools4ever data" provides the product name as a keyword, but it omits natural variations a user might say such as identity governance, IAM, user account management, or access rights.	3 / 5
Distinctiveness Conflict Risk	The named product "Tools4ever" creates a clear niche with a distinct trigger, giving minimal conflict risk with other skills.	5 / 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/tools4ever/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.