Name: blueshift
Rating: 62.4 (1 reviews)
Author: membranedev

blueshift

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

Quality

74%

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/blueshift/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 content is highly actionable with executable CLI commands and a clear connection workflow including state-handling feedback loops. Its main gaps are minor prose padding and missing explicit validation for destructive/batch proxy operations.

Suggestions

Add a validation/verification checkpoint before destructive proxy calls, e.g. 'Before PUT/PATCH/DELETE, re-check the target id with membrane action run <getAction> --json'.

Trim editorial prose like 'so you can focus on the integration logic rather than auth plumbing' and the URL-normalization explanation to tighten token use.

Consider moving the proxy flag reference table and action-run details into a separate REFERENCE.md to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely efficient command-focused content, but contains minor prose padding such as 'so you can focus on the integration logic rather than auth plumbing' and the explanatory normalization paragraph.	4 / 5
Actionability	Provides copy-paste-ready commands for login, connection ensure, polling, action search/run, and proxy requests, plus a complete flag table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with a polling/state feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but lacks explicit validation checkpoints for batch or destructive proxy operations (PUT/PATCH/DELETE).	4 / 5
Progressive Disclosure	Single-file body is well-sectioned with clear headers and no nested references; no bundle files exist. It is larger than the simple-skill threshold and could arguably split the action/proxy reference out, so it stops at 4.	4 / 5
	Total	17 / 20 Passed

Description

66%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 names the product and includes an explicit 'Use when' trigger, making it distinct and reasonably complete. Its main weakness is generic, non-concrete action language and thin natural-term coverage beyond the product name.

Suggestions

Replace generic verbs with concrete actions, e.g. 'manage data, records, and automate workflows' -> 'create and update customer records, send campaigns, and trigger workflows'.

Add natural synonyms and file/record types users would mention (e.g. 'campaigns', 'events', 'catalogs', 'user lists') to broaden trigger coverage.

Tighten the 'Use when' clause with concrete scenarios, e.g. 'Use when the user wants to query BlueShift customers, send campaigns, or automate marketing workflows.'

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill forms'.	3 / 5
Completeness	Explicitly states both what it does and a 'Use when the user wants to interact with BlueShift data' trigger, though the 'what' is vague and the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product name 'BlueShift' plus generic terms like 'data', 'records', 'workflows', but misses common synonyms and variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named product 'BlueShift' gives it a clear niche with distinct triggers and minimal risk of firing for the wrong skill.	5 / 5
	Total	15 / 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/blueshift/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.