CtrlK
BlogDocsLog inGet started
Tessl Logo

rentcast

RentCast integration. Manage Properties, Contacts, Leads. Use when the user wants to interact with RentCast data.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/rentcast/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 CLI commands and a solid connection-readiness feedback loop. It is held back by some redundant/over-explanatory prose and a broken 'Step 2' cross-reference.

Suggestions

Remove the duplicate action-list instruction in 'Popular actions' (already covered in 'Searching for actions') and trim the RentCast marketing description and 'auth plumbing' commentary.

Define and label 'Step 2' (or replace the 'skip to Step 2' reference with the actual section name) and clean up the '1b' numbering so the connection workflow is a coherent numbered sequence.

Consider moving the proxy flag table and detailed connection-state handling into a reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Mostly concrete commands, but it includes unnecessary explanation (what RentCast is, 'so you can focus on the integration logic rather than auth plumbing') and redundant sections ('Popular actions' repeats the 'Searching for actions' command), fitting anchor 3 over 4.

3 / 5

Actionability

Provides copy-paste-ready executable commands across install, login, connection, action search, action run with JSON input, and proxy requests, covering the common cases comprehensively.

5 / 5

Workflow Clarity

There is a clear sequence with an explicit validation feedback loop (poll connection state; handle READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-poll after user action), but the dangling 'Step 2' reference and loose '1b' numbering prevent a 5.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized section headers and no nested references, giving easy navigation; a ~140-line body with all detail inline (proxy flag table, connection-state handling) has minor organization gaps but no structure failures.

4 / 5

Total

16

/

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 is third-person, names the RentCast niche clearly, and includes both a 'what' and 'when' clause. Its main weakness is the generic verb 'Manage' and a trigger clause that could list more concrete scenarios.

Suggestions

Replace the generic verb 'Manage' with specific actions per entity (e.g., 'Create and update Properties, manage Contacts, track Leads').

Expand the 'Use when' clause with concrete trigger phrases (e.g., 'when the user mentions RentCast, rental properties, tenant leads, or contacts').

Add file/identifier synonyms if RentCast data is referenced by other natural terms users might say.

DimensionReasoningScore

Specificity

Names the domain (RentCast) and lists entity areas ('Manage Properties, Contacts, Leads'), but the single generic verb 'Manage' applied to all three is minimal rather than comprehensive, fitting anchor 3 better than 4.

3 / 5

Completeness

Provides a clear 'what' ('RentCast integration. Manage Properties, Contacts, Leads.') and an explicit 'when' ('Use when the user wants to interact with RentCast data.'), but the trigger clause is somewhat generic rather than listing concrete trigger phrases, so it stops short of anchor 5.

4 / 5

Trigger Term Quality

'RentCast', 'Properties, Contacts, Leads', and 'RentCast data' give good keyword coverage of natural terms a user would say, though a few synonyms or context variations are missing.

4 / 5

Distinctiveness Conflict Risk

'RentCast' is a unique proper-noun niche with distinct triggers, giving minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.