@mongoui/skills 0.1.7 → 0.1.9

package/package.json

@@ -1,26 +1,26 @@
-{
-  "name": "@mongoui/skills",
-  "version": "0.1.7",
-  "description": "CLI for installing product skills into AI tools",
-  "license": "MIT",
-  "publishConfig": {
-    "access": "public"
-  },
-  "type": "module",
-  "bin": {
-    "msg-skills": "dist/cli.js"
-  },
-  "files": [
-    "dist",
-    "skills"
-  ],
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "dev": "tsx src/cli.ts"
-  },
-  "devDependencies": {
-    "@types/node": "^24.6.0",
-    "tsx": "^4.20.6",
-    "typescript": "^5.9.3"
-  }
-}
+{
+  "name": "@mongoui/skills",
+  "version": "0.1.9",
+  "description": "CLI for installing product skills into AI tools",
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "bin": {
+    "msg-skills": "dist/cli.js"
+  },
+  "files": [
+    "dist",
+    "skills"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "dev": "tsx src/cli.ts"
+  },
+  "devDependencies": {
+    "@types/node": "^24.6.0",
+    "tsx": "^4.20.6",
+    "typescript": "^5.9.3"
+  }
+}

package/skills/flink-flight-api/SKILL.md

@@ -1,63 +1,63 @@
----
-name: flink-flight-api
-description: Integrate with the Flink flight OpenAPI exposed through the Open Platform runtime gateway. Use when an AI coding assistant needs to read, verify, explain, test, or implement against `docs/swagger/flink-api.json` or Flink route code; choose Flink ticket endpoints; generate or debug `X-OP-*` signatures; explain sandbox or production credential issuance/reset; or handle Chinese/English requests about Flink 机票 search, booking, payment, order detail, change, refund, airport, airline, nationality, and fields workflows.
----
-
-# Flink Flight API Skill
-
-## Quick Start
-
-Use this skill when the task is "call Flink through the open platform".
-
-Start with the smallest current source that answers the request:
-
-- Prefer the repository source of truth when it exists: `docs/swagger/flink-api.json`, route handlers, DTOs, and tests.
-- Read `references/auth-and-credentials.md` for signing, headers, key acquisition, reset, or auth troubleshooting.
-- Read `references/api-workflows.md` for business sequencing such as search to booking, change, or refund.
-- Read `references/endpoint-index.md` for a compact endpoint map, then verify fragile fields against the current swagger or code.
-- Use `scripts/flink_signed_request.py` to generate headers, inspect the canonical string, or send a signed request.
-
-## Working Rules
-
-Follow this workflow:
-
-1. Confirm the environment: `sandbox` and `production` credentials are separate.
-2. Confirm whether the user is asking for documentation, code changes, local smoke testing, or live API calls.
-3. Confirm the public path under `/openapi/v1/flink/*` and the required `lang` path parameter when present.
-4. Build the minimum valid request body from swagger/code first, using `references/endpoint-index.md` as navigation.
-5. Sign the exact request path, sorted query string, and raw body bytes with the platform secret.
-6. Evaluate both HTTP status and response envelope `code`, not HTTP status alone.
-
-Do not violate these rules:
-
-- Always send `X-OP-App-Key`, `X-OP-Timestamp`, `X-OP-Nonce`, and `X-OP-Sign`.
-- Never send Flink-side `appid`, `timestamp`, or `sign`; the platform injects Flink downstream auth fields.
-- Never invent credentials or secrets. Use explicit user-provided values or environment variables.
-- Treat `code=SUCCESS` as success. Treat `code=SUPPLIER_BIZ_ERROR` as a business failure even if HTTP status is `200`.
-- Keep timestamp skew within `+-5` minutes.
-- Reuse of the same nonce under the same app key can trigger `NONCE_REPLAY`.
-- Preserve bridge identifiers across steps:
-  - `priceKey` bridges search or cabin to verify and order creation.
-  - `orderNo` bridges order detail, cancel, change, refund, and fields lookup.
-  - `changeOrderNo` and `refundOrderNo` drive their detail or cancel or confirm calls.
-- For `GET /openapi/v1/flink/fields`, send at least one of `priceKey` or `orderNo`.
-
-## Typical Requests
-
-Use these patterns by default:
-
-- Search and booking: `flight.search` -> `flight.cabin` if needed -> `flight.verify` -> `flight.order.create` -> `flight.order.pay` -> `flight.order.detail`
-- Change: `flight.order.detail` -> `flight.change.search` -> `flight.change.apply` -> `flight.order.pay` with `type=1` if payment is required -> `flight.change.detail`
-- Refund: `flight.order.detail` -> `flight.refund.apply` -> `flight.refund.detail` -> `flight.refund.confirm`
-- Base data: `airports.list`, `airlines.list`, `airports.search`, `nationality.list`, `fields`
-
-## Output Expectations
-
-When answering or coding with this skill:
-
-- Prefer concrete request examples over abstract summaries.
-- Name the source used when the current swagger/code and bundled references disagree.
-- State which environment the credential belongs to.
-- State which identifier from the previous step is needed next.
-- Call out auth failures with the likely root cause and the exact header or field to inspect.
-- For code changes, keep Flink downstream auth and platform gateway auth clearly separated.
+---
+name: flink-flight-api
+description: Integrate with the Flink flight OpenAPI exposed through the Open Platform runtime gateway. Use when an AI coding assistant needs to read, verify, explain, test, or implement against `docs/swagger/flink-api.json` or Flink route code; choose Flink ticket endpoints; generate or debug `X-OP-*` signatures; explain sandbox or production credential issuance/reset; or handle Chinese/English requests about Flink 机票 search, booking, payment, order detail, change, refund, airport, airline, nationality, and fields workflows.
+---
+
+# Flink Flight API Skill
+
+## Quick Start
+
+Use this skill when the task is "call Flink through the open platform".
+
+Start with the smallest current source that answers the request:
+
+- Prefer the repository source of truth when it exists: `docs/swagger/flink-api.json`, route handlers, DTOs, and tests.
+- Read `references/auth-and-credentials.md` for signing, headers, key acquisition, reset, or auth troubleshooting.
+- Read `references/api-workflows.md` for business sequencing such as search to booking, change, or refund.
+- Read `references/endpoint-index.md` for a compact endpoint map, then verify fragile fields against the current swagger or code.
+- Use `scripts/flink_signed_request.py` to generate headers, inspect the canonical string, or send a signed request.
+
+## Working Rules
+
+Follow this workflow:
+
+1. Confirm the environment: `sandbox` and `production` credentials are separate.
+2. Confirm whether the user is asking for documentation, code changes, local smoke testing, or live API calls.
+3. Confirm the public path under `/openapi/v1/flink/*` and the required `lang` path parameter when present.
+4. Build the minimum valid request body from swagger/code first, using `references/endpoint-index.md` as navigation.
+5. Sign the exact request path, sorted query string, and raw body bytes with the platform secret.
+6. Evaluate both HTTP status and response envelope `code`, not HTTP status alone.
+
+Do not violate these rules:
+
+- Always send `X-OP-App-Key`, `X-OP-Timestamp`, `X-OP-Nonce`, and `X-OP-Sign`.
+- Never send Flink-side `appid`, `timestamp`, or `sign`; the platform injects Flink downstream auth fields.
+- Never invent credentials or secrets. Use explicit user-provided values or environment variables.
+- Treat `code=SUCCESS` as success. Treat `code=SUPPLIER_BIZ_ERROR` as a business failure even if HTTP status is `200`.
+- Keep timestamp skew within `+-5` minutes.
+- Reuse of the same nonce under the same app key can trigger `NONCE_REPLAY`.
+- Preserve bridge identifiers across steps:
+  - `priceKey` bridges search or cabin to verify and order creation.
+  - `orderNo` bridges order detail, cancel, change, refund, and fields lookup.
+  - `changeOrderNo` and `refundOrderNo` drive their detail or cancel or confirm calls.
+- For `GET /openapi/v1/flink/fields`, send at least one of `priceKey` or `orderNo`.
+
+## Typical Requests
+
+Use these patterns by default:
+
+- Search and booking: `flight.search` -> `flight.cabin` if needed -> `flight.verify` -> `flight.order.create` -> `flight.order.pay` -> `flight.order.detail`
+- Change: `flight.order.detail` -> `flight.change.search` -> `flight.change.apply` -> `flight.order.pay` with `type=1` if payment is required -> `flight.change.detail`
+- Refund: `flight.order.detail` -> `flight.refund.apply` -> `flight.refund.detail` -> `flight.refund.confirm`
+- Base data: `airports.list`, `airlines.list`, `airports.search`, `nationality.list`, `fields`
+
+## Output Expectations
+
+When answering or coding with this skill:
+
+- Prefer concrete request examples over abstract summaries.
+- Name the source used when the current swagger/code and bundled references disagree.
+- State which environment the credential belongs to.
+- State which identifier from the previous step is needed next.
+- Call out auth failures with the likely root cause and the exact header or field to inspect.
+- For code changes, keep Flink downstream auth and platform gateway auth clearly separated.

