CtrlK
BlogDocsLog inGet started
Tessl Logo

search-api

Search API integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Search API data.

57

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

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.

A well-structured, actionable CLI integration guide with concrete commands throughout. It is held back by an unnecessary concept-explanation preamble and a lack of validation checkpoints for destructive proxy operations.

Suggestions

Remove the opening paragraph explaining what a search API is and trim marketing phrasing like "so you can focus on the integration logic rather than auth plumbing" — Claude already knows these concepts.

Add validation checkpoints for destructive operations: verify a connection succeeded before running actions, and confirm the target before proxying a DELETE/PUT; the proxy section currently supports destructive methods with no verify step.

De-duplicate the "Searching for actions" and "Popular actions" sections, which both repeat the same `action list --intent=QUERY` discovery command.

DimensionReasoningScore

Conciseness

Mostly efficient command references and a flags table, but it opens by explaining what a search API is ("provides search functionality... find specific information within large datasets") and includes marketing phrasing ("so you can focus on the integration logic rather than auth plumbing") that Claude does not need.

3 / 5

Actionability

Concrete, copy-paste-ready Membrane CLI commands cover setup, connecting, discovery, running actions, and proxying, plus a thorough flags table; minor gaps are that commands rely on placeholders throughout and there is no end-to-end worked example with real values.

4 / 5

Workflow Clarity

A clear sequence is present (login → connect → discover actions → run → proxy), but there are no explicit validation checkpoints, and the proxy section supports destructive HTTP methods (DELETE/PUT) with no verify step, which caps this dimension at 3.

3 / 5

Progressive Disclosure

A single self-contained file with well-organized sections and no need for external references; the skeletal "Search API Overview" (four bare bullet labels) and minor redundancy between "Searching for actions" and "Popular actions" keep it just below a 5.

4 / 5

Total

14

/

20

Passed

Description

70%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.

A solid third-person description that covers both capabilities and a use-trigger, with good keyword coverage from the named entities. Its main weakness is generic action verbs and a circular "when" clause that could name concrete triggers.

Suggestions

Replace the single generic verb "Manage" with 2-3 distinct concrete actions (e.g., "create, update, and search Deals, Persons, Organizations...") so capabilities read as specific actions rather than one verb over many entities.

Expand the "Use when..." trigger with concrete phrases a user would actually say, e.g., "Use when the user wants to search or manage Deals, Persons, Organizations, Leads, Projects, or Pipelines."

DimensionReasoningScore

Specificity

The description names the domain and six concrete entities ("Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more"), but the actions are a single generic verb ("Manage"/"interact with") rather than multiple distinct concrete actions.

3 / 5

Completeness

It answers both "what" (manage the listed entities) and "when" ("Use when the user wants to interact with Search API data"), but the trigger clause is somewhat generic and circular rather than a rich list of concrete trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage with several natural terms a user would say (the six entity names plus "Search API" and "Search API data"), though synonyms or variations of the trigger phrasing are missing.

4 / 5

Distinctiveness Conflict Risk

The entity combination (Deals, Persons, Organizations, Leads, Projects, Pipelines) signals a clear niche, but the name "Search API" is generic and carries minor overlap risk with general search-related skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.