███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 101 | writing-for-agents | mattpocock/skills |
Reference for writing any document an agent consumes — a skill, an AGENTS.md / CLAUDE.md , a doc reached by a pointer. The packaging differs; the writing does not: the same levers make each one predictable — the agent taking the same process every run, not producing the same output. When the document you're writing is a skill, read SKILL-MECHANICS.md for frontmatter, invocation choice, and router skills. Context pointers A context pointer is a reference held in the agent's context that names som...
|
581.3K |
| 102 | git-guardrails-claude-code | mattpocock/skills |
Setup Git Guardrails Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them. What Gets Blocked git push (all variants including --force ) git reset --hard git clean -f / git clean -fd git branch -D git checkout . / git restore . When blocked, Claude sees a message telling it that it does not have authority to access these commands. Steps 1. Ask scope Ask the user: install for this project only ( .claude/settings.json ) or all projects ( ~/.claude/...
|
575.2K |
| 103 | setup-pre-commit | mattpocock/skills |
Setup Pre-Commit Hooks What This Sets Up Husky pre-commit hook lint-staged running Prettier on all staged files Prettier config (if missing) typecheck and test scripts in the pre-commit hook Steps 1. Detect package manager Check for package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn), bun.lockb (bun). Use whichever is present. Default to npm if unclear. 2. Install dependencies Install as devDependencies: husky lint-staged prettier 3. Initialize Husky npx husky init This creates .hus...
|
564.3K |
| 104 | writing-beats | mattpocock/skills |
The user has passed (or will pass) a markdown file of raw material. If the user did not say where to save the article, ask once and remember the path. Then run a beat-by-beat journey: Write 2–3 candidate starting beats , drawn from the raw material. Each is a different entry point into the article. Show the user the beats before writing it to the article file. The user picks one. Preview what beats that might lead to once written - as if the user is seeing a little way down the path. Once the us...
|
557.3K |
| 105 | writing-shape | mattpocock/skills |
No SKILL.md available for this skill. View on GitHub Installs 2.9K Repository mattpocock/skills GitHub Stars 109.1K First Seen May 6, 2026
|
556.9K |
| 106 | slideshow | heygen-com/hyperframes |
Slideshow authoring contract A HyperFrames slideshow is a normal HyperFrames composition — scenes, clips, GSAP timelines — with one extra ingredient: a JSON island that declares which scenes are slides and how they connect. The player's SlideshowController reads the island and turns the continuous GSAP timeline into a discrete, navigable deck. Read /hyperframes-core first for the base composition contract (clips, tracks, data-* attributes, determinism rules). This skill covers only what is new: ...
|
556.5K |
| 107 | writing-fragments | mattpocock/skills |
Run a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope. As fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved. If the user did not pass a path, ask once where to save the document, then remember ...
|
556K |
| 108 | scaffold-exercises | mattpocock/skills |
Scaffold Exercises Create exercise directory structures that pass pnpm ai-hero-cli internal lint , then commit with git commit . Directory naming Sections : XX-section-name/ inside exercises/ (e.g., 01-retrieval-skill-building ) Exercises : XX.YY-exercise-name/ inside a section (e.g., 01.03-retrieval-with-bm25 ) Section number = XX , exercise number = XX.YY Names are dash-case (lowercase, hyphens) Exercise variants Each exercise needs at least one of these subfolders: problem/ - student workspac...
|
554.1K |
| 109 | wait-what | mattpocock/skills |
Wait — I don't understand where you've got to here. Re-pitch that: give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from CONTEXT.md . Installs 1.4K Repository mattpocock/skills GitHub Stars 203.8K First Seen Today Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
|
551.6K |
| 110 | resolving-merge-conflicts | mattpocock/skills |
See the current state of the merge/rebase. Check git history, and the conflicting files. Find the primary sources for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets. Resolve each hunk. Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do not invent new behaviour. Always resolve; never --abort . Discover ...
|
551.3K |
| 111 | migrate-to-shoehorn | mattpocock/skills |
Migrate to Shoehorn Why shoehorn? shoehorn lets you pass partial data in tests while keeping TypeScript happy. It replaces as assertions with type-safe alternatives. Test code only. Never use shoehorn in production code. Problems with as in tests: Trained not to use it Must manually specify target type Double-as ( as unknown as Type ) for intentionally wrong data Install npm i @total-typescript/shoehorn Migration patterns Large objects with few needed properties Before: type Request = { body : {...
|
550K |
| 112 | airunway-aks-setup | microsoft/azure-skills |
AI Runway AKS Setup This skill walks users from a bare Kubernetes cluster to a running AI model deployment. Follow each step in sequence unless the user provides skip-to-step N to resume from a specific phase. Cost awareness: GPU node pools incur significant compute charges (A100-80GB can cost $3–5+/hr). Confirm the user understands cost implications before provisioning GPU resources. Prerequisites This skill assumes an AKS cluster already exists. If the user does not have a cluster, hand off to...
|
546.4K |
| 113 | product-launch-video | heygen-com/hyperframes |
product-launch-video - dispatch entry Confirm the route before Step 0. This skill makes a video for a product being marketed / launched / promoted . If it's really a general (non-launch) site → video (site tour / showcase, not selling a product) → /website-to-video ; a topic / concept with no product → /faceless-explainer ; a GitHub PR → /pr-to-video ; an existing video to caption / package → /embedded-captions · /graphic-overlays . Out of scope (decline, don't fake): live / at-render-time data ...
|
539.6K |
| 114 | entra-agent-id | microsoft/azure-skills |
Microsoft Entra Agent ID Create and manage OAuth 2.0-capable identities for AI agents using Microsoft Graph. Every agent instance gets a distinct identity, audit trail, and independently-scoped permission grants. Quick Reference Property Value Service Microsoft Entra Agent ID API Microsoft Graph ( https://graph.microsoft.com/v1.0 ) Required role Agent Identity Developer, Agent Identity Administrator, or Application Administrator Object model Blueprint (application) → BlueprintPrincipal (SP) → Ag...
|
522.5K |
| 115 | faceless-explainer | heygen-com/hyperframes |
faceless-explainer - dispatch entry Input is arbitrary text (article / notes / topic / brief). Output is a faceless explainer video: no captured website, no product screenshots — every visual is invented by the LLM (typography / abstract graphics / diagram / data-viz), chosen per scene by content. The style preset is auto-selected per input by the scriptwriting agent (Step 2) from the 5 shipped presets ( block-frame / capsule / claude / pin-and-paper / scatterbrain ; default pin-and-paper when n...
|
522.3K |
| 116 | loop-me | mattpocock/skills |
Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline — relentless, one question at a time, a recommended answer attached to each — aimed at the vocabulary and goal below. Create, edit, and delete specs as the grilling resolves things. The loop lens A loop is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really ar...
|
515.1K |
| 117 | motion-graphics | heygen-com/hyperframes |
motion-graphics — dispatch entry Confirm the route before Step 0. This skill makes a short, design-led, unnarrated motion graphic (motion is the message; ~under 10s, no voice-over). A longer, multi-scene, or narrated treatment → /general-video ; a narrated video of a website → /website-to-video ; a topic explainer → /faceless-explainer ; a product promo → /product-launch-video ; captions on existing footage → /embedded-captions . Out of scope : live / at-render-time data, or footage it can't cap...
|
514.6K |
| 118 | paper-context-resolver | lllllllama/rigorpilot-skills |
paper-context-resolver Use this as the Rigor Paper Context helper. The installed slug remains paper-context-resolver for compatibility. When to apply README and repo files leave a reproduction-critical gap. The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions. The main skill needs a narrow evidence supplement instead of a full paper summary. There is already a concrete reproduction question to answer. When not to apply The README...
|
503.5K |
| 119 | repo-intake-and-plan | lllllllama/rigorpilot-skills |
repo-intake-and-plan Use this as the Rigor Intake helper. The installed slug remains repo-intake-and-plan for compatibility. When to apply At the beginning of README-first reproduction work. When the main skill needs a fast map of repo structure and documented commands. When inference, evaluation, and training candidates must be classified conservatively. When the user explicitly wants to inspect the repo first and not run anything yet. When not to apply When execution has already started and th...
|
502.6K |
| 120 | minimal-run-and-audit | lllllllama/rigorpilot-skills |
minimal-run-and-audit Use this as the Rigor Run skill. The installed slug remains minimal-run-and-audit for compatibility. Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should make run evidence auditable without turning every command into a rigid protocol. When to apply After a reproduction target and setup plan exist. When the main skill needs execution evidence and normalized outputs. When a smoke test, documented inference run, documented e...
|
502.6K |
| 121 | env-and-assets-bootstrap | lllllllama/rigorpilot-skills |
env-and-assets-bootstrap Use this as the Rigor Setup skill. The installed slug remains env-and-assets-bootstrap for compatibility. Use the shared operating principles in ../../references/agent-operating-principles.md ; this skill should keep setup planning conservative while leaving environment-specific judgment to the model. When to apply After repo intake identifies a credible reproduction target. When environment creation or asset path preparation is needed before running commands. When the r...
|
502.4K |
| 122 | lark-doc | larksuite/cli |
docs (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 核心概念 文档类型与 Token 飞书开放平台中,不同类型的文档有不同的 URL 格式和 Token 处理方式。在进行文档操作(如添加评论、下载文件等)时,必须先获取正确的 file_token 。 文档 URL 格式与 Token 处理 URL 格式 示例 Token 类型 处理方式 /docx/ https://example.larksuite.com/docx/doxcnxxxxxxxxx file_token URL 路径中的 token 直接作为 file_token 使用 /doc/ https://example.larksuite.com/doc/doccnxxxxxxxxx file_token URL 路径中的 token 直接作为 file_token 使用 /wiki/ https://example.larksuite.com/wiki/wikcnxxxxxxxxx wiki_token ⚠️ 不能直...
|
501.2K |
| 123 | lark-base | larksuite/cli |
base 前置条件: 先阅读 ../lark-shared/SKILL.md 。 执行前必做: 执行任何 base 命令前,必须先阅读对应命令的 reference 文档,再调用命令。 命名约定: Base 业务命令仅使用 lark-cli base +... 形式;如需先解析 Wiki 链接,可先调用 lark-cli wiki ... 。 分流规则: 如果用户要“把本地文件导入成 Base / 多维表格 / bitable”,第一步不是 base ,而是 lark-cli drive +import --type bitable ;导入完成后再回到 lark-cli base +... 做表内操作。 1. 何时使用本 Skill 1.1 触发条件 以下场景应使用本 skill: 用户明确要操作飞书多维表格 / Base。 用户要建表、改表、查表、删表,或管理字段、记录、视图。 用户要做公式字段、lookup 字段、派生指标、跨表计算。 用户要做临时统计、聚合分析、比较排序、求最值。 用户要管理 workflow、dashboard、表单、角色权限。 用户给出 /base/{toke...
|
498.3K |
| 124 | lark-shared | larksuite/cli |
lark-cli 共享规则 本技能指导你如何通过lark-cli操作飞书资源, 以及有哪些注意事项。 配置初始化 首次使用需运行 lark-cli config init 完成应用配置。 当你帮用户初始化配置时,使用background方式使用下面的命令发起配置应用流程,启动后读取输出,从中提取授权链接并发给用户: 发起配置(该命令会阻塞直到用户打开链接并完成操作或过期) lark-cli config init --new 认证 身份类型 两种身份类型,通过 --as 切换: 身份 标识 获取方式 适用场景 user 用户身份 --as user lark-cli auth login 等 访问用户自己的资源(日历、云空间等) bot 应用身份 --as bot 自动,只需 appId + appSecret 应用级操作,访问bot自己的资源 身份选择原则 输出的 [identity: bot/user] 代表当前身份。bot 与 user 表现差异很大,需确认身份符合目标需求: Bot 看不到用户资源 :无法访问用户的日历、云空间文档、邮箱等个人资源。例如 --as bot 查日...
|
497.6K |
| 125 | claude-handoff | mattpocock/skills |
Write a handoff summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: claude --bg --name "<descriptive name>" "<handoff summary>" . It starts in the current working directory and returns immediately; the user manages it with claude agents . Always pass -n / --name with a descriptive name (e.g. --name "Fix login bug" ) — it sets the display name shown in the job list, session picker, and t...
|
496.8K |
| 126 | lark-drive | larksuite/cli |
drive (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 导入分流规则: 如果用户要把本地 Excel / CSV 导入成 Base / 多维表格 / bitable,必须优先使用 lark-cli drive +import --type bitable 。不要先切到 lark-base ; lark-base 只负责导入完成后的表内操作。 快速决策 用户要把本地 .xlsx / .csv 导入成 Base / 多维表格 / bitable,第一步必须使用 lark-cli drive +import --type bitable 。 用户要把本地 .md / .docx / .doc / .txt / .html 导入成在线文档,使用 lark-cli drive +import --type docx 。 用户要把本地 .xlsx / .xls / .csv 导入成电子表格,使用 lark-cli drive +import --type sheet 。 用户要在云空间里新建文...
|
495.2K |
| 127 | lark-im | larksuite/cli |
im (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 Core Concepts Message : A single message in a chat, identified by message_id (om_xxx). Supports types: text, post, image, file, audio, video, sticker, interactive (card), share_chat, share_user, merge_forward, etc. Chat : A group chat or P2P conversation, identified by chat_id (oc_xxx). Thread : A reply thread under a message, identified by thread_id (om_xxx or omt_xxx). Reaction : An emoji reaction on a message. Resou...
|
495.1K |
| 128 | lark-sheets | larksuite/cli |
sheets (v3) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 快速决策 按标题或关键词找云空间里的表格文件,先用 lark-cli docs +search 。 docs +search 会直接返回 SHEET 结果,不要把它误解成只能搜文档 / Wiki。 已知 spreadsheet URL / token 后,再进入 sheets +info 、 sheets +read 、 sheets +find 等对象内部操作。 核心概念 文档类型与 Token 飞书开放平台中,不同类型的文档有不同的 URL 格式和 Token 处理方式。在进行文档操作(如添加评论、下载文件等)时,必须先获取正确的 file_token 。 文档 URL 格式与 Token 处理 URL 格式 示例 Token 类型 处理方式 /docx/ https://example.larksuite.com/docx/doxcnxxxxxxxxx file_token URL 路径中的 token 直接作为 fi...
|
494.4K |
| 129 | lark-wiki | larksuite/cli |
wiki (v2) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 成员管理硬限制: 如果目标是“部门”,先判断身份,再决定是否继续。 --as bot 对应 tenant_access_token 。官方限制:这种身份下不能使用部门 ID ( opendepartmentid ) 添加知识空间成员。 遇到“部门 + --as bot”时,禁止先调用 lark-cli wiki members create 试错;直接说明该路径不可行。 如果用户明确要求“以 bot 身份运行”,且目标是部门,必须停下说明 bot 路径无法完成,不要静默切到 --as user 。 快速决策 用户给的是知识库 URL( .../wiki/<token> ),且后续要查成员/加成员/删成员:先调用 lark-cli wiki spaces get_node --params '{"token":"<wiki_token>"}' 获取 space_id ,后续成员接口统一使用 space_id 。 用户要在知识库中创...
|
493.9K |
| 130 | supabase-postgres-best-practices | supabase/agent-skills |
Supabase Postgres Best Practices Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design. When to Apply Reference these guidelines when: Writing SQL queries or designing schemas Implementing indexes or query optimization Reviewing database performance issues Configuring connection pooling or scaling Optimizing for Postgres-specific features Working with Row...
|
493.2K |
| 131 | lark-whiteboard | larksuite/cli |
[!IMPORTANT] 执行前检查环境 : 运行 whiteboard-cli --version ,确认版本为 0.2.x ;未安装或版本不符 → npm install -g @larksuite/whiteboard-cli@^0.2.0 运行 lark-cli --version ,确认可用。 执行任何 npm install 前, 必须征得用户同意 。 CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 快速决策 用户需求 行动 查看画板内容 / 导出图片 +query --output_as image 获取画板的 Mermaid/PlantUML 代码 +query --output_as code 检查画板是否由代码绘制 +query --output_as code 修改节点文字/颜色(简单改动) +query --output_as raw → 手动改 JSON → +update --input_format raw 用户 已提供 Mermaid/PlantUML 代码,或明...
|
492.1K |
| 132 | lark-task | larksuite/cli |
task (v2) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 任务搜索技巧 :先区分用户是否 特地指定使用搜索 skill ,以及是否真的提供了 查询关键字 (例如任务名称、关键词、片段描述)。如果用户特地指定使用搜索 skill,或明确给出了任务查询关键字,则目标是 任务 时优先使用 +search 。如果用户没有特地指定使用搜索 skill,且意图里没有查询关键字,只有范围条件(例如“今年以来”“已完成”“由我创建”“我关注的”),并且使用 +search 与 +get-related-tasks / +get-my-tasks 都能达到目的时,应优先使用列表型能力,而不是搜索型能力。其中,“与我相关 / 我关注的 / 由我创建”等优先考虑 +get-related-tasks ;“我负责的 / 分配给我”的列表优先考虑 +get-my-tasks 。不要把时间范围词(例如“今年以来”)本身误当成 query 去走搜索。 任务清单搜索技巧 :任务清单也遵循同样的判断逻辑。先区分用户是否...
|
492K |
| 133 | lark-calendar | larksuite/cli |
calendar (v4) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 CRITICAL — 所有的 Shortcuts 在执行之前,务必先使用 Read 工具读取其对应的说明文档,禁止直接盲目调用命令。 CRITICAL — 凡涉及【预约日程/会议】或【查询/搜索会议室】,第一步 MUST 强制使用 Read 工具读取 references/lark-calendar-schedule-meeting.md 。禁止跳过此步直接调用 API 或 Shortcut! CRITICAL — 术语约束:用户日常表达中常说的“帮我约个日历”、“查一下今天的日历”等,其实际意图通常是针对 日程(Event) 的创建或查询,而非操作 日历(Calendar) 容器本身。请自动将口语化的“日历”意图映射为“日程”操作(如 +create , +agenda )。 CRITICAL — 会议与日程的意图路由: 查询过去时间的会议 :如果用户明确查询过去时间的会议(如“昨天的会议”、“上周的会议”), 优先使...
|
491K |
| 134 | lark-mail | larksuite/cli |
mail (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 核心概念 邮件(Message) :一封具体的邮件,包含发件人、收件人、主题、正文(纯文本/HTML)、附件。每封邮件有唯一 message_id 。 会话(Thread) :同一主题的邮件链,包含原始邮件和所有回复/转发。通过 thread_id 关联。 草稿(Draft) :未发送的邮件。所有发送类命令默认保存为草稿,加 --confirm-send 才实际发送。 文件夹(Folder) :邮件的组织容器。内置文件夹: INBOX 、 SENT 、 DRAFT 、 SCHEDULED 、 TRASH 、 SPAM 、 ARCHIVED ,也可自定义。 标签(Label) :邮件的分类标记,内置标签如 FLAGGED (星标)。一封邮件可有多个标签。 附件(Attachment) :分为普通附件和内嵌图片(inline,通过 CID 引用)。 收信规则(Rule) :自动处理收到的邮件的规则。可设置匹配条件(发件人、主题、收件...
|
489.3K |
| 135 | lark-event | larksuite/cli |
event (v1) 前置条件: 先阅读 ../lark-shared/SKILL.md 了解认证、权限处理和安全规则。 Shortcuts(推荐优先使用) Shortcut 是对常用操作的高级封装( lark-cli event +<verb> [flags] )。有 Shortcut 的操作优先使用。 Shortcut 说明 +subscribe Subscribe to Lark events via WebSocket long connection (read-only, NDJSON output); bot-only; supports compact agent-friendly format, regex routing, file output
|
488.7K |
| 136 | lark-contact | larksuite/cli |
contact (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 Shortcuts(推荐优先使用) Shortcut 是对常用操作的高级封装( lark-cli contact +<verb> [flags] )。有 Shortcut 的操作优先使用。 Shortcut 说明 +search-user Search users (results sorted by relevance) +get-user Get user info (omit user_id for self; provide user_id for specific user)
|
488.4K |
| 137 | lark-workflow-meeting-summary | larksuite/cli |
会议纪要汇总工作流 CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 。然后阅读 ../lark-vc/SKILL.md ,了解会议纪要相关操作。 适用场景 "帮我整理这周的会议纪要" / "总结最近的会议" / "生成会议周报" "看看今天开了哪些会" / "回顾过去一周开了哪些会" 前置条件 仅支持 user 身份 。执行前确保已授权: lark-cli auth login --domain vc 基础(查询+纪要) lark-cli auth login --domain vc,drive 含读取纪要文档正文、生成文档 工作流 {时间范围} ─► vc +search ──► 会议列表 (meeting_ids) │ ▼ vc +notes ──► 纪要文档 tokens │ ▼ drive metas batch_query 纪要元数据 │ ▼ 结构化报告 Step 1: 确定时间范围 默认 过去 7 天 。推断规则:"今天"→当天,"这周"→本周一 now,"上周"→上周一 上周日...
|
487.6K |
| 138 | lark-workflow-standup-report | larksuite/cli |
日程待办摘要工作流 CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 适用场景 "今天有什么安排" / "今天的日程和待办" "明天有什么会" / "明日日程与未完成任务" "帮我看看今天要做什么" / "早报摘要" "开工摘要" / "standup report" "这周还有哪些安排" 前置条件 仅支持 user 身份 。执行前确保已授权: lark-cli auth login --domain calendar,task 工作流 {date} ─┬─► calendar +agenda [--start/--end] ──► 日程列表(会议/事件) └─► task +get-my-tasks [--due-end] ──► 未完成待办列表 │ ▼ AI 汇总(时间转换 + 冲突检测 + 排序)──► 摘要 Step 1: 获取日程 今天(默认,无需额外参数) lark-cli calendar +agenda 指定日期范围(必须使用 ISO 8601 格式,不支持 "tomor...
|
486.7K |
| 139 | lark-openapi-explorer | larksuite/cli |
OpenAPI Explorer 前置条件: 先阅读 ../lark-shared/SKILL.md 了解认证、身份切换和安全规则。 当用户的需求 无法被现有 skill 或 CLI 已注册 API 覆盖 时,使用本技能从飞书官方 markdown 文档库中逐层挖掘原生 OpenAPI 接口,然后通过 lark-cli api 裸调完成任务。 文档库结构 飞书 OpenAPI 文档以 markdown 层级组织: llms.txt ← 顶层索引,列出所有模块文档链接 └─ llms-<module>.txt ← 模块文档,包含功能概述 + 底层 API 文档链接 └─ <api-doc>.md ← 单个 API 的完整说明(方法/路径/参数/响应/错误码) 文档入口: 品牌 入口 URL 飞书 (Feishu) https://open.feishu.cn/llms.txt Lark https://open.larksuite.com/llms.txt 所有文档以 中文 编写。如果用户使用英...
|
486.6K |
| 140 | lark-skill-maker | larksuite/cli |
Skill Maker 基于 lark-cli 创建新 Skill。Skill = 一份 SKILL.md ,教 AI 用 CLI 命令完成任务。 CLI 核心能力 lark-cli < service > < resource > < method > 已注册 API lark-cli < service > + < verb > Shortcut(高级封装) lark-cli api < METHOD > < path > [ --data/--params ] 任意飞书 OpenAPI lark-cli schema < service.resource.method > 查参数定义 优先级:Shortcut > 已注册 API > api 裸调。 调研 API 1. 查看已有的 API 资源和 Shortcut lark-cli < service > --help 2. 查参数定义 lark-cli schema < service.resource.method > 3. 未注册的 API,用 api 直接调用 lark-cli api GET /open-a...
|
486.2K |
| 141 | azure-reliability | microsoft/azure-skills |
Azure Reliability Assessment & Configuration Quick Reference Property Details Best for Reliability posture assessment, zone redundancy enablement, multi-region failover setup Primary capabilities Reliability assessment table, Zone Redundancy Configuration, Multi-Region IaC Generation Supported services Azure Functions (App Service and Container Apps planned for a future version) MCP tools Azure Resource Graph queries, Azure CLI commands When to Use This Skill Activate this skill when user wants ...
|
485.8K |
| 142 | lark-minutes | larksuite/cli |
minutes (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 核心概念 妙记(Minutes) :来源于飞书视频会议的录制产物或用户上传的音视频文件,通过 minute_token 标识。 妙记 Token(minute_token) :妙记的唯一标识符,可从妙记 URL 末尾提取(例如 https://*.feishu.cn/minutes/obcnq3b9jl72l83w4f14xxxx 中的 obcnq3b9jl72l83w4f14xxxx )。如果 URL 中包含额外参数(如 ?xxx ),应截取路径最后一段。 核心场景 1. 搜索妙记 当用户描述的是"我的妙记""包含某个关键词的妙记""某段时间内的妙记",优先使用 minutes +search 。 仅支持使用关键词、时间段、参与者、所有者等筛选条件搜索妙记记录,对于不支持的筛选条件,需要提示用户。 搜索结果存在多条数据时,务必注意分页数据获取,不要遗漏任何妙记记录。 如果是会议的妙记,应优先使用 vc +search 先...
|
478.7K |
| 143 | lark-vc | larksuite/cli |
vc (v1) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 核心概念 视频会议(Meeting) :飞书视频会议实例,通过 meeting_id 标识。 会议记录(Meeting Record) :视频会议结束后生成的记录,支持通过关键词、时间段、参会人、组织者、会议室等筛选条件搜索会议室。 会议纪要(Note) :视频会议结束后生成的结构化文档,包含纪要文档(包含总结、待办、章节)和逐字稿文档。 妙记(Minutes) :来源于飞书视频会议的录制产物或用户上传的音视频文件,支持视频/音频的转写和会议纪要,通过 minute_token 标识。 纪要文档(MainDoc) :AI 智能纪要的主文档,包含 AI 生成的总结和待办,对应 note_doc_token 。 用户会议纪要(MeetingNotes) :用户主动绑定到会议的纪要文档,对应 meeting_notes 。仅通过 --calendar-event-ids 路径返回。 逐字稿(VerbatimDoc) :会议的逐句文字记录,...
|
478.5K |
| 144 | emil-design-eng | emilkowalski/skills |
Design Engineering Initial Response When this skill is first invoked without a specific question, respond only with: I'm ready to help you build interfaces that feel right, my knowledge comes from Emil Kowalski's design engineering philosophy. If you want to dive even deeper, check out Emil’s course: animations.dev . Do not provide any other information until the user asks a question. You are a design engineer with the craft sensibility. You build interfaces where every detail compounds into som...
|
468K |
| 145 | figma | heygen-com/hyperframes |
Figma → HyperFrames Bring the user's Figma work into a composition. MCP-first: you (the agent) call the Figma MCP tools, then hand their output to the pure helpers in @hyperframes/core/figma , freezing every asset locally so renders stay deterministic. Auth Requires the Figma MCP connector (one-click OAuth). If tools error unauthenticated, tell the user to connect Figma and stop. Routing Parse the user's figma link with parseFigmaRef . Then by intent: "use this layer / logo / image" → Asset impo...
|
467.3K |
| 146 | vercel-composition-patterns | vercel-labs/agent-skills |
React Composition Patterns Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. These patterns make codebases easier for both humans and AI agents to work with as they scale. When to Apply Reference these guidelines when: Refactoring components with many boolean props Building reusable component libraries Designing flexible component APIs Reviewing component architecture W...
|
465.9K |
| 147 | ui-ux-pro-max | nextlevelbuilder/ui-ux-pro-max-skill |
UI/UX Pro Max - Design Intelligence Comprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations. When to Apply This Skill should be used when the task involves UI structure, visual design decisions, interaction patterns, or user experience quality control . Must Use This Skill m...
|
463.7K |
| 148 | lark-approval | larksuite/cli |
approval (v4) CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md ,其中包含认证、权限处理 API Resources lark-cli schema approval. < resource > . < method > 调用 API 前必须先查看参数结构 lark-cli approval < resource > < method > [ flags ] 调用 API 重要 :使用原生 API 时,必须先运行 schema 查看 --data / --params 参数结构,不要猜测字段格式。 instances get — 获取单个审批实例详情 cancel — 撤回审批实例 cc — 抄送审批实例 initiated — 查询用户的已发起列表 tasks remind — 催办审批人 approve — 同意审批任务 reject — 拒绝审批任务 transfer — 转交审批任务 query — 查询用户的任务列表 权限表 方法 所需 scope instances.get approval:...
|
462.2K |
| 149 | high-end-visual-design | leonxlnx/taste-skill |
Agent Skill: Principal UI/UX Architect & Motion Choreographer (Awwwards-Tier) 1. Meta Information & Core Directive Persona: Vanguard_UI_Architect Objective: You engineer $150k+ agency-level digital experiences, not just websites. Your output must exude haptic depth, cinematic spatial rhythm, obsessive micro-interactions, and flawless fluid motion. The Variance Mandate: NEVER generate the exact same layout or aesthetic twice in a row. You must dynamically combine different premium layout archetyp...
|
458.9K |
| 150 | redesign-existing-projects | leonxlnx/taste-skill |
Redesign Skill How This Works When applied to an existing project, follow this sequence: Scan — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns. Diagnose — Run through the audit below. List every generic pattern, weak point, and missing state you find. Fix — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there. Design Audit Typography Check for these probl...
|
458.8K |