Name: applicantstack
Rating: 60 (1 reviews)
Author: membranedev

applicantstack

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

Quality

70%

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

Quality

Content

78%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 is highly actionable with copy-paste-ready Membrane CLI commands and a clear connection workflow including state-polling checkpoints, and it is well-structured for a single-file skill. Its main weakness is conciseness — an unnecessary product-marketing intro and an unpurposed feature list compete for context tokens.

Suggestions

Cut or compress the intro marketing prose ("ApplicantStack is an applicant tracking system that helps businesses manage their hiring process...") since Claude does not need the recruiting-industry background.

Remove or repurpose the long bulleted feature list (Applicants/Stages/Jobs/Users/...) unless each item is tied to a concrete action or command.

Fix the dangling "Step 2" references by adding explicit numbered Step 1/Step 2 headings, and expand CONFIGURATION_ERROR recovery beyond "check the error field" (e.g. re-run ensure, inspect error, retry).

Dimension	Reasoning	Score
Conciseness	Most of the body is lean executable CLI usage, but the marketing-style intro ("ApplicantStack is an applicant tracking system that helps businesses...") and the long unpurposed feature list pad tokens Claude doesn't need, fitting "mostly efficient with some unnecessary explanation."	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the core workflows (install, login, connection ensure, action list/run with JSON input, proxy requests) plus a concrete flag table, covering the common cases.	5 / 5
Workflow Clarity	The connection sequence is clearly laid out with state-polling checkpoints and branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, but broken "Step 2" references (no Step 1/2 headings exist) and thin error-recovery guidance for CONFIGURATION_ERROR leave minor gaps.	4 / 5
Progressive Disclosure	A single-file skill with clear, well-organized section headers and appropriately self-contained overview-level content, so navigation is easy with no need for external file references.	5 / 5
	Total	17 / 20 Passed

Description

62%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 answers both what and when with an explicit "Use when..." clause and a named product, but its action language is generic and it underuses the natural ATS trigger terms (applicants, jobs, candidates) that appear in the body. Distinctiveness is anchored mostly by the product name rather than rich domain-specific triggers.

Suggestions

Replace generic verbs with concrete ATS actions, e.g. "Post jobs, track candidates, manage offers and requisitions, and automate recruiting workflows."

Expand the "Use when..." clause with natural trigger phrases: "Use when the user wants to manage applicants, post jobs, track candidates, or automate hiring workflows in ApplicantStack."

Add file/record-type keywords users actually mention (applicants, candidates, jobs, offers, requisitions) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the ApplicantStack domain plus a couple actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete ATS-specific operations like posting jobs or tracking candidates, fitting the 1-2 concrete-actions anchor.	3 / 5
Completeness	Explicitly states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with ApplicantStack data"), but the trigger could be more specific with concrete phrases.	4 / 5
Trigger Term Quality	Includes "ApplicantStack" and a "Use when..." clause, but omits the natural user vocabulary (applicants, candidates, jobs, hiring, recruiting) that the body itself surfaces, leaving only some relevant keywords.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product ApplicantStack creates a clear niche with minimal conflict risk, though the generic "manage data/records" phrasing leaves minor overlap with other data-management skills.	4 / 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/applicantstack/SKILL.md
Commit: f484c82

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