localdata-business-status

nomadamas/k-skill

Query South Korean local business licensing data to check operating status, permits, and details for 208+ business types.

Source View on skills.sh

What is localdata-business-status?

This skill accesses South Korea's LOCALDATA (local administrative licensing database) to look up business operating status, licensing dates, closure dates, business type, and address. Search by business name and city/district with no authentication key required.

Query operating, closed, or suspended status for licensed businesses
Retrieve business licensing date (age/tenure) and closure date if applicable
Look up business type (업태) and registered address
Search across 208+ licensed business categories (restaurants, cafes, accommodations, pharmacies, salons, academies, etc.)
Search by business name (상호) and city/district (시군구) without API keys

How to install localdata-business-status

npx skills add https://github.com/nomadamas/k-skill --skill localdata-business-status

Claude Code

Cursor

Windsurf

Cline

How to use localdata-business-status

1.Run `npx -y @nomadamas/k-skill@0 instruct localdata-business-status` to get full runtime-specific instructions
2.Prepare the business name (상호) and city/district (시군구) you want to search
3.Execute the query using the provided CLI or integration method
4.Review the returned operating status, licensing date, and business details

Use cases

Good for

Verify if a local restaurant or cafe is currently operating before visiting
Check business licensing history and tenure for due diligence
Find closure dates for businesses that have shut down
Research competitor or partner business status in a specific area
Validate business information for local market research

Who it's for

Local business researchers and market analysts
Real estate or franchise scouts evaluating neighborhoods
Consumers verifying business operating status
Korean business development teams
Anyone researching South Korean local commerce

localdata-business-status FAQ

Do I need an API key or authentication?

No, this skill requires no authentication key to access LOCALDATA.

What business types can I search?

You can search 208+ licensed business categories including restaurants, cafes, accommodations, pharmacies, beauty salons, academies, and other regulated businesses.

What information is returned?

Results include operating/closed/suspended status, licensing date, closure date (if applicable), business type (업태), and address.

How do I search?

Search by providing the business name (상호) and city/district (시군구).

What language is this skill in?

The skill is designed for South Korean businesses and uses Korean administrative data; instructions are in Korean.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.

name: localdata-business-status description: 지방행정 인허가데이터(LOCALDATA)로 동네 사업장(식당·카페·숙박·약국·미용실·학원 등 인허가 업종 208종)의 영업/휴업/폐업 상태, 인허가일자(업력), 폐업일자, 업태, 주소를 조회한다. 상호+시군구로 검색하며 인증키 불필요. license: MIT metadata: category: business locale: ko-KR phase: v1

localdata-business-status

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 localdata-business-status

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 localdata-business-status

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/localdata-business-status/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.