Name: linguixcom
Rating: 52 (1 reviews)
Author: membranedev

linguixcom

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

Quality

58%

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/linguixcom/SKILL.md

Quality

Content

67%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 is well-structured and highly actionable with concrete CLI commands and a connection-state feedback loop. Its main weaknesses are minor verbosity in the intro and inconsistent step numbering that slightly weakens workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style intro ('used by professionals, students, and anyone who wants to write more clearly') and phrases like 'so you can focus on the integration logic rather than auth plumbing'. It is above 2 because the bulk is actionable, not padded throughout.	3 / 5
Actionability	The skill provides concrete, copy-pasteable commands for install, login, connection, action listing/running, and proxy requests, plus a flag table, matching 'mostly executable guidance; concrete code or commands with minor gaps'. It does not reach 5 because examples use generic placeholders rather than real Linguix action ids or inputs.	4 / 5
Workflow Clarity	There is a clear sequence (install, authenticate, connect, search, run, proxy) with validation checkpoints via state polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-poll feedback. It stops at 4 because step numbering is inconsistent ('skip to Step 2' with no labeled Step 1/2) and some checkpoints are implicit.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested external references and no bundle files, matching 'good structure; most content is appropriately placed'. It does not reach 5 because the inlined clientAction details and request-flag table could live in separate reference files for a skill of this length.	4 / 5
	Total	15 / 20 Passed

Description

48%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 trigger clause and a distinct product niche, but its capability list is generic and vague. Tightening 'Manage data, records, and automate workflows' into concrete Linguix-specific actions would lift specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Linguix.com actions (e.g. 'check grammar and style, manage documents, run writing checks').

Add natural trigger synonyms beyond 'Linguix.com data', such as 'writing assistant', 'grammar check', or 'Linguix API'.

State the 'what' as specific operations so the description clearly answers what the skill does, not just when to use it.

Dimension	Reasoning	Score
Specificity	The description names the Linguix.com domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor. It does not rise to a 3 because no truly concrete operations are enumerated.	2 / 5
Completeness	Both a 'what' and an explicit 'Use when' clause are present, but the 'what' ('Manage data, records, and automate workflows') is vague, so it does not reach the 4 anchor's clear 'what'. It clears 2 because the 'when' is explicit rather than absent.	3 / 5
Trigger Term Quality	'Use when the user wants to interact with Linguix.com data' supplies a relevant keyword (Linguix.com) but lacks common variations or synonyms, fitting 'some relevant keywords but missing common variations or synonyms'. It is above 2 because the term is product-specific and natural rather than generic jargon.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product Linguix.com gives it a clear niche with minor overlap risk, matching 'mostly distinct; minor overlap risk'. It does not reach 5 because the generic action verbs ('manage data') could overlap with other data skills.	4 / 5
	Total	12 / 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/linguixcom/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.