Name: lexer
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lexer

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lexer/SKILL.md

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.

The body provides strong, executable Membrane CLI guidance with a real connection-readiness feedback loop, but is undermined by a contradictory opening that describes a compiler lexer and links to Pygments, plus broken step references in the workflow. Structure and actionability are otherwise solid.

Suggestions

Remove or rewrite the opening paragraph and the 'Official docs: https://pygments.org/docs/' link — they describe a compiler lexer/syntax highlighter, contradicting the skill's actual purpose as a Lexer data integration via Membrane.

Fix the broken workflow numbering: 'Skip to Step 2' and '#### 1b' reference steps that don't exist; renumber the connection workflow into a coherent 1 → 2 → 3 sequence with explicit checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph explains a concept (what a lexer is) that is both unnecessary and incorrect for this skill, plus minor prose padding, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login/connection ensure/action list/run/request) with a flag table, matching the 'mostly executable guidance with minor gaps' anchor; not 5 due to placeholder IDs and no worked input/output example.	4 / 5
Workflow Clarity	A genuine polling feedback loop exists (BUILDING to READY, CLIENT_ACTION_REQUIRED handling, re-poll after action), but sequencing is incoherent: 'Skip to Step 2' references a non-existent step and '#### 1b' appears with no preceding 1a/Step 1, fitting the 'sequence present but checkpoints/gaps' anchor.	3 / 5
Progressive Disclosure	With no bundle files present, the single ~135-line SKILL.md is organized into clear headed sections with no nested references and content appropriately placed, matching the 'good structure, minor organization gaps' anchor.	4 / 5
	Total	14 / 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 has an explicit 'Use when' trigger and a clear named-app niche, but its capability statement relies on generic verbs ('manage data, records, automate workflows') instead of concrete Lexer actions. It is adequate but not specific enough to fully distinguish what the skill does.

Suggestions

Replace the generic verbs ('Manage data, records, and automate workflows') with the concrete Lexer actions the skill actually performs, e.g. 'Search Lexer records, fetch data views, and run Lexer actions via Membrane.'

Broaden trigger coverage with natural phrasings a user would say beyond 'interact with Lexer data', e.g. 'query Lexer', 'pull Lexer records', or 'automate Lexer workflows'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Lexer integration') but its actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete Lexer operations, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It states both a what ('Lexer integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with Lexer data.'), but the what is generic rather than concrete, matching the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	'Lexer' and 'interact with Lexer data' provide relevant named-app trigger terms, but coverage of natural synonyms and variations a user might say is thin, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Lexer' is a named app giving a clear niche with minimal conflict risk, though the generic 'data, records, workflows' phrasing creates minor overlap with other data tools, fitting the 'mostly distinct, minor overlap' anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/lexer/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.