CtrlK
BlogDocsLog inGet started
Tessl Logo

clearbit

Clearbit integration. Manage Persons, Organizations. Use when the user wants to interact with Clearbit data.

56

Quality

65%

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

Quality

Content

67%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 delivers executable CLI guidance with a clear, validated connection workflow and well-organized sections. Its main weakness is token efficiency, with marketing padding and repeated auth explanations that could be trimmed.

Suggestions

Cut marketing-fluff sentences like "so you can focus on the integration logic rather than auth plumbing" and consolidate the repeated Membrane-auth explanations.

Fix the broken step numbering by labeling the post-connection step as "Step 2" (or remove the "skip to Step 2" reference) so the workflow cross-references resolve.

Move the popular-actions table and proxy flags table into a reference file, keeping SKILL.md a lean overview with one-level-deep links, to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete command examples, but padded with marketing fluff ("focus on the integration logic rather than auth plumbing") and repeated explanations of Membrane auth, matching anchor 3 rather than 4.

3 / 5

Actionability

Provides copy-paste-ready CLI commands across install, login, connection, action search/run, and proxy, plus a flags table and popular-actions table, with only minor gaps from placeholder values, matching anchor 4 and approaching 5.

4 / 5

Workflow Clarity

The connection workflow is sequenced with state-based validation checkpoints and a re-poll feedback loop for CLIENT_ACTION_REQUIRED, but the "skip to Step 2" reference points at an unlabeled step, leaving a minor gap at anchor 4.

4 / 5

Progressive Disclosure

No bundle files exist, and the single ~150-line file is organized into clear sections (Overview, Working with Clearbit, Popular actions, Best practices) with good navigation, matching anchor 4.

4 / 5

Total

15

/

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 is a concise, third-person statement that names the service and two object types and includes an explicit Use-when clause. It is mostly clear and distinct, but the actions and trigger terms remain generic.

Suggestions

Replace the generic verb "Manage" with specific actions (e.g., "Enrich, search, and reveal Person and Company records").

Expand the when-clause with concrete natural triggers users would say (e.g., "Use when the user wants to enrich leads, find a company by domain or IP, or look up a person by email").

Add file extensions or product-name synonyms (e.g., "Clearbit data", "Clearbit API") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Clearbit domain plus two concrete entities ("Manage Persons, Organizations"), but the action verb "Manage" is generic and coverage is not comprehensive, matching anchor 3 rather than 4.

3 / 5

Completeness

Answers both "what" (Manage Persons, Organizations) and "when" ("Use when the user wants to interact with Clearbit data"), but the when-clause is generic rather than concrete trigger phrases, so it falls at anchor 4 not 5.

4 / 5

Trigger Term Quality

Contains Clearbit-specific terms (Persons, Organizations, Clearbit data) but lacks common variations or synonyms users might naturally say, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

Clearbit is a named service giving it a clear niche with minimal conflict risk, though the broad "interact with Clearbit data" trigger leaves minor overlap risk with related Clearbit skills, matching anchor 4.

4 / 5

Total

14

/

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.