Name: linkly
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

linkly

Linkly integration. Manage Organizations, Users. Use when the user wants to interact with Linkly data.

Quality

60%

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

Quality

Content

57%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 delivers concrete, executable CLI guidance with a solid connection-readiness workflow, but carries mild explanatory padding and lacks validation checkpoints for potentially destructive action/proxy calls. With no bundle files, all detail lives inline rather than being progressively disclosed.

Suggestions

Add a validation/verification checkpoint before destructive or write operations (e.g., confirming a connection is READY and reviewing the action's effect before running DELETE/PUT via the proxy).

Move the detailed clientAction state machine and the proxy flag table into a referenced file (e.g., references/connections.md) to enable one-level-deep progressive disclosure.

Trim conceptual framing about what Linkly is and the "auth plumbing" aside so every token earns its place, and populate the "Popular actions" section with concrete example actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary framing such as "Linkly is a smart link management platform..." and "so you can focus on the integration logic rather than auth plumbing" that could be trimmed.	3 / 5
Actionability	Copy-paste-ready CLI commands with real flags and a proxy options table provide mostly executable guidance; minor gaps remain in placeholders (CONNECTION_ID, QUERY) and a thin "Popular actions" section that lists no actual actions.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with a state-polling feedback loop, but the action-running and proxy workflows (which enable DELETE and user/org management) lack validation checkpoints, capping the score per the destructive-operations guidance.	3 / 5
Progressive Disclosure	The file is well-sectioned with clear headers, but all content is inline in a single 145-line SKILL.md with no bundle files or one-level-deep references to absorb the detailed state machine and flag table.	3 / 5
	Total	13 / 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 concisely pairs a clear capability statement with an explicit trigger clause and a distinctive named platform, satisfying both what and when. Its main weakness is limited action coverage and keyword variety.

Suggestions

Expand the capability list beyond Organizations and Users to mention Links, Bundles, Spaces, Tags, and Reports for fuller coverage.

Broaden trigger keywords with natural user phrases such as "shorten links", "track links", or "Linkly reports" rather than relying on the product name alone.

Tighten the "Use when" clause to name concrete Linkly tasks (e.g., managing links or viewing reports) instead of the generic "interact with Linkly data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Linkly integration") and two concrete actions ("Manage Organizations, Users"), but coverage is not comprehensive given Bundles, Spaces, Tags, and Reports are unmentioned.	3 / 5
Completeness	Both a clear "what" ("Manage Organizations, Users") and an explicit "Use when..." clause are present; the "when" could be more specific about which Linkly tasks apply.	4 / 5
Trigger Term Quality	The proper noun "Linkly" recurs with an explicit trigger ("Use when the user wants to interact with Linkly data"), but there is little keyword variety or synonyms beyond the product name.	3 / 5
Distinctiveness Conflict Risk	The named proprietary platform ("Linkly") gives a clear niche with distinct triggers; minor overlap risk with generic user/organization-management skills keeps it below 5.	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/linkly/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.