package/skills/flink-flight-api/agents/openai.yaml

@@ -1,4 +1,4 @@
-interface:
-  display_name: "Flink OpenAPI 接入"
-  short_description: "Flink 机票开放接口鉴权、签名和业务调用"
-  default_prompt: "Use $flink-flight-api to implement or debug Flink flight OpenAPI auth, signatures, endpoint selection, and order workflows."
+interface:
+  display_name: "Flink OpenAPI 接入"
+  short_description: "Flink 机票开放接口鉴权、签名和业务调用"
+  default_prompt: "Use $flink-flight-api to implement or debug Flink flight OpenAPI auth, signatures, endpoint selection, and order workflows."

package/skills/flink-flight-api/references/api-workflows.md

@@ -1,104 +1,104 @@
-# Flink API Workflows
-
-## Search And Booking
-
-Use this sequence for a normal booking flow:
-
-1. `flink.flight.search`
-   - Search journeys and offer combinations.
-   - Save returned `priceKey` values for the next step.
-2. `flink.flight.cabin`
-   - Use when a selected offer needs more fare or cabin quotes.
-   - Input is `priceKey`.
-3. `flink.flight.verify`
-   - Validate the selected offer before order creation.
-   - Input is `priceKey`.
-4. `flink.flight.order.create`
-   - Create the pre-booking order with contact and passenger data.
-   - Input still depends on `priceKey`.
-5. `flink.flight.order.pay`
-   - Pay the standard order with `type=0`.
-6. `flink.flight.order.detail`
-   - Read status, ticketing progress, and later change or refund context.
-7. `flink.flight.order.cancel`
-   - Use only for cancellable standard orders.
-
-Keep these state tokens:
-
-- `priceKey`: search or cabin -> verify or order creation
-- `orderNo`: order creation or detail -> pay, cancel, change, refund, fields
-
-## Change Flow
-
-Use this sequence for voluntary or involuntary changes:
-
-1. `flink.flight.order.detail`
-   - Confirm order status and segment context.
-2. `flink.flight.change.search`
-   - Search eligible changed flights for an existing order and passenger or segment scope.
-3. `flink.flight.change.apply`
-   - Submit the actual change request with `priceKey`, passenger scope, segment scope, reason, and contact info.
-4. `flink.flight.order.pay`
-   - If the change order requires payment, pay with `type=1`.
-5. `flink.flight.change.detail`
-   - Track the change request by `changeOrderNo`.
-6. `flink.flight.change.cancel`
-   - Cancel a pending change request by `changeOrderNo`.
-
-Bridge identifiers:
-
-- `orderNo` drives change search and apply.
-- `priceKey` from change search is used in change apply.
-- `changeOrderNo` drives detail and cancel.
-
-## Refund Flow
-
-Use this sequence for refunds:
-
-1. `flink.flight.order.detail`
-   - Confirm the refundable order, passenger, and segment scope.
-2. `flink.flight.refund.apply`
-   - Submit the refund request with passenger scope, segment scope, contact data, and reason.
-3. `flink.flight.refund.detail`
-   - Track the refund request by `refundOrderNo`.
-4. `flink.flight.refund.confirm`
-   - Confirm or cancel the refund request.
-
-Bridge identifiers:
-
-- `orderNo` drives refund apply.
-- `refundOrderNo` drives detail and confirm.
-
-## Base Data And Helper Calls
-
-Use these APIs outside the booking lifecycle:
-
-- `flink.airports.list`
-  - Paged airport list with optional keyword filtering.
-- `flink.airlines.list`
-  - Paged airline list with optional keyword and code filtering.
-- `flink.airports.search`
-  - Lightweight airport search by keyword.
-- `flink.nationality.list`
-  - Nationality reference data.
-- `flink.fields`
-  - Field translations and baggage or travel notice helpers.
-  - Provide either `priceKey` or `orderNo`.
-
-## Language Parameter
-
-All Flink routes except `flink.fields` require `{lang}` in the path.
-
-Common values:
-
-- `en`
-- `zh_CN`
-- `zh_TW`
-
-Use the same `lang` across related calls unless there is a clear reason to switch.
-
-## Business Handling Rules
-
-- Do not treat HTTP `200` as enough; inspect `code`.
-- Do not rebuild Flink headers; the runtime gateway handles downstream authentication.
-- Preserve the original Flink identifiers from earlier responses instead of recomputing them.
+# Flink API Workflows
+
+## Search And Booking
+
+Use this sequence for a normal booking flow:
+
+1. `flink.flight.search`
+   - Search journeys and offer combinations.
+   - Save returned `priceKey` values for the next step.
+2. `flink.flight.cabin`
+   - Use when a selected offer needs more fare or cabin quotes.
+   - Input is `priceKey`.
+3. `flink.flight.verify`
+   - Validate the selected offer before order creation.
+   - Input is `priceKey`.
+4. `flink.flight.order.create`
+   - Create the pre-booking order with contact and passenger data.
+   - Input still depends on `priceKey`.
+5. `flink.flight.order.pay`
+   - Pay the standard order with `type=0`.
+6. `flink.flight.order.detail`
+   - Read status, ticketing progress, and later change or refund context.
+7. `flink.flight.order.cancel`
+   - Use only for cancellable standard orders.
+
+Keep these state tokens:
+
+- `priceKey`: search or cabin -> verify or order creation
+- `orderNo`: order creation or detail -> pay, cancel, change, refund, fields
+
+## Change Flow
+
+Use this sequence for voluntary or involuntary changes:
+
+1. `flink.flight.order.detail`
+   - Confirm order status and segment context.
+2. `flink.flight.change.search`
+   - Search eligible changed flights for an existing order and passenger or segment scope.
+3. `flink.flight.change.apply`
+   - Submit the actual change request with `priceKey`, passenger scope, segment scope, reason, and contact info.
+4. `flink.flight.order.pay`
+   - If the change order requires payment, pay with `type=1`.
+5. `flink.flight.change.detail`
+   - Track the change request by `changeOrderNo`.
+6. `flink.flight.change.cancel`
+   - Cancel a pending change request by `changeOrderNo`.
+
+Bridge identifiers:
+
+- `orderNo` drives change search and apply.
+- `priceKey` from change search is used in change apply.
+- `changeOrderNo` drives detail and cancel.
+
+## Refund Flow
+
+Use this sequence for refunds:
+
+1. `flink.flight.order.detail`
+   - Confirm the refundable order, passenger, and segment scope.
+2. `flink.flight.refund.apply`
+   - Submit the refund request with passenger scope, segment scope, contact data, and reason.
+3. `flink.flight.refund.detail`
+   - Track the refund request by `refundOrderNo`.
+4. `flink.flight.refund.confirm`
+   - Confirm or cancel the refund request.
+
+Bridge identifiers:
+
+- `orderNo` drives refund apply.
+- `refundOrderNo` drives detail and confirm.
+
+## Base Data And Helper Calls
+
+Use these APIs outside the booking lifecycle:
+
+- `flink.airports.list`
+  - Paged airport list with optional keyword filtering.
+- `flink.airlines.list`
+  - Paged airline list with optional keyword and code filtering.
+- `flink.airports.search`
+  - Lightweight airport search by keyword.
+- `flink.nationality.list`
+  - Nationality reference data.
+- `flink.fields`
+  - Field translations and baggage or travel notice helpers.
+  - Provide either `priceKey` or `orderNo`.
+
+## Language Parameter
+
+All Flink routes except `flink.fields` require `{lang}` in the path.
+
+Common values:
+
+- `en`
+- `zh_CN`
+- `zh_TW`
+
+Use the same `lang` across related calls unless there is a clear reason to switch.
+
+## Business Handling Rules
+
+- Do not treat HTTP `200` as enough; inspect `code`.
+- Do not rebuild Flink headers; the runtime gateway handles downstream authentication.
+- Preserve the original Flink identifiers from earlier responses instead of recomputing them.