Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add openyida/openyida-openclaw-skill --skill yida-get-schemagit clone --depth 1 https://github.com/openyida/openyida-openclaw-skillWrote 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-get-schema)<a href="https://agentmods.dev/skills/openyida/openyida-openclaw-skill/yida-get-schema"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-get-schema/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-get-schema"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-get-schema.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.00074 | $0.00867 |
| Opus 5 | $0.00037 | $0.00434 |
| Sonnet 5 | $0.00015 | $0.00173 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
yida-get-schema 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 9d 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.
What it actually says
宜搭表单 Schema 获取技能
概述
本技能描述如何通过 getFormSchema 接口获取宜搭表单的完整 Schema 结构。获取到的 Schema 可用于分析字段定义、组件配置、学习表单结构等场景，也可用于在编码时确认字段 ID（fieldId）。
何时使用
当以下场景发生时使用此技能：
- 用户需要查看已有表单的字段结构
- 需要确认表单中各字段的 fieldId
- 在编码前需要了解表单的组件配置
- 需要分析现有表单作为参考
使用示例
示例 1：获取表单 Schema
场景：获取表单的完整 Schema 结构 命令：
node .claude/skills/yida-get-schema/scripts/get-schema.js APP_XXX FORM-XXX
输出：完整的 Schema JSON，包含 pages、componentsMap 等
使用方式
node .claude/skills/yida-get-schema/scripts/get-schema.js <appType> <formUuid>
参数说明：
| 参数 | 必填 | 说明 |
|---|---|---|
appType |
是 | 应用 ID，如 APP_XXX |
formUuid |
是 | 表单 UUID，如 FORM-XXX |
示例：
node .claude/skills/get-schema/scripts/get-schema.js "APP_XXX" "FORM-XXX"
输出：日志输出到 stderr，Schema JSON 输出到 stdout。
前置依赖
- Node.js
- 项目根目录存在
.cache/cookies.json（由yida-loginskill 生成）
⚠️ 重要：若
.cache/cookies.json不存在或 Cookie 已失效，脚本会报错退出，不会自动登录。此时必须先调用yida-loginskill 完成登录，再重新执行本技能。
调用流程
- 读取项目根目录的
.cache/cookies.json获取登录态；若不存在或 Cookie 失效，脚本会报错退出，必须先调用yida-loginskill 完成登录 - 调用
getFormSchema接口获取表单 Schema - 将 Schema 输出到 stdout
文件结构
get-schema/
├── SKILL.md # 本文档
├── getFormSchema.ts # 接口类型定义参考
└── scripts/
└── get-schema.js # Schema 获取脚本
接口说明
getFormSchema（获取表单 Schema）
- 地址：
GET /alibaba/web/{appType}/_view/query/formdesign/getFormSchema.json - 参数：
| 参数 | 类型 | 必填 | 说明 |
|---|---|---|---|
formUuid |
String | 是 | 表单 UUID |
schemaVersion |
String | 否 | Schema 版本，默认 V5 |
- 返回值：
完整的表单 Schema JSON，包含
pages数组，结构与saveFormSchema保存的格式一致。各字段的fieldId（如textField_xxxxxxxx）可从 Schema 中读取。
与其他技能配合
- 获取已有表单 Schema → 本技能，用于确认字段 ID 或学习字段结构
- 创建表单页面 → 使用
yida-create-form-page技能 - 部署页面代码 → 使用
yida-publish技能
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 95 lines · 74 tokens per session scan A 606de187d20b
yida-get-schema is a skill published in the GitHub repository openyida/openyida-openclaw-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 867 once invoked, about $0.0004 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…