PluginBench
Skill
Review
Audit score 70

building-register-search

nomadamas/k-skill

Look up Korean building-register title records by address, PNU, legal-dong code, or parcel number.

What is building-register-search?

Searches Korean building-register (건축물대장) title records using multiple query methods. Use this when you need to retrieve property registration details, ownership information, or building specifications for Korean real estate.

  • Query building-register records by Korean address
  • Search by PNU (Property Number Unit)
  • Look up by legal-dong code
  • Find records by parcel number
  • Retrieve building title and ownership details

How to install building-register-search

npx skills add https://github.com/nomadamas/k-skill --skill building-register-search
Prerequisites
  • Node.js 18 or higher
  • npx package manager access
  • Run 'npx -y @nomadamas/k-skill@0 instruct building-register-search' to get full runtime-specific instructions
Claude Code
Cursor
Windsurf
Cline

How to use building-register-search

  1. 1.Run the CLI instruction command to get current runtime-specific guidance
  2. 2.Prepare your search query (address, PNU, legal-dong code, or parcel number)
  3. 3.Execute the search using the appropriate query method
  4. 4.Review the returned building-register title record details
  5. 5.Verify the information matches your property of interest

Use cases

Good for
  • Real estate due diligence and property verification
  • Building ownership and title confirmation
  • Property research for Korean real estate transactions
  • Checking building specifications and registration status
  • Legal and administrative property inquiries
Who it's for
  • Real estate professionals
  • Property researchers
  • Legal professionals handling Korean real estate
  • Administrative staff managing property records
  • Individuals verifying property ownership

building-register-search FAQ

What query formats are supported?

You can search by Korean address, PNU (Property Number Unit), legal-dong code, or parcel number. The skill auto-detects the format.

Do I need special credentials or authentication?

Follow the CLI instructions for your runtime environment (Dolshoi vault/CloakBrowser vs generic). Never store plaintext credentials in chat or files.

What information does a building-register record contain?

Records include building title, ownership details, building specifications, registration status, and other official property registration information.

Is this skill available outside Korea?

The skill is designed for Korean building-register (건축물대장) records, which are Korea-specific property registrations.

How do I keep the skill current?

Run 'npx -y @nomadamas/k-skill@0 update' regularly to ensure you have the latest version and helper files.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.


name: building-register-search description: Use when the user asks to look up a Korean building-register title record by address, PNU, legal-dong code, or parcel number. license: MIT metadata: category: real-estate locale: ko-KR phase: v1

building-register-search

<!-- k-skill:cli-stub — generated by scripts/generate-skill-stubs.js; edit skill.json / instruction.md instead -->

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 building-register-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 building-register-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/building-register-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.