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

Blog Docs Log in Get started

recruitee

Recruitee integration. Manage Companies. Use when the user wants to interact with Recruitee 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/recruitee/SKILL.md

Quality

Content

63%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 delivers strong executable guidance and a well-sequenced connection workflow with state-based feedback loops, but it carries explanatory padding and inlines a bulky actions reference that would benefit from being split out. The dangling "Step 2" label is a small navigation wart.

Suggestions

Move the Popular actions table into a separate reference file (e.g. references/actions.md) and link to it from the body, keeping only a few representative examples inline.

Trim the opening paragraph that defines what an ATS is and what recruiters do; Claude already knows this — lead with what the skill does.

Relabel the dangling "Step 2" reference (e.g. add an explicit "### Step 2: Search for actions" header) so the workflow's cross-references resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening "cloud-based applicant tracking system (ATS) designed to streamline and automate the hiring process" paragraph explains concepts Claude already knows, and the ~20-row Popular actions table is bulk reference that pads the file.	3 / 5
Actionability	Copy-paste ready commands appear throughout (install, login, connection ensure, action list/run, request with a flags table), with only minor placeholder gaps (<actionId>, CONNECTION_ID).	4 / 5
Workflow Clarity	The install→authenticate→connect→poll-for-ready→search→run sequence is clear and includes a genuine feedback loop (poll state, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED, re-poll after user action); the main gap is the dangling "skip to Step 2" reference with no labeled Step 2.	4 / 5
Progressive Disclosure	Section structure is reasonable, but the large Popular actions reference table is inlined rather than split into a separate file, and the skill references no external files at all despite being well over 50 lines.	3 / 5
	Total	14 / 20 Passed

Description

61%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 names the niche product and includes a usable trigger clause, but its action list is thin and generic, and it lacks the synonym-rich trigger terms users would naturally say. Notably, "Manage Companies" does not reflect the candidate/offer/job entities the body actually exposes.

Suggestions

Replace the generic "Manage Companies" with the concrete entities the skill exposes, e.g. "Manage candidates, offers, jobs, and users in Recruitee."

Broaden the trigger clause with natural synonyms users say: "Use when the user wants to manage recruiting, hiring, candidates, job offers, or ATS data in Recruitee."

Add file/record-level trigger terms (e.g. candidates, applications, pipeline) so the description surfaces the most common user intents.

Dimension	Reasoning	Score
Specificity	The phrase "Recruitee integration. Manage Companies." names the domain but offers only one generic action ("Manage Companies"), matching the anchor for minimal/generic actions rather than the multi-action anchors.	2 / 5
Completeness	Both a "what" ("Recruitee integration. Manage Companies.") and a "when" ("Use when the user wants to interact with Recruitee data") are present, but the trigger clause is generic rather than packed with concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Recruitee data" surfaces the core product keyword but omits common synonyms and variations a user would say (hiring, recruiting, ATS, candidates, jobs, offers).	3 / 5
Distinctiveness Conflict Risk	Recruitee is a named niche ATS, and the trigger is tied directly to that product, so overlap with other skills is minimal.	5 / 5
	Total	14 / 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/recruitee/SKILL.md
Commit: f484c82

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