Name: linqs
Rating: 66.4 (1 reviews)
Author: membranedev

linqs

Linqs integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Linqs data.

Quality

80%

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

Quality

Content

88%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 integration guide with concrete executable commands and a clearly sequenced, validated connection workflow; its main gaps are minor over-explanation and some inline reference material that could live in separate files.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with brief, necessary operational context (auth, connection states) rather than concepts Claude already knows; a few lines like 'This is the fastest way to get a connection' could be trimmed, matching the 'efficient; minor over-explanation' anchor.	4 / 5
Actionability	Commands are concrete and copy-paste ready throughout (install, login, connection ensure/get with --wait, action list/run with --input, request with a full flag table), covering the common cases and matching the 'fully executable' anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced (install -> login -> connection ensure -> poll state -> search actions -> run) with explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and an error-recovery feedback loop ('poll again' after user action), matching the top anchor.	5 / 5
Progressive Disclosure	No bundle files exist, but the ~150-line body is organized into clear sections (Overview, Working with Linqs, Popular actions, Best practices); some inline detail like the request flag table and clientAction sub-fields could be split into a reference file, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	18 / 20 Passed

Description

71%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 is third-person, names a clear niche, and provides both a 'what' and an explicit 'Use when' trigger, but the trigger language is generic and lacks synonyms or natural phrasings users would say.

Suggestions

Broaden the trigger with natural user phrasings and synonyms, e.g. 'Use when the user wants to manage Linqs deals, leads, or contacts, log sales activities, or query Linqs CRM data.'

Replace the generic 'Manage' with more concrete verbs (create, update, list, search) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the Linqs domain and lists six concrete entity types ('Manage Persons, Organizations, Deals, Leads, Activities, Notes'), matching the 'several specific actions' anchor; the generic verb 'Manage' and 'and more' hedge keep it just below comprehensive (5).	4 / 5
Completeness	Both 'what' (manage the listed entities) and 'when' ('Use when the user wants to interact with Linqs data') are present, but the trigger is fairly generic rather than concrete, fitting the 'both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The 'Use when the user wants to interact with Linqs data' clause supplies the domain keyword and entity names but no synonyms or natural user variations, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Linqs integration' tied to a specific named app with distinct triggers gives it a clear niche and minimal conflict risk, matching the top anchor; voice is correctly third person.	5 / 5
	Total	16 / 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/linqs/SKILL.md
Commit: f484c82

Reviewed: 10 hours 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.