Lap Airportsapi

airportsapi API skill. Use when working with airportsapi for airportsapi. Covers 1 endpoint.

Security Scan

The skill is an instruction-only wrapper for a single airportsapi endpoint and its requirements are largely consistent with that purpose; the only notable mismatch is a wording/auth detail in the instructions (OAuth2 vs a single AIRPORTSAPI_API_KEY).

Purpose & Capability

The name, description, and declared requirement (AIRPORTSAPI_API_KEY) align with a simple API client for a single airports endpoint. There are no unrelated binaries, config paths, or extra credentials requested.

Instruction Scope

The SKILL.md stays within the API-client scope (shows base URL, auth, endpoint, and CLI tips). It references a local spec file (references/api-spec.lap) that is not included and suggests running npx @lap-platform/lapsh commands to fetch/update specs — this is reasonable but means the agent may attempt to run npx or fetch remote specs. The instructions say "OAuth2" for Auth while the skill requires AIRPORTSAPI_API_KEY, which is a minor inconsistency in how authentication is described.

Install Mechanism

No install spec and no code files — instruction-only — so nothing will be written to disk by an installer. This is the lowest-risk install profile.

Credentials

Only one environment variable is required (AIRPORTSAPI_API_KEY), which is proportionate for an API wrapper. The mismatch between the declared env var and the 'OAuth2' wording is worth confirming: verify whether the API expects an OAuth2 flow (client_id/secret, token exchange) or a single API key/bearer token before providing credentials.

Persistence & Privilege

always is false and the skill is user-invocable only. There is no indication the skill requests persistent system-wide privileges or modifies other skills/configs.

Assessment

This skill is a lightweight instruction-only adapter for a single airportsapi endpoint and appears coherent. Before installing/providing credentials: 1) Confirm what the API actually requires for auth — is AIRPORTSAPI_API_KEY sufficient or does it require a full OAuth2 flow (client id/secret and token exchange)? 2) Only provide a dedicated, least-privilege API key (don't reuse high-privilege or unrelated service credentials). 3) Note the SKILL.md references fetching a spec with npx; if you don't want the agent running npx or fetching external specs, avoid enabling autonomous invocation or test in a sandbox first. 4) As best practice, test with a scoped or temporary key and rotate/revoke it if you stop using the skill.

airportsapi

API version: v1

Auth

OAuth2

Base URL

https://airport-web.appspot.com/_ah/api

Setup

1. Configure auth: OAuth2
2. GET /airportsapi/v1/airports/{icao_code} -- verify access

Endpoints

1 endpoints across 1 groups. See references/api-spec.lap for full details.

airportsapi

Method	Path	Description
GET	/airportsapi/v1/airports/{icao_code}

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "Get airport details?" -> GET /airportsapi/v1/airports/{icao_code}
• "How to authenticate?" -> See Auth section

Response Tips

• Check response schemas in references/api-spec.lap for field details

CLI

# Update this spec to the latest version
npx @lap-platform/lapsh get airportsapi -o references/api-spec.lap

# Search for related APIs
npx @lap-platform/lapsh search airportsapi

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP