Name: dux-soup
Rating: 52.8 (1 reviews)
Author: membranedev

dux-soup

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

Quality

59%

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

Quality

Content

61%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 concrete CLI commands and a well-structured connection workflow, but it loses points for redundant commands, an undefined 'Step 2' reference, and missing validation after destructive action/proxy runs. Trimming repetition and adding a verify step would meaningfully raise the score.

Suggestions

Add a validation/verification checkpoint after running actions or proxy POSTs (e.g., inspect the 'output' field and confirm the expected record count or state before proceeding), since LinkedIn automation is destructive/batch in nature.

Define or remove the dangling 'Step 2' reference (the body says 'Skip to Step 2' but no Step 2 heading exists) so the workflow is navigable.

De-duplicate the 'membrane action list --intent=QUERY' instructions that appear in both 'Searching for actions' and 'Popular actions', and trim the padded entity overview list.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the entity overview list, a repeated 'membrane action list --intent' command (in both 'Searching for actions' and 'Popular actions'), and a somewhat padded 'Best practices' section could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready CLI commands with a flag table covering install, auth, connection, search, run, and proxy, matching 'mostly executable guidance with minor gaps'; placeholders like CONNECTION_ID and the bare proxy example keep it just below level 5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state polling checkpoints, but running actions and proxy POSTs (destructive/batch LinkedIn operations) lack any verification step, which caps workflow clarity at 3; additionally the referenced 'Step 2' is never defined.	3 / 5
Progressive Disclosure	There are no bundle files and the content is organized into clear, well-labeled sections with no nested references, fitting 'good structure; most content appropriately placed'; since it is over 50 lines and entirely inline, it stays at level 4 rather than 5.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly identifies the Dux Soup niche and includes an explicit trigger clause, but its capability wording is generic rather than concrete. Tightening the action list to specific Dux Soup operations would lift specificity and distinctiveness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Dux Soup capabilities such as 'visit profiles, send connection requests, launch campaigns, and tag prospects'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user wants to automate LinkedIn outreach, run Dux-Soup campaigns, or manage Dux-Soup profile data.'

Mirror the product's spelling consistently ('Dux-Soup' vs 'Dux Soup') so trigger matching is reliable.

Dimension	Reasoning	Score
Specificity	The description names the Dux Soup domain but its actions ('Manage data, records, and automate workflows') are generic verbs with no concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than the more concrete level 3.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' clause are present; it avoids the level-3 cap because the trigger guidance is explicit, but the 'what' is vague enough to keep it below level 5.	4 / 5
Trigger Term Quality	It includes the natural term 'Dux Soup' and the trigger 'interact with Dux Soup data', but offers no synonyms or common variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Dux Soup app gives it a clear niche with low conflict risk, but the generic action phrasing ('manage data, records') leaves minor overlap with other data-management skills, so it sits at level 4 rather than 5.	4 / 5
	Total	13 / 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/dux-soup/SKILL.md
Commit: f484c82

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