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

slicknode

Slicknode integration. Manage data, records, and automate workflows. Use when the user wants to interact with Slicknode 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/slicknode/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 content is highly actionable with copy-paste commands and a well-sequenced connection workflow including validation checkpoints, but it carries some padded prose and is a long single-file monolith with no progressive disclosure to supporting files.

Suggestions

Trim explanatory prose (e.g. the URL-normalization aside and the "auth plumbing" phrasing) so every line earns its place.

Label the workflow steps explicitly so the "skip to Step 2" reference resolves to a real heading.

Move the proxy flags table and best practices into a separate reference file to reduce inline length and aid navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, but includes unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing" and an explanation of URL normalization that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end: install, login, connection ensure/get, action list/run, and proxy requests with a full flags table.	5 / 5
Workflow Clarity	The connection flow has a clear state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with an explicit polling feedback loop, though "Step 2" is referenced without a matching label and action execution lacks verification steps.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but the ~140-line single file keeps the proxy flags table and best practices inline where a separate reference could help.	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 and when with a third-person voice and a clear product niche, but its action list is generic and it lacks trigger-term synonyms beyond the brand name.

Suggestions

Replace generic verbs with concrete Slicknode capabilities, e.g. "Run GraphQL queries and mutations, manage content records, and automate workflows".

Add natural trigger synonyms such as "content model", "GraphQL API", or "Slicknode CMS" to broaden trigger-term coverage.

Make the when clause more specific, e.g. "Use when the user wants to query or mutate Slicknode content via its GraphQL API".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Slicknode domain but the listed actions are generic and minimal rather than concrete capabilities.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Slicknode data"), though the when clause is fairly generic.	4 / 5
Trigger Term Quality	"Slicknode" is the natural brand keyword users would say, and "data, records, workflows" add some relevance, but common synonyms and variations are missing.	3 / 5
Distinctiveness Conflict Risk	Slicknode is a specific named product with a distinct trigger ("interact with Slicknode data"), giving mostly distinct niche with only minor overlap risk from generic data-management phrasing.	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/slicknode/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.