CtrlK
BlogDocsLog inGet started
Tessl Logo

lano

Lano integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lano 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/lano/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 well-structured, highly actionable CLI integration guide with executable commands and good connection-workflow feedback loops. Minor gaps are step-label consistency and light redundancy between sections.

Suggestions

Number the workflow steps explicitly (Step 1 install/auth, Step 2 connect, Step 3 search/run) and ensure referenced labels like 'Step 2' actually exist.

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated action-list command.

Add a brief verification step after running actions (e.g., check the response `output`/error fields) to close the workflow loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and a flag table, with only minor editorial prose ('focus on the integration logic rather than auth plumbing', 'burn less tokens') and a brief Lano intro that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, with a clear flag table covering the common cases.

5 / 5

Workflow Clarity

The connection flow has a clear sequence with state-polling feedback loops and error-state handling, but step labels are loose ('Step 2' is referenced but unlabeled) and there is no explicit post-run verification step.

4 / 5

Progressive Disclosure

The single file is well-organized into clear sections with no nested references, though some content (e.g., 'Popular actions') overlaps with the earlier 'Searching for actions' section.

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 covers both what the skill does and when to use it with an explicit trigger clause and a distinct product niche. Its main weakness is generic action verbs and limited trigger-term variety.

Suggestions

Replace generic verbs ('Manage data, records') with more specific Lano actions (e.g., 'create employees, run payroll, manage contractor payments') to lift specificity.

Expand the 'Use when' clause with concrete trigger phrases (e.g., 'when the user mentions Lano payroll, contractor payments, or international compliance').

DimensionReasoningScore

Specificity

The description names the Lano domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic and not comprehensive, fitting the 'domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Both a clear 'what' and an explicit 'Use when the user wants to interact with Lano data' trigger are present, but the 'when' is a single somewhat generic phrase rather than multiple concrete triggers.

4 / 5

Trigger Term Quality

Natural terms 'Lano', 'Lano data', and 'Lano integration' appear, but coverage lacks synonyms or variations beyond the product name itself.

3 / 5

Distinctiveness Conflict Risk

'Lano' is a specific named product with a distinct trigger, giving it a clear niche with minimal conflict risk against other skills.

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.