PluginBench
Skill
Review
Audit score 70

fine-dust-location

nomadamas/k-skill

Query fine dust and ultrafine dust levels by location name or coordinates using AirKorea data.

What is fine-dust-location?

This skill retrieves real-time particulate matter (PM10 and PM2.5) air quality data from South Korea's AirKorea service based on location names or geographic hints. Use it when you need current fine dust pollution levels for specific Korean regions.

  • Query fine dust (PM10) and ultrafine dust (PM2.5) concentrations by region name
  • Look up air quality data using location hints or coordinates
  • Integrate with k-skill-proxy's report endpoint for data retrieval
  • Support Korean locale queries and region-based filtering

How to install fine-dust-location

npx skills add https://github.com/nomadamas/k-skill --skill fine-dust-location
Prerequisites
  • Node.js 18 or higher
  • k-skill-proxy with report endpoint configured and accessible
  • Access to AirKorea data service
Claude Code
Cursor
Windsurf
Cline

How to use fine-dust-location

  1. 1.Run `npx -y @nomadamas/k-skill@0 instruct fine-dust-location` to get runtime-specific instructions
  2. 2.Review the helper files with `npx -y @nomadamas/k-skill@0 files fine-dust-location`
  3. 3.Provide a location name or coordinate hint to query dust levels
  4. 4.Parse the returned fine dust and ultrafine dust concentration data
  5. 5.Keep the CLI updated with `npx -y @nomadamas/k-skill@0 update`

Use cases

Good for
  • Check air quality before outdoor activities in specific Korean cities
  • Monitor particulate pollution trends across different regions
  • Build location-aware air quality alerts or dashboards
  • Provide real-time dust level information to users planning travel within Korea
Who it's for
  • Environmental monitoring applications
  • Weather and air quality apps targeting Korean users
  • Location-based health and wellness tools
  • Urban planning and public health initiatives

fine-dust-location FAQ

What data sources does this skill use?

It queries AirKorea (에어코리아), South Korea's official air quality information service, via the k-skill-proxy report endpoint.

Can I query by coordinates instead of region names?

Yes, the skill accepts both location names and location hints, which can include coordinate-based queries.

What are PM10 and PM2.5?

PM10 is fine dust (particles ≤10 micrometers) and PM2.5 is ultrafine dust (particles ≤2.5 micrometers); both are tracked for air quality assessment.

Is this skill limited to South Korea?

Yes, it uses AirKorea data which covers regions within South Korea.

Do I need to set up credentials?

No plaintext credentials should be stored; ensure your k-skill-proxy endpoint is properly configured and accessible.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.


name: fine-dust-location description: 에어코리아 기반 미세먼지/초미세먼지를 지역명 또는 위치 힌트로 조회한다. 기본 경로는 k-skill-proxy의 report endpoint다. license: MIT metadata: category: utility locale: ko-KR phase: v1

fine-dust-location

<!-- 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 fine-dust-location

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 fine-dust-location

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/fine-dust-location/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.