mcpField
R
real-estate-search

real-estate-search

github.com/nomadamasOther8.2k8.1k installsUpdated 2d ago
Repository

About real-estate-search

real-estate-search is a coding-agent skill whose current instructions are retrieved through the k-skill CLI. Its README emphasizes approval, credential, and legal-boundary safeguards.

Key features

  1. 01Fetch current skill instructions with the CLI
  2. 02List bundled helper files
  3. 03Update the CLI and installed skills
  4. 04Require approval for consequential actions
  5. 05Protect credentials and legal boundaries

Use cases

  1. 01Load instructions for real-estate search tasks
  2. 02Review the skill's bundled helper files
  3. 03Keep the CLI and skill installations current

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill real-estate-search

After installing, type/real-estate-searchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
nationwide_daily_report.py
tests/
test_nationwide_daily_report.py

Details

From the project README

real-estate-search

Get the full instructions (required first step)

Run this and follow its output as the primary instructions for this skill:

npx -y @nomadamas/k-skill@0 instruct real-estate-search

The CLI detects the current runtime (Dolshoi vault/CloakBrowser vs generic) and prints only the applicable instructions, always up to date. Helper files bundled with the CLI are listed by:

npx -y @nomadamas/k-skill@0 files real-estate-search

Keep the CLI and every coding-agent skill install current (including Vercel Agent Skills) with:

npx -y @nomadamas/k-skill@0 update

If npx is unavailable, install Node.js 18+ or follow https://github.com/NomaDamas/k-skill#readme, or read the source instructions at https://github.com/NomaDamas/k-skill/blob/main/real-estate-search/instruction.md.

Hard rules even without the CLI

  • Never execute payment, message/email delivery, final submission, cancellation, or public posting without the user's explicit approval immediately beforehand.
  • Never ask for, print, or store plaintext credentials in chat, files, or shell arguments.
  • Never bypass legal, physical-presence, CAPTCHA, identity-proofing, or electronic-signature boundaries.

Comments

Markdown supported