Name: talend
Rating: 64.8 (1 reviews)
Author: membranedev

talend

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

Quality

78%

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

Quality

Content

82%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 highly actionable, packed with executable CLI commands and a well-structured connection state machine with polling feedback loops. Minor over-explanation and a dangling 'Step 2' reference keep it just below the top band on conciseness and workflow clarity.

Suggestions

Define or remove the dangling 'Step 2' reference — either add a labeled '## Step 2: Run an action' section or reword 'skip to Step 2' to point to the concrete 'Searching for actions' section.

Trim rhetorical filler such as '— so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven prose, but contains minor over-explanation such as '— so you can focus on the integration logic rather than auth plumbing' and a few explanatory sentences that Claude could infer, keeping it just below the top band.	4 / 5
Actionability	Fully executable, copy-paste-ready CLI commands cover the common cases end to end — install, login (interactive and headless), connection ensure/get with --wait, action list/run with JSON input, and request proxying with a flag table — with concrete examples for each.	5 / 5
Workflow Clarity	The connection setup has an explicit state machine with polling feedback loops (BUILDING → READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after user action), but it references 'skip to Step 2' with no corresponding Step 2 section defined, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	A single well-organized file with clearly headed sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and no nested references; at ~130 lines it exceeds the 50-line simple-skill exception, so it stops just short of 5 despite good structure.	4 / 5
	Total	17 / 20 Passed

Description

73%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 Talend domain and lists concrete managed entities with an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is held back from the top band by the single generic verb 'Manage' and a somewhat vague trigger clause.

Suggestions

Replace the single generic 'Manage' with differentiated concrete verbs (e.g. 'Create, update, query, and delete Persons, Organizations, Leads, Deals, Activities, and Notes') to lift specificity.

Sharpen the 'Use when' clause with concrete trigger phrases users actually say (e.g. 'Use when the user wants to query Talend leads, log activities, or sync organizations').

Dimension	Reasoning	Score
Specificity	Names the domain ('Talend integration') and several concrete entities ('Persons, Organizations, Leads, Deals, Activities, Notes'), but every action collapses into the single generic verb 'Manage', so distinct concrete actions are minimal rather than comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage Persons, Organizations, Leads, Deals, Activities, Notes') and 'when' ('Use when the user wants to interact with Talend data'), but the 'when' clause is generic and lacks concrete trigger variations, so it is not a 5.	4 / 5
Trigger Term Quality	Good coverage of natural terms users would say — 'Talend', 'Talend data', plus the entity names (Leads, Deals, etc.) — but common synonyms or shorthand for the platform are absent, so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'Talend integration' niche plus entity-specific triggers make this clearly distinguishable from other skills with minimal risk of triggering for the wrong skill.	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/talend/SKILL.md
Commit: f484c82

Reviewed: ~23 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.