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

recruiterflow

Recruiterflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Recruiterflow 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/recruiterflow/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 content is highly actionable with executable CLI commands and a solid connection-state feedback loop, but it loses workflow_clarity to the missing post-action validation and an undefined 'Step 2' reference, and carries minor redundancy between the two action-discovery sections.

Suggestions

Add a validation/verification step after 'membrane action run' and 'membrane request' (e.g. check the output/error field before proceeding) to lift the workflow_clarity cap.

Fix the broken step numbering: 'Step 2' is referenced but never labeled, and '1b. Wait for the connection' has no matching '1a'.

Replace the redundant 'Popular actions' section with a few concrete Recruiterflow action examples (e.g. list candidates, create a note) instead of repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code blocks and commands with brief procedural prose, with only minor redundancy (the 'Popular actions' section repeats the discovery command from 'Searching for actions'), so it fits anchor 4 rather than the fully lean 5.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action discovery, action run, and proxy requests with a flag table, but 'Popular actions' promises named actions yet only re-states the discovery command, leaving a minor gap that keeps it at 4.	4 / 5
Workflow Clarity	The connection workflow has a real feedback loop (poll state -> handle CLIENT_ACTION_REQUIRED -> re-poll until READY), but running/proxying actions on live data lacks any validation or verification step; per the destructive/batch cap this holds at 3, and the dangling 'Step 2' reference with no labeled Step 2 confirms the gap.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clear section headers (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with easy navigation; it is over 50 lines and could arguably split the verbose connection-state reference, so it sits at anchor 4 rather than 5.	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 has an explicit trigger clause and a highly distinctive proper-noun target, but its capability list ('manage data, records, automate workflows') is generic and lacks the concrete Recruiterflow-specific actions that would lift specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete Recruiterflow operations, e.g. 'search candidates, update client records, and trigger hiring workflows'.

Add natural trigger synonyms users actually say, such as 'candidates', 'clients', 'pipeline', or 'ATS'.

Tighten the 'what' to name the specific entities (candidates, clients, jobs) the skill manipulates rather than abstract 'data and records'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Recruiterflow integration') and three action areas ('Manage data, records, and automate workflows'), but the actions are generic categories rather than concrete operations like 'create candidates' or 'update pipelines', so it sits at anchor 3 and not 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Recruiterflow data') are present; the when clause is explicit so it clears the 3-cap, but the what is generic enough to keep it at 4 rather than 5.	4 / 5
Trigger Term Quality	The key natural term 'Recruiterflow' and 'Recruiterflow data' are present, but it misses common variations a user would say (candidates, clients, pipeline, ATS, recruiting), placing it at anchor 3 rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	'Recruiterflow' is a specific proper-noun SaaS app with a clear niche (recruiting ATS/CRM), so the trigger is highly distinctive with minimal conflict risk against other skills, matching anchor 5.	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/recruiterflow/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.