Name: talentlyft
Rating: 58.4 (1 reviews)
Author: membranedev

talentlyft

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

Quality

67%

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

Quality

Content

68%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 strongly actionable with concrete, executable Membrane commands and a clear install-to-run flow, but it loses points on conciseness from concept-explanation padding and on workflow clarity from missing validation checkpoints for destructive proxy calls. Adding a verify-before-destructive-call step and trimming explanatory prose would raise both.

Suggestions

Add a validation/confirmation checkpoint before destructive proxy requests (e.g. POST/PUT/DELETE) — confirm the target with the user or dry-run first.

Trim concept-explanation padding like 'so you can focus on the integration logic rather than auth plumbing' and the recruiting-platform introductory paragraph.

Fix step numbering (the 'Step 2' reference has no matching 'Step 1') or replace it with consistent sequential headers.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but includes some padding ('so you can focus on the integration logic rather than auth plumbing') and an opening paragraph explaining what a recruiting platform is.	3 / 5
Actionability	Commands are concrete and copy-paste ready (install, login, connection ensure, action run with --input, request with flags), and the proxy flags table covers the common cases comprehensively.	5 / 5
Workflow Clarity	A clear install-to-run sequence with enumerated state transitions exists, but destructive proxy methods (DELETE/PUT) lack validation checkpoints and step numbering is inconsistent ('Step 2' referenced with no Step 1).	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear headers and no nested-reference problem, though some content (the clientAction field breakdown, flags table) could move to a reference file to keep the overview leaner.	4 / 5
	Total	15 / 20 Passed

Description

66%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 pairs a 'what' and a 'when' clause tied to a distinct product niche, but the capabilities and trigger terms stay generic ('data, records', 'interact with TalentLyft data') rather than naming concrete TalentLyft objects. Tightening the action list to TalentLyft-specific entities would lift specificity and trigger quality.

Suggestions

Replace generic verbs with TalentLyft-specific actions, e.g. 'Search candidates, manage job applications, and send recruiting emails'.

Add concrete trigger terms recruiters would say, such as 'candidates', 'job postings', 'applications', or 'applicant tracking'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage candidates, jobs, or applications in TalentLyft'.

Dimension	Reasoning	Score
Specificity	Names the TalentLyft domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than TalentLyft-specific (candidates, jobs, applications).	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with TalentLyft data') are present, though both could be more concrete.	4 / 5
Trigger Term Quality	The natural trigger is essentially the product name ('interact with TalentLyft data'), but common recruiter phrasings like 'candidates' or 'job applications' are missing.	3 / 5
Distinctiveness Conflict Risk	The named product (TalentLyft) creates a clear niche with a distinct trigger and minimal conflict risk with other 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/talentlyft/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.