Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/openyida/openyida-openclaw-skillnpx agentmods add skills/openyida/openyida-openclaw-skill/yida-appWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/openyida/openyida-openclaw-skill/yida-app)<a href="https://agentmods.dev/skills/openyida/openyida-openclaw-skill/yida-app"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-app/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openyida/openyida-openclaw-skill/yida-app"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00092 | $0.03810 |
| Opus 5.5 | $0.00037 | $0.01524 |
| Sonnet 5.5 | $0.00018 | $0.00762 |
| Haiku 4.5 | $0.00009 | $0.00381 |
Grade A, and why
yida-app scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
宜搭完整应用开发技能
概述
本技能描述如何从零到一完整搭建一个宜搭应用,涵盖从应用创建到代码发布的全流程。每个步骤均依赖对应的子技能完成。
何时使用
当以下场景发生时使用此技能:
- 用户想要一句话生成完整的宜搭应用
- 用户需要从头开始开发一个宜搭应用
- 用户不了解宜搭开发流程,需要完整指导
- 进行完整的宜搭应用开发项目
使用示例
示例 1:一句话生成应用
场景:用户说"帮我搭建一个生日祝福小游戏" 流程:
- 调用 yida-create-app 创建应用
- 需求分析,写入 prd 文档
- 调用 yida-create-page 创建自定义页面
- 如需存储数据,调用 yida-create-form-page 创建表单
- 调用 yida-custom-page 编写页面代码
- 调用 yida-publish-page 发布页面
完整开发流程
创建应用
↓
需求分析 → 创建 prd 文档(prd/<项目名>.md)
↓
创建自定义页面
↓
(如需存储数据)创建表单 → 将字段描述信息写入 prd 文档
↓
调用 yida-custom-page 技能编写页面代码(src/<name>.js)
↓
自动调用 yida-publish-page 技能发布代码
💡 登录态说明:各脚本会自动读取项目根目录的
.cache/cookies.json。若 Cookie 不存在或已失效,脚本会报错退出,此时必须先调用yida-loginskill 完成交互式扫码登录(agent 用 browser 工具打开页面截图发给用户扫码),再重新执行后续步骤。严禁直接告知用户去自己打开浏览器扫码。
步骤详解
⚠️ 前置强制规则(必须遵守)
在开始任何宜搭应用开发前,必须先执行以下检查:
⚠️ corpId 一致性检查(关键步骤)
在执行创建页面前,必须检查 prd 文档中的 corpId 与当前登录态的 corpId 是否一致:
- 读取 prd 文档中的应用配置,获取已记录的
corpId - 读取
.cache/cookies.json,获取当前登录态的corpId - 对比两个 corpId:
- 如果一致:继续执行创建页面
- 如果不一致或 prd 中无 corpId:提示用户选择处理方式
corpId 不一致时的处理选项:
| 场景 | 建议操作 |
|---|---|
| prd 中有 corpId,但与当前登录态不一致 | 询问用户:是重新登录到 prd 中的组织,还是在当前组织新建应用? |
| prd 中无 corpId | 直接新建应用 |
决策流程:
检查 prd.corpId vs Cookie.corpId
│
├── 一致 → 继续创建页面
│
└── 不一致
│
├── 用户选择"重新登录" → 执行 yida-logout → 重新扫码登录到正确组织
│
└── 用户选择"新建应用" → 回到 Step 1 创建新应用(会自动覆盖 prd 配置)
Step 1:创建应用
调用 yida-create-app 技能创建宜搭应用,获取 appType。
node .claude/skills/yida-create-app/scripts/create-app.js "<应用名称>" "[描述]"
输出:appType(如 APP_XXXXXX),用 markdown 记录到 prd 文件夹下文档备用。
详见
yida-create-app技能文档。
Step 2:创建自定义页面
创建页面命令
确认 corpId 一致后,调用 yida-create-page 技能:
node .claude/skills/yida-create-page/scripts/create-page.js "<appType>" "<页面名称>"
输出:pageId(如 FORM-XXXXXX),记录到 prd 文档备用。
详见
yida-create-page技能文档。
Step 3:需求分析 → 写入 prd 文档
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 386 lines · 92 tokens per session scan A 22082fb23846
yida-app is a skill published in the GitHub repository openyida/openyida-openclaw-skill (5 stars, last pushed 7mo ago), licensed MIT. It adds 92 tokens to every session and 3,810 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…