Name: greenhouse-harvest
Rating: 59.2 (1 reviews)
Author: membranedev

greenhouse-harvest

Greenhouse Harvest integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Greenhouse Harvest data.

Quality

68%

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

Quality

Content

63%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 action-oriented with executable CLI commands and a clear connection-state feedback loop, making it strong on actionability and workflow clarity. It is held back by conceptual padding plus an irrelevant domain-model bullet list, and by having no progressive file structure.

Suggestions

Remove the 'Greenhouse Harvest Overview' bullet tree (Harvest/Field/Crop/Farmer/Vehicle/Task/Report) — it is unrelated to the integration and adds noise.

Trim explanatory filler like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need.

Move the proxy flag table and clientAction schema into a separate reference file referenced from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient copy-paste commands, but it includes conceptual padding Claude already knows (e.g. 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing') and a 'Greenhouse Harvest Overview' bullet tree listing Harvest/Field/Crop/Farmer that is irrelevant filler.	3 / 5
Actionability	It provides concrete, executable membrane CLI commands with flags for install, auth, connection ensure, action list/run, and proxy requests, covering the common cases with copy-paste-ready syntax; minor gaps such as leaving CONNECTION_ID as a placeholder are acceptable.	4 / 5
Workflow Clarity	The connection setup is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance, a genuine feedback loop; it loses a point because later sections (searching actions, running actions, proxy) are presented as parallel options rather than one explicit ordered workflow.	4 / 5
Progressive Disclosure	The body is reasonably sectioned but everything is inlined into a single SKILL.md with no bundle files or one-level-deep references, and content that arguably belongs in separate references (the proxy flag table, the clientAction schema) is inline; it is serviceable but not split for discovery.	3 / 5
	Total	14 / 20 Passed

Description

73%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 clearly identifies a specific product niche and includes an explicit 'Use when...' trigger clause, giving it strong completeness and distinctiveness. Its weakness is specificity, since 'Manage' is generic and the concrete actions are implied rather than listed.

Suggestions

Replace the generic verb 'Manage' with 2-3 concrete actions (e.g. 'Create, update, and query Persons, Organizations, and Deals').

Add common synonyms or natural phrasings users might say, such as 'candidates' or 'job postings', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Greenhouse Harvest) and enumerates concrete entity types ('Persons, Organizations, Deals, Leads, Projects, Activities'), but the actions performed on them are generic ('Manage...') rather than specific concrete operations.	3 / 5
Completeness	It states what the skill does ('Manage Persons, Organizations...') and includes an explicit 'Use when the user wants to interact with Greenhouse Harvest data' trigger, satisfying both what and when, though the 'when' is fairly broad.	4 / 5
Trigger Term Quality	It surfaces natural user-facing terms ('interact with Greenhouse Harvest data') plus the domain name itself, which is what a user would say; it lacks synonyms/file extensions but the niche vocabulary is solid.	4 / 5
Distinctiveness Conflict Risk	Greenhouse Harvest is a named, specific product with a clear niche (ATS/HRIS), making it highly distinct from other skills and unlikely to trigger for the wrong one.	5 / 5
	Total	16 / 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/greenhouse-harvest/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.