CtrlK
BlogDocsLog inGet started
Tessl Logo

implisense-api

Implisense API integration. Manage Organizations. Use when the user wants to interact with Implisense API data.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/implisense-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 copy-paste-ready CLI commands and a sensible end-to-end workflow including a connection-readiness feedback loop. Main weaknesses are minor verbosity in the intro and a couple of dangling step references that break the otherwise clear sequence.

Suggestions

Trim the marketing-style intro paragraph ('comprehensive database... used by sales, marketing, and research teams') to a one-line factual purpose; Claude does not need the audience pitch.

Fix the dangling navigation: either label the post-connection section as 'Step 2' consistently or remove the 'skip to Step 2' / orphaned '1b' references in favor of a coherent numbered sequence.

Consider moving the 9-row Popular actions table to a references file so SKILL.md stays a lean overview, which would also tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly executable commands and a useful actions table with only minor over-explanation (the marketing-style intro paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing'), fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the leaner level-5.

4 / 5

Actionability

It provides copy-paste-ready commands for the full lifecycle (npm install, membrane login, connection ensure, action list/run, request proxy) with real flags and a concrete popular-actions table, matching the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The install → authenticate → connect → wait/search → run → proxy sequence is clear with an explicit connection-state feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but dangling references like 'skip to Step 2' (no labeled Step 2) and the orphaned '1b' heading leave minor sequencing gaps that keep it below level 5.

4 / 5

Progressive Disclosure

No bundle files exist, so structure is assessed on the single SKILL.md; it is well-organized into clearly headed sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, but at ~150 lines with a sizable inlined actions table it sits at 'good structure, minor organization gaps' rather than the level-5 lean-overview ideal.

4 / 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 is well-formed with explicit what/when structure and a clearly distinct niche, but its capability list is thin and its trigger phrasing lacks synonyms or concrete trigger terms. Tightening 'Manage Organizations' into specific actions and broadening the 'Use when' clause would lift specificity and trigger-term quality.

Suggestions

Replace the generic 'Manage Organizations' with 2-3 concrete capabilities (e.g., 'Search German companies, retrieve company details, people, and events').

Expand the 'Use when' clause with concrete trigger phrases users would actually say (e.g., company lookups, lead enrichment, market research) rather than only 'interact with Implisense API data'.

Add natural synonyms/file-extensions or related terms (e.g., 'company data', 'B2B lookups') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Implisense API integration') and one concrete-ish action ('Manage Organizations'), but that action is generic ('manage') and coverage is far from comprehensive, matching the 'domain + 1-2 actions, not comprehensive' anchor rather than the more thorough level 4-5 examples.

3 / 5

Completeness

It states both what ('Implisense API integration. Manage Organizations.') and when ('Use when the user wants to interact with Implisense API data.'), but the 'when' clause is generic rather than listing concrete trigger phrases, matching the level-4 anchor where both are present yet 'when' could be more specific.

4 / 5

Trigger Term Quality

'Use when the user wants to interact with Implisense API data' surfaces the natural product name, but offers only one phrasing with no synonyms or variations, fitting the 'some relevant keywords but missing common variations/synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to a specific named product ('Implisense API') creates a clear niche with distinct triggers and minimal overlap risk with other skills, matching the level-5 anchor.

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.