CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

property-listings

Present property and rental listings as desktop cards.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 skill body is an exemplary instruction-only SKILL.md: concise, fully actionable with concrete commands, a complete schema table and example, explicit validation checkpoints, and a render-failure recovery path. Its self-contained structure is appropriate for a single-task presentation recipe that needs no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: every section earns its place — a one-line scope boundary ("This is a presentation recipe, not a listing search service or an investment valuation"), concrete install/load commands, a compact field table, one explicitly-labeled fictional example, and dense pitfalls with renderer limits. There is no concept over-explanation or padding, matching anchor 5.

5 / 5

Actionability

Fully actionable: copy-paste install command ("hermes skills install official/productivity/property-listings"), a complete field table specifying shapes and required/optional semantics, a full example JSON exercising every field, and hard numeric limits (24 properties, 40 images, 12 entries, 400-char truncation). Matches anchor 5 — specific examples cover the common cases.

5 / 5

Workflow Clarity

The Procedure is a clear 4-step sequence with an explicit validation checkpoint ("Check the JSON before sending") and the Verification section provides a feedback loop for error recovery ("If the card fails to render, validate the fence language and JSON, then preserve a readable Markdown fallback"). Even though this is a batch-capable operation (up to 24 properties per fence), validation steps are present, matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the skill is a self-contained, well-sectioned single-task recipe; nothing in the body belongs in a separate file. Per the simple-skill guidance, well-organized sections with clear headers and no external-reference needs warrant anchor 5.

5 / 5

Total

20

/

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 concise, third-person, and states a clear concrete capability, but it omits any explicit 'when to use' trigger guidance and lacks common synonyms (apartments, homes, real estate) that would improve discovery and completeness. It is a solid mid-tier description that would benefit most from an explicit Use-when clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when presenting property or rental search results, comparing a shortlist of apartments or homes, or re-ranking real-estate listings."

Include natural synonyms such as "apartments", "homes", or "real estate" alongside "property and rental listings" to broaden trigger-term coverage.

Mention the key actions beyond presenting (e.g., comparing shortlists and re-ranking properties) to raise specificity and completeness.

DimensionReasoningScore

Specificity

"Present property and rental listings as desktop cards" names the domain and one concrete action with a specific output form, matching anchor 3 (domain + 1-2 concrete actions, not comprehensive). It is above anchor 2 because the concrete output ('desktop cards') is more specific than generic processing, but below anchor 4 because only a single action is described.

3 / 5

Completeness

The 'what' is clear (present property/rental listings as desktop cards) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This exactly matches anchor 3 ('clear what but when is missing'), not 4 since 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "property", "rental", "listings" — giving good core keyword coverage, but misses common variations like "apartments", "homes", or "real estate". Fits anchor 4 ('good keyword coverage; a few natural terms missing'), not 5 which requires comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The property/rental listing niche is clear and distinct with concrete triggers, but 'desktop cards' could overlap with other card-formatting or presentation skills. Mostly distinct with minor overlap risk against closely related skills — anchor 4, not 5 since the card-rendering surface is shared with other presentation skills.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/productivity/property-listings/SKILL.md

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.