Name: teamtailor
Rating: 55.2 (1 reviews)
Author: membranedev

teamtailor

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

Quality

62%

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

Quality

Content

67%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 actionable and well-structured with executable Membrane CLI commands and a clear connection workflow, but it carries some explanatory padding and leaves minor workflow gaps around step labeling and destructive-action validation.

Suggestions

Tighten or remove the introductory ATS paragraph and the vague Overview bullets so the body assumes Claude's competence.

Label the referenced 'Step 2' (e.g., rename 'Searching for actions' to 'Step 2: Search for actions') so the skip-to instructions resolve.

Add a brief validation/verification note for create, update, and delete actions (e.g., re-fetch the resource to confirm the change) to close the destructive-operation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some padding such as the introductory ATS explainer, the vague Overview bullets, and 'Use action names and parameters as needed.' that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands throughout (login, connection ensure, action list/run, request) with flag tables and a popular-actions table; minor gaps are placeholders like CONNECTION_ID and the QUERY intent that the user must substitute.	4 / 5
Workflow Clarity	The install → login → connection → search → run sequence is clear with a connection state machine and a poll-after-action feedback loop, but 'Step 2' is referenced without being labeled and destructive actions (create/update/delete) lack validation checkpoints.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and inline reference tables; with no bundle files present the structure is appropriate, though the 20-row popular-actions table and proxy-flags table are bulk content that could live in a reference file.	4 / 5
	Total	15 / 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 answers both what the skill does and when to use it with an explicit trigger, but its capability verbs are generic rather than reflecting Teamtailor-specific actions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Teamtailor actions, e.g. 'Manage job postings, candidates, and job applications, and automate recruitment workflows.'

Broaden the trigger clause to cover natural user phrasings, e.g. 'Use when the user wants to manage Teamtailor recruiting data, candidates, job applications, or job postings.'

Dimension	Reasoning	Score
Specificity	The description names the Teamtailor domain but its actions — 'Manage data, records, and automate workflows' — are generic rather than concrete Teamtailor-specific operations like job postings, candidates, or applications.	2 / 5
Completeness	Both 'what' (Teamtailor integration that manages data/records and automates workflows) and 'when' ('Use when the user wants to interact with Teamtailor data') are present and explicit, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Teamtailor' in an explicit trigger clause, but the phrasing 'interact with Teamtailor data' is limited and offers no variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	'Teamtailor' is a named product giving it a clear niche with minimal conflict risk, but the generic 'manage data, records, and automate workflows' phrasing leaves slight overlap with other integration skills.	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/teamtailor/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.