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

Blog Docs Log in Get started

linkish

Linkish integration. Manage Organizations. Use when the user wants to interact with Linkish 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/linkish/SKILL.md

Quality

Content

72%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 comprehensive executable commands and clean organization, but it opens with unnecessary marketing prose and lacks validation/verification checkpoints for its mutating operations. Trimming the intro and adding verify-after-run steps would lift the two weaker dimensions.

Suggestions

Cut or compress the opening marketing paragraph to a one-line definition of Linkish; Claude does not need the business value framing.

Add a verification step after connecting and after running mutating actions (e.g. re-list connections to confirm the new id, or check the action output before proceeding) to satisfy the validation-checkpoint requirement.

Drop filler lines like "Use action names and parameters as needed." that add no concrete guidance.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but the opening marketing paragraph ("It allows marketers and businesses to create branded short links... optimize their marketing campaigns") over-explains what the product is, and filler like "Use action names and parameters as needed" adds little.	3 / 5
Actionability	It provides copy-paste-ready bash commands for every key flow (install, login, search, connect, action list/run with JSON input, proxy requests) plus a full flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	The install → setup → connect → search → run sequence is clearly ordered, but there are no validation checkpoints or error-recovery loops, and the skill covers mutating operations (save-link, proxy POST/PUT/DELETE) which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The skill is a compact, well-organized single file with clear section headers, tables, and code blocks and no nested references, meeting the simple-skill exception for progressive disclosure.	5 / 5
	Total	16 / 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 covers both what and when and is clearly distinct, but its capability list is thin and generic ("Manage Organizations") and it omits the concrete action phrases (short links, tags, collections) a user would naturally say. Tightening the action list would raise specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Organizations" with concrete Linkish actions such as creating branded short links, tagging links, and retrieving link collections.

Add natural trigger phrases users would say, e.g. "Use when the user wants to shorten links, manage link collections, or track link clicks in Linkish."

Mirror the body's actual entities (Link, Tag, Collections) so the description previews the real capabilities.

Dimension	Reasoning	Score
Specificity	The description only names the domain ("Linkish integration") plus one generic action ("Manage Organizations"), with no concrete capability verbs such as shortening links or tracking clicks.	2 / 5
Completeness	Both a "what" ("Linkish integration. Manage Organizations.") and a "when" ("Use when the user wants to interact with Linkish data.") are explicitly present, though neither is concrete or specific.	4 / 5
Trigger Term Quality	"Linkish" and "interact with Linkish data" are natural domain keywords, but the description misses the common action phrases users would actually say (shorten links, track clicks, manage collections) and any synonyms.	3 / 5
Distinctiveness Conflict Risk	It names a proprietary platform (Linkish) with distinct triggers, giving it a clear niche and minimal risk of triggering for unrelated skills.	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/linkish/SKILL.md
Commit: f484c82

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