CtrlK
BlogDocsLog inGet started
Tessl Logo

barcode-lookup

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

60

Quality

70%

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/barcode-lookup/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 a tight, executable guide to driving Barcode Lookup through the Membrane CLI, with strong command coverage and a well-instrumented connection-readiness flow; its main weaknesses are minor structural labeling gaps and a sparse actions table.

DimensionReasoningScore

Conciseness

The body is largely command-driven and skips explaining concepts Claude already knows, with only minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and the agent-types aside that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout — install, login, connection ensure/get with --wait, action list/run with --input JSON, and request proxying with a concrete flag table — covering the common cases.

5 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-ready → search → run sequence is clear with explicit state-based checkpoints and a re-poll feedback loop, but the "skip to Step 2" reference points to no labeled Step 2 and numbering is inconsistent ("1b" with no "1a").

4 / 5

Progressive Disclosure

The single file is well-organized into clear sections with no nested references and no bundle files to navigate, though the Popular actions table carries an empty description column and the ~150-line length slightly exceeds the simple-skill threshold.

4 / 5

Total

17

/

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 pairs a named integration with an explicit "Use when" trigger, but its capability statement relies on generic verbs (manage, automate) rather than the concrete product/barcode actions the skill actually exposes.

Suggestions

Replace "Manage data, records, and automate workflows" with the concrete actions the skill performs, e.g. "Look up products by barcode, search products by ASIN/MPN/brand/category, and run Barcode Lookup workflows."

Broaden trigger terms to include natural phrasings users say, such as "scan a barcode", "look up a product", or "find product details".

Tighten the "what" so it reflects the specific Barcode Lookup actions rather than generic data-management language.

DimensionReasoningScore

Specificity

The description names the domain ("Barcode Lookup integration") but the stated actions — "Manage data, records, and automate workflows" — are minimal and generic, with no concrete operations like lookup-by-barcode or product search.

2 / 5

Completeness

Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Barcode Lookup data") are present; the "when" is explicit but the "what" is generic and could be more specific.

4 / 5

Trigger Term Quality

It includes relevant keywords ("Barcode Lookup", "barcode", "data") and a natural trigger phrase, but misses common variations users would say such as "scan barcode", "product lookup", or "product info".

3 / 5

Distinctiveness Conflict Risk

Tying the trigger to a named app ("Barcode Lookup") gives it a clear niche with low conflict risk, though the generic "Manage data, records, and automate workflows" phrase could overlap with other data-management 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.