OpenClaw

edgeos-applications

Apply to an EdgeOS popup city through OpenClaw (v1 fixed PROD backend). Use when users ask to apply to a popup city (for example Edge Esmeralda), submit an application, check application status, select products after approval, or generate/check payment links. Covers OTP login, popup discovery, application submission, approval-aware product selection, payment preview/create, and payment status checks.

franvinas0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install franvinas/edgeos-applications

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

OpenClaw Popup Application (v1)

Run the EdgeOS application flow with a strict, reliable sequence:

Authenticate user via OTP once per session.
Persist and reuse JWT for all subsequent calls in that session.
Resolve target popup.
Collect required application fields.
Submit application.
Check status on demand.
After acceptance, guide product selection and payment.

Read these references before executing:

{baseDir}/references/conversation-flow.md
{baseDir}/references/flow.md
{baseDir}/references/api-contract.md (API source of truth)

Before collecting fields, read workspace USER.md and use it as prefill context when values are relevant and trustworthy for the current user.

Runtime configuration

This v1 skill is intentionally pinned to PROD backend values (no user setup required). Values are defined once in:

{baseDir}/scripts/env.sh

Do not ask users to configure runtime values in v1. Use the values from scripts/env.sh consistently for auth and API calls.

Script-first rule

Prefer scripts in {baseDir}/scripts over ad-hoc curl construction:

auth_request_otp.sh
auth_login.sh (persists JWT in local state file)
submit_application.sh
check_application_status.sh (supports --application-id or --citizen-id + --popup-city-id)
payment_preview.sh
payment_create.sh
payment_status.sh

Only fall back to raw curl if a script cannot handle the case.

Data collection policy (strict minimal questions)

Use this exact sequence:

Determine required + optional application fields.
Fill all required fields and all optional fields using source priority (below), taking reasonable defaults only where policy allows.
Ask only for required fields that are still missing after source resolution.
Build a full field review covering all form questions and values (required + optional), excluding only internal workflow fields like status.
For every unresolved field, ask the user and label it as requ...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/franvinas/edgeos-applications
Version: —
Commit: b9fcf01e9f522ed0f840d67b0fc739f138830946
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# OpenClaw Popup Application (v1)

Run the EdgeOS application flow with a strict, reliable sequence:

1. Authenticate user via OTP once per session.
2. Persist and reuse JWT for all subsequent calls in that session.
3. Resolve target popup.
4. Collect required application fields.
5. Submit application.
6. Check status on demand.
7. After acceptance, guide product selection and payment.

Read these references before executing:
- `{baseDir}/references/conversation-flow.md`
- `{baseDir}/references/flow.md`
- `{baseDir}/references/api-contract.md` (API source of truth)

Before collecting fields, read workspace `USER.md` and use it as prefill context when values are relevant and trustworthy for the current user.

## Runtime configuration

This v1 skill is intentionally pinned to PROD backend values (no user setup required).
Values are defined once in:
- `{baseDir}/scripts/env.sh`

Do not ask users to configure runtime values in v1.
Use the values from `scripts/env.sh` consistently for auth and API calls.

## Script-first rule

Prefer scripts in `{baseDir}/scripts` over ad-hoc curl construction:
- `auth_request_otp.sh`
- `auth_login.sh` (persists JWT in local state file)
- `submit_application.sh`
- `check_application_status.sh` (supports `--application-id` or `--citizen-id` + `--popup-city-id`)
- `payment_preview.sh`
- `payment_create.sh`
- `payment_status.sh`

Only fall back to raw curl if a script cannot handle the case.

## Data collection policy (strict minimal questions)

Use this exact sequence:
1. Determine required + optional application fields.
2. Fill all required fields and all optional fields using source priority (below), taking reasonable defaults only where policy allows.
3. Ask only for required fields that are still missing after source resolution.
4. Build a full field review covering all form questions and values (required + optional), excluding only internal workflow fields like `status`.
5. For every unresolved field, ask the user and label it as requ...

搜索