Name: ihomefinder
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ihomefinder

IHomefinder integration. Manage Leads, Users, Filters. Use when the user wants to interact with IHomefinder data.

Quality

61%

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

Quality

Content

61%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 concrete CLI commands, real flags, and a useful action table, plus a well-structured connection workflow with state-based checkpoints. The main gaps are mild verbosity in framing prose, destructive actions lacking validation guidance, and the large action table being inline rather than offloaded to a reference file.

Suggestions

Trim framing prose that Claude does not need (the 'Real estate professionals use it to...' sentence and the 'so you can focus on the integration logic' aside) to tighten token efficiency.

Add a validation/confirmation checkpoint before destructive actions (e.g., 'Before running delete-subscriber, confirm the subscriber ID with the user and verify via get-subscriber') to lift the workflow-clarity cap.

Consider moving the full popular-actions table into a references file (e.g., ACTIONS.md) and keeping only the most common few inline, with a clearly signaled link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary asides Claude does not need (e.g., 'Real estate professionals use it to generate leads, showcase listings...' and 'so you can focus on the integration logic rather than auth plumbing'), fitting the 3-anchor for mostly efficient content that could be tightened rather than the lean 4-anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands with real flags throughout (login, connection ensure, action list/run, request) and a popular-actions table with keys, but several commands retain unfilled placeholders (CONNECTION_ID, <id>, <actionId>) requiring substitution, fitting the 4-anchor for mostly executable guidance with minor gaps rather than fully turnkey 5.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checkpoints and a polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive operations (delete-subscriber) in the action table with no validation or confirmation guidance before running them, which caps workflow clarity at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Working with IHomefinder, Popular actions, Best practices) with no nested references and no bundle files, but the large 20-row popular-actions table is inline content that could arguably live in a separate reference file, fitting the 4-anchor for good structure with minor organization gaps rather than the ideal split 5-anchor.	4 / 5
	Total	14 / 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 is well-structured with an explicit 'Use when' trigger and a distinct product-specific niche, scoring well on completeness and distinctiveness. Its main weakness is the single generic verb 'Manage' covering the entity list, which limits specificity, and a somewhat generic trigger clause.

Suggestions

Replace the generic 'Manage' with concrete verbs (e.g., 'Create, update, and delete Leads and Subscribers; search listings; manage Users and Filters') to lift specificity.

Expand the trigger clause with concrete scenarios (e.g., 'Use when the user wants to list or create leads/subscribers, search property listings, or manage market/office/agent data').

Add common synonym triggers users might say (e.g., 'leads', 'subscribers', 'property listings', 'IDX') alongside 'IHomefinder'.

Dimension	Reasoning	Score
Specificity	Names the IHomefinder domain and lists concrete entities to 'Manage' (Leads, Users, Filters), but the single generic verb 'Manage' applied to three entities is not a comprehensive action list, landing at the anchor for naming domain plus a few concrete actions rather than the more exhaustive 4-anchor.	3 / 5
Completeness	Explicitly answers both 'what' ('IHomefinder integration. Manage Leads, Users, Filters.') and 'when' ('Use when the user wants to interact with IHomefinder data'), but the 'when' clause is generic ('interact with IHomefinder data') and could be more specific, fitting the 4-anchor for having both with room to sharpen the trigger.	4 / 5
Trigger Term Quality	Includes the natural product-name trigger ('IHomefinder') and an explicit 'Use when the user wants to interact with IHomefinder data' clause, but lacks synonym variations or alternative phrasings a user might say, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The unique product name 'IHomefinder' gives a clear niche with minimal conflict risk, but the generic CRM entities (Leads, Users, Filters) carry minor overlap risk with other CRM/contact skills, placing it at the 4-anchor rather than the fully distinct 5-anchor.	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/ihomefinder/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.