Name: reputation-lyncs
Rating: 60.8 (1 reviews)
Author: membranedev

reputation-lyncs

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

Quality

71%

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

Quality

Content

80%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 highly actionable with executable CLI commands and a clear state-machine for connection setup, and it is reasonably concise. The main gaps are the lack of an explicit ordered workflow with validation feedback loops and no use of bundle files to offload detail.

Suggestions

Add an explicit numbered end-to-end workflow (install -> login -> connection ensure -> wait -> action list -> action run) with an explicit validate-and-retry checkpoint after polling for connection state.

Consider moving the proxy request-flag reference table and the clientAction schema details into a references/ file, keeping SKILL.md a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands and a tight options table, though lines like 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing' and the overview's product-marketing framing add minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, request proxy) with concrete flags and a clear options table, covering the common cases fully.	5 / 5
Workflow Clarity	The connection setup is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling loops, but it lacks a top-level ordered workflow and validation is implicit (re-polling) rather than an explicit validate->fix->retry loop.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no bundle files to split out, and references to external docs are signaled; minor gaps are the absence of a navigational overview and some inline reference material that a bundle file could hold.	4 / 5
	Total	17 / 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 clearly names the target product and provides an explicit 'Use when' trigger, giving it strong distinctiveness and completeness. Weaknesses are generic action verbs and limited natural trigger-term coverage, which keep specificity and trigger_term_quality mid-range.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with specific operations the skill performs, e.g., 'track reviews, monitor social mentions, and analyze brand sentiment'.

Expand the 'Use when' clause with concrete natural-language triggers a user would actually say, such as 'reviews', 'online reputation', or 'brand sentiment'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Reputation Lyncs') and lists concrete actions ('Manage data, records, and automate workflows'), but the actions are broad and generic rather than a comprehensive set of specific operations, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Reputation Lyncs data'), satisfying both, though the 'when' is generic and could name concrete trigger scenarios more explicitly.	4 / 5
Trigger Term Quality	It includes 'Reputation Lyncs' and the trigger 'when the user wants to interact with Reputation Lyncs data', but it offers few natural synonyms or variations a user might say (e.g., reviews, mentions, sentiment), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The product-specific name 'Reputation Lyncs' creates a clear niche with distinct triggers and minimal conflict risk with unrelated skills.	5 / 5
	Total	15 / 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/reputation-lyncs/SKILL.md
Commit: f484c82

Reviewed: 5 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.