Name: bluesky-by-unshape
Rating: 60 (1 reviews)
Author: membranedev

bluesky-by-unshape

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

Quality

70%

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/bluesky-by-unshape/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 concrete, executable CLI commands and a clear connection-state workflow, and it stays mostly concise. The main weaknesses are an incomplete 'Popular actions' list relative to the promised overview entities and a stray 'Step 2' reference with no Step 1.

Suggestions

Reconcile the overview (Post/Reply/User/Feed/Notification) with the 'Popular actions' table by documenting actions for each entity or moving the full list to a referenced file.

Fix the orphaned 'Step 2' / '1b' numbering in the connection-ready section so the sequence is coherent.

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

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete CLI commands and minimal concept explanation, though a few phrasings like 'so you can focus on the integration logic rather than auth plumbing' add light padding.	4 / 5
Actionability	It provides copy-paste-ready membrane CLI commands for install, login, connection setup, action search/run, and proxy requests, covering the common cases with executable flag tables.	5 / 5
Workflow Clarity	The connection setup flow has a clear READY/BUILDING/CLIENT_ACTION_REQUIRED sequence with polling checkpoints, but it is labeled 'Step 2' with no preceding Step 1 and the overview promises five entities while only three actions are documented, leaving minor gaps.	4 / 5
Progressive Disclosure	Content is well sectioned with clear headers and no bundle files to reference, though all reference-style detail (action schemas, proxy options) is inlined rather than split into separate files, keeping it just below the ideal split.	4 / 5
	Total	17 / 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 has a clear and explicit 'Use when' trigger clause and a distinctive proper-noun subject, but its capability language is generic ('Manage data, records, and automate workflows') rather than naming concrete Bluesky actions. Tightening the 'what' with specific actions like posting, replying, or fetching feeds would raise specificity and distinctiveness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Bluesky actions such as 'Create and reply to posts, fetch feeds, and manage user notifications'.

Add natural trigger synonyms and file/URL cues, e.g. 'Use when the user wants to post, reply, or pull feeds from Bluesky via Unshape'.

Tie the 'when' clause to concrete user phrasings (e.g. mentions of Bluesky posts or feed automation) to improve distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain but its actions are minimal and generic — 'Manage data, records, and automate workflows' names no concrete capabilities, sitting between the vague score-1 anchor and the '1-2 concrete actions' score-3 anchor.	2 / 5
Completeness	It answers both 'what' (manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Bluesky by Unshape data'), but the 'what' is generic and the 'when' could be more specific, so it lands just above the midpoint.	4 / 5
Trigger Term Quality	'Bluesky by Unshape' is a distinctive proper-noun trigger, but it is repeated verbatim with no natural variations or file extensions, matching 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Bluesky by Unshape' proper noun makes it mostly distinct with only minor overlap risk against generic data-management skills, though the generic action verbs slightly weaken the niche.	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/bluesky-by-unshape/SKILL.md
Commit: f484c82

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