CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-property-mgmt-us

Runs a small US rental portfolio: tenant screening, lease packets, notices, maintenance workflow and move-out accounting. Use when: Generate state-specific residential lease agreements; Calculate security deposit return deadlines and itemizations; Draft compliant pay-or-quit and entry notices.

Quality

64%

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 ./plugins/nex-finance-property/skills/nex-property-mgmt-us/SKILL.md

The canonical home for this skill is nex-property-mgmt-us in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%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 a marketing-style README, not operational skill guidance: it describes what the skill does and includes one sample notice, but provides no executable workflows, templates, or state-specific data, and acknowledges the actual operational assets are missing from the folder. Structure and the limitations/safety framing are its only real strengths. It needs rewritten step-by-step workflows, bundled or referenced templates/deadline tables, and removal of the promotional and FAQ padding.

Suggestions

Replace the descriptive 'What it does' bullets with concrete sequenced workflows — e.g., screening (application criteria -> adverse action notice), notice drafting (identify state -> select notice type -> verify statutory period -> generate), and move-out accounting (inspection -> itemize deductions -> check state return deadline -> issue statement) — each with an explicit verify-against-current-statute checkpoint.

Bundle or clearly reference the operational assets the body claims to use (notice and lease templates, state deadline tables, addenda checklist) in a references/ directory, since the file itself states 'Scripts, extension source, and templates from the original package are not in this folder'.

Cut the padding: the marketing header, the 'Use cases' section that restates the description, the FAQ that re-describes features, and the paid-catalog footer links consume context without adding instruction.

DimensionReasoningScore

Conciseness

A large share of the body is padding rather than instruction: the marketing header ("Free skill by Nex AI"), the "Use cases" section that restates the description, a four-question FAQ that re-describes features, and a promotional footer linking to a "paid catalog". This matches "noticeably verbose; several unnecessary explanations or padded sections" — not 3, because well over half the tokens are non-operational rather than just "some" unnecessary explanation.

2 / 5

Actionability

The body only describes capabilities ("Builds the tenant screening workflow", "Assembles the lease packet", "It generates a universal core lease") with no steps, commands, templates, criteria, or state deadline data. The single example output and the hint that the skill "asks for your state and city" provide minimal concrete guidance, which keeps it above the "entirely vague, only describes" anchor at 1 but firmly below 3's "some concrete guidance".

2 / 5

Workflow Clarity

No multi-step sequence exists anywhere in the body — the "What it does" bullets name four functional areas but give no order, no checkpoints, and no validation steps (e.g., verifying state statutory deadlines before issuing a notice is only vaguely urged in limitations). This matches the anchor "Steps missing or incoherent; no sequence"; the 2 anchor requires at least a rough sequence, which is absent.

1 / 5

Progressive Disclosure

The body has real section structure (What it does, Use cases, Limitations, Example, Questions), and no references/ or scripts/ bundle exists — the text even admits "Scripts, extension source, and templates from the original package are not in this folder". This sits between anchors: better organized than the 2 anchor's "minimal structure", but it cannot reach 4 because the detailed material this multi-domain skill clearly needs (state law tables, notice templates, screening criteria) is neither inlined nor available in local files — the only links are external marketing URLs.

3 / 5

Total

8

/

20

Passed

Description

87%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 strong: it uses third person, states concrete capabilities across the property-management lifecycle, and pairs them with an explicit "Use when" clause containing natural trigger phrases. Minor improvements would be adding common synonyms (eviction notice, tenant, landlord) and tightening action wording from category nouns to concrete verbs.

DimensionReasoningScore

Specificity

"tenant screening, lease packets, notices, maintenance workflow and move-out accounting" lists several concrete action areas in third person ("Runs a small US rental portfolio"), matching the anchor for several specific actions with minor gaps. It falls short of 5 because actions are named as domain categories ("lease packets", "notices") rather than fully concrete operations, and coverage gaps exist (e.g., renewals, rent collection).

4 / 5

Completeness

The what is explicit ("Runs a small US rental portfolio: tenant screening, lease packets, notices, maintenance workflow and move-out accounting") and the when is explicit with concrete trigger phrases ("Use when: Generate...; Calculate...; Draft..."), matching the anchor that clearly answers both what AND when. Not below 5 because neither half is vague or merely implied.

5 / 5

Trigger Term Quality

"Generate state-specific residential lease agreements; Calculate security deposit return deadlines and itemizations; Draft compliant pay-or-quit and entry notices" contains natural phrases a landlord or property manager would actually say. Not 5 because common variations like "eviction notice", "tenant screening", "landlord", or "rent" are absent from the trigger clause.

4 / 5

Distinctiveness Conflict Risk

The US landlord-tenant niche with triggers like "state-specific residential lease agreements", "security deposit return deadlines", and "pay-or-quit and entry notices" occupies a clear niche with minimal overlap risk against generic document or legal skills. No neighboring anchor fits better, since even the 4 anchor's "minor overlap risk with closely related skills" is not evident here.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-finance-property/skills/nex-property-mgmt-us/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.