Name: restack
Rating: 61.6 (1 reviews)
Author: membranedev

restack

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

Quality

72%

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

Quality

Content

82%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-ready commands and a clear, state-validated connection workflow, organized into clean sections. Its main weaknesses are minor redundancy between action-search sections and an undefined 'Step 2' reference.

Suggestions

Consolidate the 'Searching for actions' and 'Popular actions' sections, which repeat the same `action list --intent=QUERY` command, to remove redundancy.

Label 'Step 2' explicitly (e.g. add a '## Step 2: Search and run actions' heading) so the 'skip to Step 2' references resolve clearly.

Tighten promotional phrasing like 'so you can focus on the integration logic rather than auth plumbing' to factual notes about automatic credential refresh.

Dimension	Reasoning	Score
Conciseness	The body is an efficient, mostly-operational CLI guide, but the 'Searching for actions' and 'Popular actions' sections overlap and light promotional phrasing ('focus on the integration logic rather than auth plumbing') could be trimmed, matching the score-4 anchor.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure/get with --wait, action list/run, request) plus a flags table, matching the score-5 anchor ('fully executable; copy-paste ready; specific examples cover the common cases').	5 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with an explicit state-machine feedback loop (READY/BUILDING poll/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but 'skip to Step 2' is referenced without a labeled Step 2 heading, holding it at the score-4 anchor.	4 / 5
Progressive Disclosure	With no bundle files present and a single ~145-line file, the content is well-organized into clear sections with no deep nesting, and the inlined flags table and best practices are appropriately placed for a CLI guide, matching the score-4 anchor.	4 / 5
	Total	17 / 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 clearly answers both what and when and is anchored to a distinct named platform, but its action verbs ('manage', 'automate') are generic and it lacks richer trigger-term variants. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Restack actions, e.g. 'Create and manage Stacks, Cards, and records; run and automate workflows' to lift specificity.

Expand the 'when' clause with concrete trigger phrases a user would say, e.g. 'Use when the user wants to query Restack records, manage Stacks/Cards, or automate Restack workflows.'

Add common synonyms or Restack entity names (Stack, Card, Workspace, Integration) as trigger keywords to improve distinctiveness and natural-language matching.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names three actions, but the verb 'manage' is generic rather than the concrete verbs (extract/fill/merge) seen in the score-4 anchor, so it sits at the score-3 anchor ('names domain and 1-2 concrete actions').	3 / 5
Completeness	It has both an explicit what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Restack data'), but the when is a single generic trigger and the what is not concrete enough to reach the multi-trigger score-5 anchor.	4 / 5
Trigger Term Quality	Keywords 'Restack', 'data', 'records', 'workflows', and 'interact with Restack data' are relevant but lack synonym or file-extension variants, matching the score-3 anchor ('some relevant keywords but missing common variations').	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform 'Restack' establishes a clear niche with distinct triggers, but the generic data-management verbs leave minor overlap risk with other integration skills, matching the score-4 anchor.	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/restack/SKILL.md
Commit: f484c82

Reviewed: 5 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.