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

toolset

Toolset integration. Manage data, records, and automate workflows. Use when the user wants to interact with Toolset 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/toolset/SKILL.md

Quality

Content

75%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 well-structured and highly actionable, anchored by concrete CLI commands and a clear state-driven connection workflow with feedback loops. Minor tightening of padding and a fully-worked example would push it to the top level.

Dimension	Reasoning	Score
Conciseness	The body is dominated by tight, executable CLI commands and a flag table with only minor padding ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens'), matching the 'efficient; minor instances of over-explanation' anchor rather than the lean 5-anchor.	4 / 5
Actionability	It provides many concrete, executable commands (connection ensure, action list/run, request with a full flag table), but they rely on templated placeholders (<actionId>, CONNECTION_ID, QUERY) and lack a fully-realized end-to-end worked example, fitting 'mostly executable; minor gaps' rather than the copy-paste-complete 5-anchor.	4 / 5
Workflow Clarity	The connection flow has explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, but the overall sequence is fragmented (references an unlabeled 'Step 2', a '1b' with no '1a'), matching 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is well-organized into clear single-file sections with the only reference being a one-level-deep external docs link, but at ~140 lines the under-50-line 5-exception does not apply and the 'Popular actions' and 'Searching for actions' sections are mildly redundant, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

57%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 the skill does and when to use it with a named-product trigger, but its capability phrasing is generic and its trigger coverage is narrow. Tightening the action list and broadening the 'when' clause would lift it from adequate to strong.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with 2-3 concrete Toolset capabilities (e.g., 'Create and manage custom post types, fields, and content templates in WordPress').

Broaden the 'Use when' trigger to enumerate natural user phrases, e.g., 'Use when the user wants to manage Toolset custom fields, post types, views, or WordPress dynamic content.'

Add Toolset-specific trigger terms users actually say (e.g., 'Toolset post types', 'Toolset fields', 'Toolset views') to improve natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the Toolset domain and lists actions ('Manage data, records, and automate workflows'), but these verbs are generic abstractions rather than concrete capabilities, matching the anchor for 'actions are minimal or generic' rather than the concrete-action anchor at 3.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Toolset data') are present, but the 'when' clause is narrow and the 'what' is generic, so it sits at 'both present; when could be more explicit' rather than the comprehensive 5-anchor.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ('Toolset', 'data', 'records', 'workflows') and a trigger phrase ('Use when the user wants to interact with Toolset data'), but lacks common variations or synonyms beyond the product name, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Toolset' is a named product giving it a clear niche with minimal conflict risk, but the surrounding action language ('Manage data, records, automate workflows') is generic enough to invite minor overlap, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/toolset/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.