CtrlK
BlogDocsLog inGet started
Tessl Logo

autobound

Autobound integration. Manage data, records, and automate workflows. Use when the user wants to interact with Autobound data.

57

Quality

66%

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/autobound/SKILL.md
SKILL.md
Quality
Evals
Security

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 skill body is an efficient, actionable CLI integration guide with a well-sequenced workflow and validation checkpoints. Its main weaknesses are minor prose padding and the Popular actions table's empty descriptions.

Suggestions

Fill in the empty Description column of the Popular actions table so Claude can pick the right action without an extra search call.

Resolve the "Step 2" / "1b" numbering into a clean numbered sequence so the connect-and-poll flow is unambiguous.

Trim motivational prose (e.g. "so you can focus on the integration logic") to keep the body strictly instructional.

DimensionReasoningScore

Conciseness

The body is lean and command-focused with only minor prose padding such as "so you can focus on the integration logic rather than auth plumbing" that could be trimmed.

4 / 5

Actionability

Copy-paste-ready CLI commands (membrane login, connection ensure, action run, request) cover the common cases, though the Popular actions table has empty description cells.

4 / 5

Workflow Clarity

A clear install→authenticate→connect→poll-state→search→run sequence includes state-validation checkpoints and a poll-again retry loop, with only minor gaps like the dangling "Step 2" reference.

4 / 5

Progressive Disclosure

With no bundle files present, the single SKILL.md is well-organized into clear sections with an external docs pointer; minor gaps like the empty Popular actions cells keep it just short of ideal.

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 correctly names the integration and includes an explicit trigger clause, but its capability statement is generic boilerplate rather than concrete Autobound actions. Trigger phrasing is product-name-only with no natural synonyms.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Autobound actions, e.g. "Generate personalized emails, sales sequences, insights, and call scripts in Autobound."

Broaden the trigger with natural phrases users say, e.g. "Use when the user wants to generate sales outreach, email sequences, or prospect insights in Autobound."

Keep the product name but pair it with task-specific keywords (outreach, sequences, prospecting) to improve both trigger quality and distinctiveness.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain (Autobound) but the actions are minimal and generic rather than concrete Autobound capabilities like generating emails or sequences.

2 / 5

Completeness

An explicit "Use when the user wants to interact with Autobound data" clause is present alongside a (vague) what-statement, so both are answered, though the when could be more specific.

4 / 5

Trigger Term Quality

The trigger relies on the product name ("Autobound", "Autobound data") with some relevant keywords but no natural synonyms or variations a user might say.

3 / 5

Distinctiveness Conflict Risk

The Autobound product name makes it mostly distinct with minimal conflict risk, though the generic "data, records, workflows" phrasing leaves minor overlap with other integration skills.

4 / 5

Total

13

/

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.