Name: bitly
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bitly

Bitly integration. Manage Bitlinks, Users, Groups, Brands. Use when the user wants to interact with Bitly data.

Quality

61%

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

Quality

Content

61%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 a solid, command-driven integration guide with a clear connection workflow and strong actionability, but it carries some unnecessary background prose and lacks validation safeguards around its destructive actions.

Suggestions

Remove the opening "Bitly is a link management platform…" paragraph and Membrane-philosophy commentary; assume Claude knows what Bitly is and lead directly with the CLI workflow.

Add an explicit validation/confirmation checkpoint before destructive actions, e.g. "Before running delete-bitlink, confirm the target Bitlink with the user and verify via get-bitlink first."

Make the BUILDING-state polling loop concrete with an executable command or a small loop example rather than "Keep polling until state is no longer BUILDING", and show how to extract the connection id from the --json output.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and command-focused, but it opens with a two-sentence explainer of what Bitly is and who uses it, plus Membrane-philosophy prose ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens"), which Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request proxying, plus a concrete popular-actions table with keys; minor gaps include the polling loop described in prose rather than as an executable command and no example of extracting the connection id from output.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and error recovery, but the skill lists destructive actions (e.g. delete-bitlink) with no validation or confirmation checkpoint, which caps workflow clarity per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist, so all content lives in SKILL.md; it is well sectioned with clear headers and no nested references, though the 12-row popular-actions table and dangling "Step 2" reference show minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

62%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 states what the skill does and when to use it, anchored to a specific product, but its trigger language and action vocabulary are too generic to fully distinguish or comprehensively signal the skill.

Suggestions

Replace the single verb "Manage" with concrete actions, e.g. "Shorten and expand links, retrieve click analytics, and manage Bitlinks, Groups, and Users."

Add natural user-facing trigger phrases such as "shorten a URL", "link shortener", "Bitly link analytics", or ".bit.ly links" to improve trigger recall.

Tighten the "Use when" clause with concrete triggers: "Use when the user wants to shorten a link, get Bitly click analytics, or manage Bitlinks, groups, or users."

Dimension	Reasoning	Score
Specificity	"Manage Bitlinks, Users, Groups, Brands" names the domain and several resource types but relies on a single generic verb ("Manage") rather than enumerating distinct concrete actions (shorten, expand, get clicks, delete).	3 / 5
Completeness	Both halves are present — "Manage Bitlinks, Users, Groups, Brands" (what) and "Use when the user wants to interact with Bitly data" (when) — but the trigger clause is generic rather than packed with concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	It surfaces domain terms ("Bitly", "Bitlinks", "Users", "Groups", "Brands") but omits the natural phrases users most often say, such as "shorten a link/URL", "link shortener", or "link analytics/clicks".	3 / 5
Distinctiveness Conflict Risk	"Bitly integration" carves a clear product-specific niche with low conflict risk, though a generic "shorten this link" request without naming Bitly could overlap with a general URL-shortener skill.	4 / 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/bitly/SKILL.md
Commit: f484c82

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