Name: linguapop
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

linguapop

Linguapop integration. Manage Users, Organizations. Use when the user wants to interact with Linguapop data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 an efficient, highly actionable CLI integration guide with executable commands, explicit state-based workflow checkpoints, and good structure. Its main weaknesses are minor over-explanation and small organization/numbering inconsistencies.

Suggestions

Fix the step numbering: label the explicit "Step 1"/"Step 2" sections referenced in the text so "1b" and "Skip to Step 2" resolve unambiguously.

Trim rationale prose like "so you can focus on the integration logic rather than auth plumbing" to keep the guide lean.

Add a short note on how to obtain/replace the <actionId> and CONNECTION_ID placeholders, or show one end-to-end example with real values substituted.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples and compact tables, with only minor over-explanation such as the auth-plumbing rationale and best-practice prose that could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands with flags and JSON examples for install, auth, connection, search, run, and proxy, with only minor placeholder gaps (<actionId>, CONNECTION_ID).	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops, though the unlabeled "Step 2" and "1b" numbering introduce minor gaps.	4 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with no nested external references and content appropriately inline; minor organization gaps in section numbering keep it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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 names the integration domain and a couple of actions with an explicit use-when clause, but the actions are generic ("Manage") and the trigger phrasing is broad. It is functional and distinct but lacks concrete action specificity and richer trigger terms.

Suggestions

Replace generic "Manage Users, Organizations" with concrete verbs, e.g. "Create, list, and update Users and Organizations; send placement-test invitations; retrieve available languages."

Expand the "Use when" clause with concrete trigger phrases users would naturally say, e.g. "Use when the user wants to send Linguapop invitations, look up languages, or manage Linguapop users and organizations."

Add file-format or entity synonyms (e.g. "placement tests", "candidates") to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage Users, Organizations" names the Linguapop domain plus two actions, but "Manage" is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	It gives a clear "what" ("Manage Users, Organizations") and an explicit "when" ("Use when the user wants to interact with Linguapop data"), though the trigger could be more specific.	4 / 5
Trigger Term Quality	"Linguapop" and "Users, Organizations" provide some relevant domain keywords, but common natural variations or synonyms users would say are missing.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named Linguapop platform gives it a clear niche with minimal conflict risk, though "interact with Linguapop data" is slightly broad.	4 / 5
	Total	14 / 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/linguapop/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.