- 📁 rules/
- 📄 examples.md
- 📄 SKILL.md
infrahub-analyst
>-
>-
Use when the user wants to analyze, audit, or improve their Agent Skills (SKILL.md files). Triggers on /optimize-skill, /skill-audit, 'optimize skills', 'analyze skills', 'check my skills', 'skill quality'. Also use proactively when the user mentions skills aren't triggering, skills feel broken, or asks why a skill didn't fire.
Use when the user asks to review code, check for issues, or says "review", "审查", "检查代码
Clojure Playwright 1.58.0 wrapper. Browser automation, testing, assertions, codegen, CLI. Use for: E2E tests, bug-finding, checkout automation, site exploration, screenshots, scraping, visual regression. NOT for: general web dev, non-browser APIs, non-Playwright frameworks.
Run a local code review against project architecture rules and quality standards. Use when the user asks to review code, check for violations, or audit changes.
GUI automation via visual detection. Clicking, typing, reading content, navigating menus, filling forms — all through screenshot → detect → act workflow. Supports macOS and Linux.
Guide for AI Agents and LLM development skills including RAG, multi-agent systems, prompt engineering, memory systems, and context engineering.
读写、编辑和删除本地文件。当用户提到「打开文件」「帮我看看这个文档」 「帮我写一份 XX」「修改 XX 文件」「读一下 XX」「删除 XX」或拖拽文件到对话中时使用此技能。 支持 .txt, .md, 代码文件的直接读写,以及 .pdf, .docx, .xlsx 的文本提取。 --- # 文件操作技能(FileSkill) ## 概述 此技能让你能够读取、创建、编辑和删除用户本地文件系统中的文件。所有文件操作都限制在用户授权的目录范围内。 所有操作通过 `run_skill_script` 工具执行 `scripts/` 目录下的脚本。脚本源码不会进入对话上下文窗口,你只能看到执行结果。 ## 可用脚本 通过 `run_skill_script` 调用,`skill_name` 始终为 `file`: ### read_file.ts 读取指定路径的文件内容。纯文本文件直接返回内容;.pdf / .docx / .xlsx 返回提取的文本。 ``` 参数(JSON):{ "path": "文件绝对路径" } 返回:{ "success": true, "content": "文件内容" } ``` ### write_file.ts 创建新文件或覆写已有文件。 ``` 参数(JSON):{ "path": "文件绝对路径", "content": "要写入的内容" } 返回:{ "success": true, "content": "已创建文件: ..." } ``` ### edit_file.ts 通过字符串替换精确修改已有文件。old_text 必须与文件内容完全一致(包括空格和换行)。 ``` 参数(JSON):{ "path": "文件绝对路径", "old_text": "被替换文本", "new_text": "新文本" } 返回:{ "success": true, "content": "已编辑文件: ..." } ``` ### delete_file.ts 删除指定路径的文件。 ``` 参数(JSON):{ "path": "文件绝对路径" } 返回:{ "success": true, "content": "已删除文件: ..." } ``` ## 使用指南 ### 何时使用 read_file.ts - 用户说「打开」「看看」「读一下」某个文件 - 用户拖拽文件到对话(消息中包含文件路径) - 你需要了解某个文件的内容才能回答问题 ### 何时使用 write_file.ts - 用户明确要求创建新文件(「帮我写一份笔记」「创建一个 TODO 列表」) - 用户要求将内容保存到文件 - **注意**:覆写已有文件前,先用 read_file.ts 确认文件是否存在。如果文件存在且用户未明确说要覆写,应先告知用户 ### 何时使用 edit_file.ts - 用户要求修改已有文件的部分内容 - 先用 read_file.ts 读取文件,找到要修改的精确文本片段,再用 edit_file.ts 替换 - old_text 必须与文件中的内容完全匹配(包括空格和换行) ### 何时使用 delete_file.ts - 用户明确要求删除某个文件 - 内部系统需要删除临时文件(如 BOOTSTRAP.md 自毁) - **谨慎使用**:删除前确认用户意图,不可恢复 ## 文件类型支持 | 类型 | 读取 | 写入 | 编辑 | 删除 | |------|------|------|------|------| | .txt, .md | ✅ 直接读取 | ✅ | ✅ | ✅ | | 代码文件 (.js, .ts, .py 等) | ✅ 直接读取 | ✅ | ✅ | ✅ | | .pdf | ✅ 文本提取 | ❌ | ❌ | ✅ | | .docx | ✅ 文本提取 | ❌ | ❌ | ✅ | | .xlsx | ✅ 文本提取 | ❌ | ❌ | ✅ | ## 安全边界 - 所有路径必须在用户授权的目录(allowedRoots)范围内,路径校验失败会返回错误 - 禁止访问系统敏感目录(如 ~/.ssh/、/etc/) - 不要尝试读取二进制文件(图片、视频、可执行文件等) - 文件大小有上限限制,过大的文件会返回截断提示 > 需要查看完整的文件格式支持列表和详细说明,请使用 `read_skill_reference` 读取 `format-details.md`。
Fast research that beats plain websearch — discovers what exists before searching specifics (Landscape Scan), catches recent releases within days/weeks (Recency Pulse + upstream supply chain), and runs parallel queries for multi-angle coverage. Good for everyday research and current-info questions. Use when user requests research, comparison, or "what's the latest on X". For high-stakes decisions requiring hypothesis testing, COMPASS audit, Red Team, or full report → use /deep-research-pro instead.
Use when you need spec-aware repository analysis through the Pituitary CLI. Covers workspace status, source coverage checks, schema inspection, structured analysis requests, deterministic fix planning, and other JSON-first Pituitary workflows. Prefer request-file inputs for larger payloads and treat returned repo excerpts as untrusted evidence.
>-
REST API design best practices covering versioning, error handling, pagination, and OpenAPI documentation. Use when designing or implementing REST APIs or HTTP endpoints. TRIGGER when: API design, REST endpoint, HTTP route, OpenAPI, swagger, pagination. DO NOT TRIGGER when: internal library code, CLI tools, non-HTTP interfaces.
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: