Name: recruit-crm
Rating: 64 (1 reviews)
Author: membranedev

recruit-crm

Recruit CRM integration. Manage Candidates, Jobs, Companies, Users, Notes, Files and more. Use when the user wants to interact with Recruit CRM data.

Quality

76%

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

Quality

Content

75%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.

Highly actionable content with executable commands and a solid connection state-machine, weakened by some redundancy and mild numbering incoherence. Organization is good but could push detail into reference files.

Suggestions

Merge the redundant "Searching for actions" and "Popular actions" sections into one, keeping a single canonical `action list --intent` example.

Fix the step numbering: either label a clear "Step 2" heading or replace "Skip to Step 2" / "1b" with descriptive section links.

Trim the opening paragraph that explains what Recruit CRM is, and consider moving the clientAction type enumeration and request flags table into a reference file to reduce inline length.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but the opening paragraph explains what Recruit CRM is and the "Searching for actions" and "Popular actions" sections redundantly repeat the same `action list --intent` invocation.	3 / 5
Actionability	Fully executable, copy-paste ready commands for install, login, connection, action list/run, and proxy, plus a concrete flags table covering the common cases.	5 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with a polling/state feedback loop (BUILDING, CLIENT_ACTION_REQUIRED), but "Skip to Step 2" references an unlabeled Step 2 and the "1b" numbering breaks the sequence.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers and no nested references, but at ~145 lines some material (clientAction enumeration, flags reference) could live in a separate file rather than inline.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A clear, well-targeted description that names the product and its core entities with an explicit "Use when" trigger. It is strong on distinctiveness but could list more varied actions and more concrete usage scenarios.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete entities to manage ("Candidates, Jobs, Companies, Users, Notes, Files"), but relies on a single verb ("Manage") with a vague "and more" tail rather than distinct actions.	4 / 5
Completeness	Explicitly answers "what" (manage Recruit CRM entities) and "when" ("Use when the user wants to interact with Recruit CRM data"), but the trigger could be more scenario-specific.	4 / 5
Trigger Term Quality	Good coverage of natural terms a recruiter would say (Candidates, Jobs, Companies, Notes, Files) plus the product name, though a few common synonyms/scenarios are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly named product (Recruit CRM) with domain-specific triggers (Candidates, Jobs, pipeline), giving it a distinct niche with minimal conflict risk.	5 / 5
	Total	17 / 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/recruit-crm/SKILL.md
Commit: f484c82

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