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

Blog Docs Log in Get started

rebrandly

Rebrandly integration. Manage Links. Use when the user wants to interact with Rebrandly 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rebrandly/SKILL.md

Quality

Content

75%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 a comprehensive, executable command catalog and a well-sequenced connection workflow including real feedback loops. Its main weakness is mild verbosity from background/marketing prose and a partly-empty actions table that could be trimmed or externalized.

Suggestions

Cut the opening "Rebrandly is a link management platform..." background paragraph and marketing phrasing ("so you can focus on the integration logic rather than auth plumbing") since they add tokens Claude does not need.

Fill or remove the empty Description column in the Popular actions table, or move the full action list to a separate reference file with a few key examples inline.

Add an explicit "Step 2" header (or reword the "skip to Step 2" reference) so the workflow's checkpoint navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The command catalog is efficient, but the opening background paragraph ("Rebrandly is a link management platform..."), marketing-style phrasing, and a Popular actions table with empty Description columns add unnecessary tokens Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every phase (install, login, connection ensure/get, action list/run, request) plus a full proxy flag table, comprehensively covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints and a poll → check state → act → re-poll feedback loop, but the "skip to Step 2" reference has no matching header and action execution lacks an explicit verification step.	4 / 5
Progressive Disclosure	The single-file body is well organized into logical sections with no nested references, but at ~160 lines some inline reference-like content (the full proxy flag table and Popular actions list) could reasonably be split into a separate reference file.	4 / 5
	Total	16 / 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 is serviceable and correctly includes a third-person "what" plus an explicit "Use when" trigger, but it is generic on capabilities and trigger synonyms. Expanding the action list and adding natural keywords would lift it from the middle of the scale.

Suggestions

Enumerate concrete actions in the description (e.g., "create, update, and delete short links, tags, and domains") rather than the generic "Manage Links".

Add natural trigger terms and synonyms users actually say, such as "branded short links", "URL shortening", or "link management", alongside "Rebrandly".

Tighten the "Use when" clause to concrete scenarios (e.g., "Use when the user wants to create or manage branded short links in Rebrandly").

Dimension	Reasoning	Score
Specificity	The description names the Rebrandly domain and a single generic action ("Manage Links") but does not enumerate concrete capabilities like create/update/delete links, tags, or domains, landing it below the "1-2 concrete actions" anchor.	2 / 5
Completeness	It answers "what" (Rebrandly integration, manage Links) and "when" ("Use when the user wants to interact with Rebrandly data") explicitly, though the "when" clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the natural product keyword "Rebrandly" plus a "Use when... interact with Rebrandly data" clause, but lacks common synonyms (short links, branded links, URL shortener) or file extensions that users would say.	3 / 5
Distinctiveness Conflict Risk	The named brand "Rebrandly" carves a clear, mostly-distinct niche with low conflict risk against unrelated skills, but the broad "interact with Rebrandly data" trigger keeps it from maximal distinctiveness.	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/rebrandly/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.