Name: tellent
Rating: 59.2 (1 reviews)
Author: membranedev

tellent

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

Quality

68%

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

Quality

Content

71%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 with comprehensive executable commands and a well-validated connection workflow, but it carries some platform padding and inlines reference-grade detail that would benefit from separation into bundle files. Trimming explanatory prose and splitting out the state-machine and flags reference would improve both conciseness and progressive disclosure.

Suggestions

Remove the opening 'Tellent is a talent management platform...' paragraph and other marketing phrasing; assume Claude knows what the platform is or state only the integration-relevant facts.

Move the clientAction state-machine reference and the proxy flags table into a separate references file (e.g. references/proxy.md) and link to it from SKILL.md to improve progressive disclosure.

Fix the dangling 'Step 2' reference and align step numbering so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but includes an unnecessary platform-explanation paragraph ('Tellent is a talent management platform used by HR departments... streamline their hiring process, manage employee performance...') and marketing phrasing ('fastest way to get a connection', 'burn less tokens') that could be trimmed, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, connection get --wait, action list/run, request with a complete flags table), covering the common integration cases, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	Presents a clear install → login → connect → wait → search → run sequence with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the dangling 'skip to Step 2' reference and inconsistent numbering (e.g. '#### 1b') leave minor gaps, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The body has clear section headers but no bundle files; content that could live in separate references (the full clientAction state machine, the proxy flags table, popular actions) is inlined into a single ~140-line document, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 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 is well-formed with an explicit 'Use when' clause and a distinctive brand anchor, but its action list and trigger terms are generic rather than concrete and platform-specific. Strengthening it with Tellent-specific entities and scenarios would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Tellent operations, e.g. 'search candidates, manage job applications, and update job postings'.

Add natural trigger terms users would say, such as 'candidates', 'job postings', 'applications', or 'Tellent API'.

Expand the 'when' clause with concrete scenarios, e.g. 'Use when the user wants to search candidates, review job applications, or automate Tellent workflows'.

Dimension	Reasoning	Score
Specificity	Names the Tellent domain plus several actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete platform-specific operations, fitting the 'names domain and 1-2 concrete actions' anchor without reaching the specific-action coverage of 4.	3 / 5
Completeness	Explicitly answers 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Tellent data'), but the 'when' is generic rather than listing concrete trigger scenarios, matching 'both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	Includes the natural trigger phrase 'Use when the user wants to interact with Tellent data' and the brand keyword 'Tellent', but misses common synonyms, variations, or specific entity terms (candidates, jobs, applications) a user might say, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Tellent' brand name anchors a clear niche with a distinct, brand-specific trigger ('interact with Tellent data'), giving minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.	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/tellent/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.