CtrlK
BlogDocsLog inGet started
Tessl Logo

gobiolink

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

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gobiolink/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 executable commands and a well-structured single-file layout. Its one substantive gap is the absence of validation/verification guidance around the destructive actions the skill exposes.

Suggestions

Add a verify-before-delete checkpoint for destructive actions (e.g. run get-* to confirm the target ID before delete-*, or list and show the to-be-deleted resource), turning the running-actions guidance into a feedback loop.

Trim the influencer/business framing in the opening paragraph and editorial phrases like "This is the fastest way to get a connection" to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete commands and minimal padding, though a few lines (the influencer framing and "This is the fastest way to get a connection") could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every phase — install, login, connection ensure, action list/run, and proxy requests — covering the common cases.

5 / 5

Workflow Clarity

The connection flow has explicit state-based polling and retry checkpoints, but destructive actions (delete-data, delete-project, delete-link, delete-qr-code) are surfaced with no verification step, capping workflow clarity per the destructive-operations rule.

3 / 5

Progressive Disclosure

The SKILL.md is a single well-organized file with clear sections and no nested or buried references; for a self-contained skill with no needed external bundles, this earns the top anchor.

5 / 5

Total

17

/

20

Passed

Description

66%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 answers both what the skill does and when to use it, anchored to a clearly distinct product name. Its main weakness is thin specificity and trigger-term coverage — only two actions and the product name as the lone trigger phrase.

Suggestions

Expand the action list beyond 'Manage Organizations, Users' to cover the breadth surfaced in the body (Links, Projects, QR Codes, data entries) so specificity reads as comprehensive.

Add natural trigger terms a user would actually say — e.g. 'shortened links', 'link-in-bio', 'QR codes', or 'form data' — rather than relying solely on the product name.

DimensionReasoningScore

Specificity

The description names the domain ("Gobio.link integration") and lists a couple of concrete actions ("Manage Organizations, Users"), matching the 1-2 concrete actions anchor without being comprehensive.

3 / 5

Completeness

Both 'what' ("Gobio.link integration. Manage Organizations, Users") and an explicit 'when' ("Use when the user wants to interact with Gobio.link data") are present, though the trigger phrasing could be more concrete.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Gobio.link data" surfaces the product name as a relevant keyword, but it lacks common synonyms or file/feature variations users might say.

3 / 5

Distinctiveness Conflict Risk

The named product "Gobio.link" gives it a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.