g2b-sanctioned-supplier

nomadamas/k-skill

Check South Korean government procurement sanctions status by business registration number via public API.

What is g2b-sanctioned-supplier?

Queries the Korean Public Data Portal API to verify current bidding participation restrictions (sanctions) for suppliers in the G2B national procurement system. Use this to check if a business is sanctioned for misconduct and view restriction periods, sanctioning agencies, and legal basis.

Looks up exact business registration number matches in the G2B sanctions database
Returns current valid bidding participation restrictions at query time
Displays sanction period, sanctioning agency, and legal basis for each restriction
Accesses data through the k-skill-proxy to the Public Data Portal API
Supports Korean government procurement compliance checks

How to install g2b-sanctioned-supplier

npx skills add https://github.com/nomadamas/k-skill --skill g2b-sanctioned-supplier

Prerequisites

Node.js 18 or later
npx or npm installed
Access to the k-skill-proxy and Public Data Portal API

Claude Code

Cursor

Windsurf

Cline

How to use g2b-sanctioned-supplier

1.Run `npx -y @nomadamas/k-skill@0 instruct g2b-sanctioned-supplier` to get full runtime-specific instructions
2.Obtain the business registration number to query
3.Call the skill with the exact business registration number
4.Review the returned sanction details including period, agency, and legal basis
5.Document findings for procurement records

Use cases

Good for

Verify supplier eligibility before awarding government contracts
Check if a bidder has active sanctions that would disqualify them
Audit procurement decisions for compliance with sanction rules
Screen potential vendors in the G2B system for misconduct history
Confirm sanction status during tender evaluation

Who it's for

Government procurement officers
Contract compliance managers
Procurement auditors
Bid evaluation committees
Suppliers verifying their own status

g2b-sanctioned-supplier FAQ

What data source does this skill use?

It queries the Korean Public Data Portal API through k-skill-proxy, accessing the G2B (나라장터) sanctions database maintained by the Korean Procurement Service.

Does it match partial business registration numbers?

No, it requires exact matches of the full business registration number for accurate results.

What information is returned for a sanctioned supplier?

The skill returns the sanction period (start/end dates), the sanctioning agency, and the legal basis or statute for the restriction.

What if a business has no active sanctions?

The query will indicate no current valid restrictions, meaning the business is eligible to participate in bidding.

Is this skill available in English?

The skill is designed for Korean government procurement (G2B) and operates in Korean; documentation and API responses are in Korean.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.

name: g2b-sanctioned-supplier description: 조달청 나라장터 부정당제재업체정보를 공공데이터포털 API(k-skill-proxy 경유)로 조회한다. 사업자등록번호 정확 일치로 조회시점 현재 유효한 입찰참가자격 제한(부정당제재)의 기간·제재기관·근거법률을 확인한다. license: MIT metadata: category: business locale: ko-KR phase: v1

g2b-sanctioned-supplier

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 g2b-sanctioned-supplier

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 g2b-sanctioned-supplier

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/g2b-sanctioned-supplier/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.