[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TBDDBH5P3DV2SHDFXEH8Z":3,"skill-same:01M77TBDDBH5P3DV2SHDFXEH8Z":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77TBDDBH5P3DV2SHDFXEH8Z","lark-openapi-explorer",null,"飞书\u002FLark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Flark-openapi-explorer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"飞书\u002FLark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。\"\n---\n# OpenAPI Explorer\n\n> **前置条件：** 先阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 了解认证、身份切换和安全规则。\n\n当用户的需求**无法被现有 skill 或 CLI 已注册 API 覆盖**时，使用本技能从飞书官方 markdown 文档库中逐层挖掘原生 OpenAPI 接口，然后通过 `lark-cli api` 裸调完成任务。\n\n## 文档库结构\n\n飞书 OpenAPI 文档以 markdown 层级组织：\n\n```\nllms.txt                          ← 顶层索引，列出所有模块文档链接\n  └─ llms-\u003Cmodule>.txt            ← 模块文档，包含功能概述 + 底层 API 文档链接\n       └─ \u003Capi-doc>.md            ← 单个 API 的完整说明（方法\u002F路径\u002F参数\u002F响应\u002F错误码）\n```\n\n文档入口：\n\n| 品牌 | 入口 URL |\n|------|----------|\n| 飞书 (Feishu) | `https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt` |\n| Lark | `https:\u002F\u002Fopen.larksuite.com\u002Fllms.txt` |\n\n> 所有文档以**中文**编写。如果用户使用英文交流，需将文档内容翻译为英文后输出。\n\n## 挖掘流程\n\n严格按以下步骤逐层检索，**不要跳步或猜测 API**：\n\n### Step 1：确认现有能力不足\n\n```bash\n# 先检查是否已有对应的 skill 或已注册 API\nlark-cli \u003C可能的service> --help\n```\n\n如果已有对应命令或 shortcut，直接使用，**不需要继续挖掘**。\n\n### Step 2：从顶层索引定位模块\n\n用 WebFetch 获取顶层索引，找到与需求相关的模块文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt\n  → 提取问题：\"列出所有模块文档链接，找出与 \u003C用户需求关键词> 相关的链接\"\n```\n\n- 飞书品牌使用 `open.feishu.cn`\n- Lark 品牌使用 `open.larksuite.com`\n- 如不确定用户品牌，默认使用飞书\n\n### Step 3：从模块文档定位具体 API\n\n用 WebFetch 获取模块文档，找到具体 API 的文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms-docs\u002Fzh-CN\u002Fllms-\u003Cmodule>.txt\n  → 提取问题：\"找出与 \u003C用户需求> 相关的 API 说明和文档链接\"\n```\n\n### Step 4：获取 API 完整规范\n\n用 WebFetch 获取具体 API 文档，提取完整的调用规范：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fdocument\u002Fserver-docs\u002F...\u002F\u003Capi>.md\n  → 提取问题：\"返回完整 API 规范：HTTP 方法、URL 路径、路径参数、查询参数、请求体字段（名称\u002F类型\u002F必填\u002F说明）、响应字段、所需权限、错误码\"\n```\n\n### Step 5：通过 CLI 调用 API\n\n使用 `lark-cli api` 裸调：\n\n```bash\n# GET 请求\nlark-cli api GET \u002Fopen-apis\u002F\u003Cpath> --params '{\"key\":\"value\"}'\n\n# POST 请求\nlark-cli api POST \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# PUT 请求\nlark-cli api PUT \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# DELETE 请求\nlark-cli api DELETE \u002Fopen-apis\u002F\u003Cpath>\n```\n\n## 输出规范\n\n向用户呈现挖掘结果时，按以下格式组织：\n\n1. **API 名称与功能**：一句话描述\n2. **HTTP 方法与路径**：`METHOD \u002Fopen-apis\u002F...`\n3. **关键参数**：列出必填和常用可选参数\n4. **所需权限**：scope 列表\n5. **调用示例**：给出 `lark-cli api` 的完整命令\n6. **注意事项**：频率限制、特殊约束等\n\n如果用户使用英文交流，将以上所有内容翻译为英文。\n\n## 安全规则\n\n- **写入\u002F删除类 API**（POST\u002FPUT\u002FDELETE）调用前必须确认用户意图\n- 建议先用 `--dry-run` 预览请求（如支持）\n- 不要猜测 API 路径或参数——必须从文档中获取确认\n- 涉及敏感操作（删除群、移除成员等）时，向用户说明影响范围\n\n## 使用场景示例\n\n### 场景 1：用户需要拉人进群（未被 CLI 封装）\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 发现没有 chat_members 相关的 create 命令\n\n# Step 2-4: 通过文档挖掘获得 API 规范\n# → POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fmembers\n\n# Step 5: 调用\nlark-cli api POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fmembers \\\n  --data '{\"id_list\":[\"ou_xxx\",\"ou_yyy\"]}' \\\n  --params '{\"member_id_type\":\"open_id\"}'\n```\n\n### 场景 2：用户需要设置群公告\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 没有 announcement 相关命令\n\n# Step 2-4: 挖掘文档\n# → PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fannouncement\n\n# Step 5: 调用\nlark-cli api PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fannouncement \\\n  --data '{\"revision\":\"0\",\"requests\":[\"\u003Chtml>公告内容\u003C\u002Fhtml>\"]}'\n```\n\n## 参考\n\n- [lark-shared](..\u002Flark-shared\u002FSKILL.md) — 认证和全局参数\n- [lark-skill-maker](..\u002Flark-skill-maker\u002FSKILL.md) — 如需将挖掘到的 API 固化为新 Skill\n","# OpenAPI Explorer\n\n> **前置条件：** 先阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 了解认证、身份切换和安全规则。\n\n当用户的需求**无法被现有 skill 或 CLI 已注册 API 覆盖**时，使用本技能从飞书官方 markdown 文档库中逐层挖掘原生 OpenAPI 接口，然后通过 `lark-cli api` 裸调完成任务。\n\n## 文档库结构\n\n飞书 OpenAPI 文档以 markdown 层级组织：\n\n```\nllms.txt                          ← 顶层索引，列出所有模块文档链接\n  └─ llms-\u003Cmodule>.txt            ← 模块文档，包含功能概述 + 底层 API 文档链接\n       └─ \u003Capi-doc>.md            ← 单个 API 的完整说明（方法\u002F路径\u002F参数\u002F响应\u002F错误码）\n```\n\n文档入口：\n\n| 品牌 | 入口 URL |\n|------|----------|\n| 飞书 (Feishu) | `https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt` |\n| Lark | `https:\u002F\u002Fopen.larksuite.com\u002Fllms.txt` |\n\n> 所有文档以**中文**编写。如果用户使用英文交流，需将文档内容翻译为英文后输出。\n\n## 挖掘流程\n\n严格按以下步骤逐层检索，**不要跳步或猜测 API**：\n\n### Step 1：确认现有能力不足\n\n```bash\n# 先检查是否已有对应的 skill 或已注册 API\nlark-cli \u003C可能的service> --help\n```\n\n如果已有对应命令或 shortcut，直接使用，**不需要继续挖掘**。\n\n### Step 2：从顶层索引定位模块\n\n用 WebFetch 获取顶层索引，找到与需求相关的模块文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt\n  → 提取问题：\"列出所有模块文档链接，找出与 \u003C用户需求关键词> 相关的链接\"\n```\n\n- 飞书品牌使用 `open.feishu.cn`\n- Lark 品牌使用 `open.larksuite.com`\n- 如不确定用户品牌，默认使用飞书\n\n### Step 3：从模块文档定位具体 API\n\n用 WebFetch 获取模块文档，找到具体 API 的文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms-docs\u002Fzh-CN\u002Fllms-\u003Cmodule>.txt\n  → 提取问题：\"找出与 \u003C用户需求> 相关的 API 说明和文档链接\"\n```\n\n### Step 4：获取 API 完整规范\n\n用 WebFetch 获取具体 API 文档，提取完整的调用规范：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fdocument\u002Fserver-docs\u002F...\u002F\u003Capi>.md\n  → 提取问题：\"返回完整 API 规范：HTTP 方法、URL 路径、路径参数、查询参数、请求体字段（名称\u002F类型\u002F必填\u002F说明）、响应字段、所需权限、错误码\"\n```\n\n### Step 5：通过 CLI 调用 API\n\n使用 `lark-cli api` 裸调：\n\n```bash\n# GET 请求\nlark-cli api GET \u002Fopen-apis\u002F\u003Cpath> --params '{\"key\":\"value\"}'\n\n# POST 请求\nlark-cli api POST \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# PUT 请求\nlark-cli api PUT \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# DELETE 请求\nlark-cli api DELETE \u002Fopen-apis\u002F\u003Cpath>\n```\n\n## 输出规范\n\n向用户呈现挖掘结果时，按以下格式组织：\n\n1. **API 名称与功能**：一句话描述\n2. **HTTP 方法与路径**：`METHOD \u002Fopen-apis\u002F...`\n3. **关键参数**：列出必填和常用可选参数\n4. **所需权限**：scope 列表\n5. **调用示例**：给出 `lark-cli api` 的完整命令\n6. **注意事项**：频率限制、特殊约束等\n\n如果用户使用英文交流，将以上所有内容翻译为英文。\n\n## 安全规则\n\n- **写入\u002F删除类 API**（POST\u002FPUT\u002FDELETE）调用前必须确认用户意图\n- 建议先用 `--dry-run` 预览请求（如支持）\n- 不要猜测 API 路径或参数——必须从文档中获取确认\n- 涉及敏感操作（删除群、移除成员等）时，向用户说明影响范围\n\n## 使用场景示例\n\n### 场景 1：用户需要拉人进群（未被 CLI 封装）\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 发现没有 chat_members 相关的 create 命令\n\n# Step 2-4: 通过文档挖掘获得 API 规范\n# → POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fmembers\n\n# Step 5: 调用\nlark-cli api POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fmembers \\\n  --data '{\"id_list\":[\"ou_xxx\",\"ou_yyy\"]}' \\\n  --params '{\"member_id_type\":\"open_id\"}'\n```\n\n### 场景 2：用户需要设置群公告\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 没有 announcement 相关命令\n\n# Step 2-4: 挖掘文档\n# → PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fannouncement\n\n# Step 5: 调用\nlark-cli api PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fannouncement \\\n  --data '{\"revision\":\"0\",\"requests\":[\"\u003Chtml>公告内容\u003C\u002Fhtml>\"]}'\n```\n\n## 参考\n\n- [lark-shared](..\u002Flark-shared\u002FSKILL.md) — 认证和全局参数\n- [lark-skill-maker](..\u002Flark-skill-maker\u002FSKILL.md) — 如需将挖掘到的 API 固化为新 Skill\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Flark-openapi-explorer",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill lark-openapi-explorer",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill lark-openapi-explorer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill lark-openapi-explorer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Flark-openapi-explorer\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]