Name: eightfold
Rating: 53.6 (1 reviews)
Author: membranedev

eightfold

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

Quality

60%

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

Quality

Content

60%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 real, executable Membrane CLI commands and a connection workflow that includes genuine state-check validation and a poll-after-action feedback loop. Its main weakness is conciseness: a large, low-value concept-name list and minor redundancy pad the token budget without adding capability.

Suggestions

Remove the ~50-item 'Eightfold Overview' concept bullet list and the filler line 'Use action names and parameters as needed' — this is padding that Claude gains nothing from.

Fix the broken step numbering ('#### 1b.' with no 1a, and references to an undefined 'Step 2') so the connection workflow reads as a coherent numbered sequence.

De-duplicate the action-discovery guidance: the 'Popular actions' section repeats the `action list --intent=QUERY` command already shown under 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	A ~50-item bullet list of generic concept names (User, Profile, Help, Support, Settings, Logout, etc.) under 'Eightfold Overview' plus the filler 'Use action names and parameters as needed' is a major padded section, and the 'Popular actions' section repeats the earlier action-list command, matching 'Noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	Concrete, executable commands are provided throughout (npm install, membrane login, connection ensure, action list/run with --input JSON, request proxy with a flag table), matching 'Mostly executable guidance; concrete code or commands with minor gaps' — the residual placeholders (CONNECTION_ID, /path/to/endpoint) keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	The connection workflow is a clear sequence with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll again after the user authenticates), matching 'Clear sequence with most checkpoints present; minor validation gaps' — the gap is the broken numbering ('1b', an undefined 'Step 2').	4 / 5
Progressive Disclosure	The file is well-sectioned with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and relies on dynamic runtime action discovery instead of a static API reference, so no external files are needed; minor organization gaps (the concept-list bloat and stray numbering) keep it just below a clean 5, matching 'Good structure; most content is appropriately placed; minor organization gaps'.	4 / 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 is clear and appropriately triggered with an explicit 'Use when' clause and a distinctive brand anchor, but its capability list is generic ('manage data, records') and it omits the natural use-case vocabulary (recruiting, talent, hiring) that users would actually say.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Eightfold capabilities such as searching candidates, managing job postings, and pulling applicant pipeline data.

Broaden the trigger terms to include natural user phrasing like 'recruiting', 'talent management', 'candidates', 'job applications', or 'hiring' rather than only 'interact with Eightfold data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Eightfold integration') but the actions listed ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It has an explicit 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger ('Use when the user wants to interact with Eightfold data'), but the 'when' could be more specific, matching 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	'Eightfold' and 'interact with Eightfold data' are relevant keywords, but it misses common natural variations a user would actually say (recruiting, talent, candidates, jobs, hiring), so it matches 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The Eightfold brand name makes the trigger highly specific and unlikely to overlap with other skills, matching 'Clear niche with distinct triggers; minimal conflict risk'.	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/eightfold/SKILL.md
Commit: f484c82

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