Name: homerun
Rating: 60.8 (1 reviews)
Author: membranedev

homerun

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

Quality

71%

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

Quality

Content

82%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 executable commands and a clear, well-instrumented connection workflow, supported by good section structure; it loses points only for minor verbosity, an undefined 'Step 2' reference, and light redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a useful state-handling breakdown, but has minor trimming opportunities (e.g. "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection"), fitting the 4-anchor rather than the fully lean 5-anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests with flag tables, matching the 5-anchor for copy-paste-ready guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with polling and state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, then re-poll), but the 'Step 2' label is referenced without being defined and action-run lacks a post-run validation checkpoint, matching the 4-anchor with minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) in a single self-contained file with no nested references, but the inlined clientAction reference and redundant action-list mentions in two sections leave minor organization gaps, fitting the 4-anchor.	4 / 5
	Total	17 / 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 cleanly identifies its niche and includes an explicit Use-when clause, but the capability list is generic (manage data, records, automate workflows) and the trigger terms lack synonyms or concrete domain verbs.

Suggestions

Replace generic verbs with concrete Homerun actions, e.g. "Post jobs, track candidates, and manage applications in Homerun."

Add natural trigger synonyms users would say, such as hiring, applicants, job postings, or candidate pipelines.

Tighten the 'when' clause to name concrete triggers, e.g. "Use when the user wants to post jobs, review applicants, or track candidates in Homerun."

Dimension	Reasoning	Score
Specificity	The description names the Homerun domain but its actions are minimal and generic — "Manage data, records, and automate workflows" are vague verbs with no concrete operations (e.g. post jobs, track candidates), matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires concrete actions.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Homerun data") are present, but the 'when' is generic and could be more specific, matching the 4-anchor rather than the fully concrete 5-anchor.	4 / 5
Trigger Term Quality	It includes the natural keyword "Homerun" and the phrase "interact with Homerun data", but offers no synonyms or common variations a user might say (e.g. hiring, applicants, jobs, candidates), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Homerun integration" targets a clear, named niche (a specific ATS) with a distinct trigger ("interact with Homerun data"), giving minimal conflict risk with other skills, matching the 5-anchor.	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/homerun/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.