Name: ashby
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ashby

Ashby integration. Manage Persons, Users, Roles. Use when the user wants to interact with Ashby data.

Quality

66%

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

Quality

Content

67%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 strong command examples and a clear, validated connection workflow. Its main weaknesses are an unnecessary marketing intro and a monolithic structure with no reference files to house the sizable actions catalog.

Suggestions

Remove the marketing opening paragraph ("Ashby is a recruiting software platform...") and keep only operational guidance Claude needs.

Move the Popular actions table and proxy option flags into a separate reference file (e.g. references/actions.md) and link to it from SKILL.md to improve progressive disclosure.

Add a validation/verification step after destructive CRUD actions (create/update/delete via action run or proxy) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused, but opens with marketing padding ("Ashby is a recruiting software platform used by high-growth companies... with a focus on data and analytics") and a few explanatory asides Claude does not need, so it could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (login, connection ensure, action list/run with --input JSON, request proxy) plus a popular-actions table with keys, with only minor gaps such as placeholder action IDs and CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow is a well-sequenced state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling and a re-poll feedback loop after user action, but the referenced "Step 2" is not explicitly labeled and CRUD/proxy operations lack verification checkpoints.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but the file is a single ~170-line document with a large 20-row actions table and proxy options that could be split into separate reference files; no bundle files exist to offload detail.	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 is clear and distinct thanks to naming a specific product, with an explicit "Use when" trigger satisfying completeness. It is held back by a single generic verb ("Manage") and limited trigger-term variation.

Suggestions

Replace the generic "Manage Persons, Users, Roles" with distinct concrete actions, e.g. "List, create, and update applications, candidates, jobs, and users."

Expand the trigger clause to include natural synonyms users say, e.g. "Use when the user wants to query or update Ashby recruiting data — candidates, applications, jobs, or offers."

Dimension	Reasoning	Score
Specificity	"Manage Persons, Users, Roles" names the Ashby domain and a few entities, but uses a single generic verb ("Manage") over nouns rather than listing distinct concrete actions like create/list/update, so it is not comprehensive.	3 / 5
Completeness	It states both what ("Ashby integration. Manage Persons, Users, Roles") and when ("Use when the user wants to interact with Ashby data"), but the "when" clause is somewhat generic and could be more specific, matching the anchor where both are present yet the trigger could be sharper.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Ashby data" supplies the core natural term ("Ashby") but misses common synonyms a user might say such as recruiting, ATS, candidates, or jobs.	3 / 5
Distinctiveness Conflict Risk	Ashby is a specific named product with an explicit trigger ("interact with Ashby data"), giving it a clear niche with minimal overlap risk against other skills.	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/ashby/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.