Name: spacelift
Rating: 50.4 (1 reviews)
Author: membranedev

spacelift

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

Quality

55%

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

Quality

Content

50%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 delivers strong, executable Membrane CLI guidance with a sensible connection workflow, but it is weighed down by a ~170-line inlined entity list that burns tokens and belongs in a reference file, and it lacks validation steps for destructive action runs.

Suggestions

Move the entity catalog into a references/ file (e.g. references/entities.md) and link to it from the overview instead of inlining ~170 bullets.

Add a validation/verification checkpoint after `membrane action run` (e.g. inspect the output state and confirm the expected result before proceeding) so destructive operations have a feedback loop.

Replace generic placeholders in examples (/path/to/endpoint, {"key": "value"}) with at least one concrete Spacelift endpoint and a realistic input payload.

Dimension	Reasoning	Score
Conciseness	The ~170-line bulleted dump of entity names (Stack, Module, Pull Request, ... Zone) is significant padding that does not teach Claude anything it could not discover via action search, matching 'Noticeably verbose; several unnecessary explanations or padded sections.' The CLI sections are efficient, but the entity list is a major inefficiency keeping it below 3.	2 / 5
Actionability	It provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) with flags and JSON examples covering the common cases, fitting 'Mostly executable guidance; concrete code or commands with minor gaps.' It is not 5 because some examples use generic placeholders like /path/to/endpoint and {"key": "value"}.	4 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → poll states → search → run) with a good connection state-machine checkpoint, but running Spacelift actions can be destructive/batch and there is no validation or verification of action results, capping the score at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Section structure is present (Overview, Working with Spacelift, Popular actions, Best practices), but the ~170-line entity catalog is inlined content that clearly belongs in a separate reference file, matching 'Some structure but could be better organized; content that should be separate is inline.' No bundle files exist to offload it.	3 / 5
	Total	12 / 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 correctly identifies a distinct named product and includes an explicit 'Use when' trigger, but its action claims ('Manage data, records, and automate workflows') are generic rather than concrete. It is solid on distinctiveness and completeness but weak on specificity.

Suggestions

Replace generic verbs with concrete Spacelift actions, e.g. 'Manage stacks, runs, modules, and drift detection; trigger tasks and review policy evaluations.'

Add a couple of natural trigger variations users might say, such as 'infrastructure-as-code deployments' or 'Terraform/Terragrunt runs'.

Tighten the 'what' to enumerate 2-3 specific capabilities so the skill's scope is unambiguous.

Dimension	Reasoning	Score
Specificity	It names the domain ("Spacelift integration") but the actions are minimal and generic ("Manage data, records, and automate workflows"), which matches the anchor 'Names the domain but actions are minimal or generic.' It does not reach 3 because no concrete actions are enumerated.	2 / 5
Completeness	Both what ("Spacelift integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Spacelift data.") are present, but the what is generic, fitting 'Has both what and when; when could be more explicit or specific.' It is not 5 because the what lacks concrete, comprehensive actions.	4 / 5
Trigger Term Quality	"Spacelift" is the specific natural term a user would say, and "interact with Spacelift data" is a usable phrase, but there is no coverage of variations or synonyms, matching 'Some relevant keywords but missing common variations or synonyms.' It is above 2 because the keyword is specific rather than generic.	3 / 5
Distinctiveness Conflict Risk	"Spacelift" is a distinct named product, giving it a clear niche with minimal conflict risk against other skills, matching 'Clear niche with distinct triggers; minimal conflict risk.'	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/spacelift/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.