XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Ontology-Augmented Generation for AI agents.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/fengzhenfei-carrel)在同一工作中把 AI 连到服务的 MCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
同类工作,排序与 Skill 列表相同
| 本项 carrel | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| 作者 | FengZhenfei | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skill 数 | 1 | 1 | 1 | 5 | 1 |
| GitHub 星标 | 808 | 83,919 | 27,723 | 53,104 | 6,905 |
| 最近代码更新 | 2026年11月17日 | 2026年11月18日 | 2026年11月17日 | 2026年9月15日 | 2026年11月13日 |
| 许可证 | MIT | – | MIT | MIT | Apache-2.0 |
FengZhenfei 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodex
依据开发者 README 和 repo 中的文件夹
GitHub account FengZhenfei (person), 1 years old
★ 808 stars · code last changed 2026年11月17日
1 scripts that can run on a computer: scripts/carrel_search.py
Scripts that go online: scripts/carrel_search.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 6486a77 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (369). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /carrel-search,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/fengzhenfei/carrel.git /tmp/popnx-skill-fengzhenfei-carrel-6486a77 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-fengzhenfei-carrel-6486a77/skills/carrel-search' ~/.claude/skills/carrel-searchChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 carrel-search 文件夹放到 ~/.agents/skills/carrel-search
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/fengzhenfei/carrel.git /tmp/popnx-skill-fengzhenfei-carrel-6486a77 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fengzhenfei-carrel-6486a77/skills/carrel-search' ~/.agents/skills/carrel-searchChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/fengzhenfei/carrel.git /tmp/popnx-skill-fengzhenfei-carrel-6486a77 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fengzhenfei-carrel-6486a77/skills/carrel-search' ~/.agents/skills/carrel-search复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 carrel-search
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/fengzhenfei/carrel.git /tmp/popnx-skill-fengzhenfei-carrel-6486a77 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-fengzhenfei-carrel-6486a77/skills/carrel-search' ~/.cursor/skills/carrel-search适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月18日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: carrel-search
description: "Query the user's local knowledge bases through the Carrel search API, use original text and source images as needed in the answer, list the reference files and offer follow-up directions drawn from the knowledge graph. Use when the user asks to search the knowledge base, find evidence in the stored material, compare records, or answer from several documents together."
---
# Carrel-Search
Evidence is retrieved through Carrel's search service (`app/kb_search`, default port 9810); the agent invoking this skill understands the question, composes the answer, lists the reference files and turns the graph leads into directions the user can ask about next. The service only recalls, reranks and arranges evidence and does no generation. The display name is **Carrel-Search** and the invocation name is `$carrel-search`.
## Invocation
The client is `scripts/carrel_search.py` in this directory (Python 3.9+, standard library only). It defaults to `http://127.0.0.1:9810`; when the service runs on another machine, set the address and token through environment variables or a config file as described in [API and configuration](references/api.md). The skill contains no real token; never read or print one. `SKILL_DIR` stands for the directory containing this `SKILL.md`; replace it with the actual absolute path when executing.
```bash
python3 "$SKILL_DIR/scripts/carrel_search.py" search --question "<the user's question>"
```
- **Every command prints a compact view directly**: retrieval status, the text of the sources (each with the file and place it comes from), facts, page summaries and graph leads, and at the end "Reference files", one line per file. Quality and degradation flags remain visible; IDs, scores and debug fields are left out; document text is not: a hit is printed in full and the chunks before and after it follow it. The script keeps the complete response by itself; do not pass `--output` and do not write scripts of your own to parse it.
- **What does not fit goes to the next page; nothing is cut off**: one output has a size limit, and every page ends by saying what the next page is and how to fetch it (`show <call id> --page 2`). Where it says "read on", read every page before using the result: reading back the original and listings are always like this, and so is a search whose best sources are too long for the first page, which then says so. Where it says "the full text of the other sources, to be read when useful", the next page holds the lower-ranked sources and neighbouring chunks of a search and may be skipped. An entry too long for a page continues on the next one, which opens with the same label and "(continued from the previous page)". To save room, the path of a file is written in full only the first time and "same file as S1" afterwards, and a table header repeated from an earlier chunk reads "HEADER: same as S3". "chunk 26 of 67" at the end of a source line is its position in the document and the document's length in chunks.
- **Every entry has a label**: S a source, F a fact, P a page, E an entity, R a relation, H the neighbourhood of a subject (`H1.2` is its second relation), N a relation returned by a neighbourhood lookup. Later commands point at an entry with `--ref <call id>:<label>` instead of copying IDs or writing request files; only R cannot be used this way: a relation has two ends and is no starting point, so point at the entity entry of one of its ends. The table gives the subcommand and arguments only; each follows the same script:
| To do this | Subcommand |
|---|---|
| Read the original around a chunk | `context --ref a1b2c3:S3` (`--before` / `--after` set how many chunks on each side, 1 by default; read on with `--after` when the matter continues on the following pages). A fact (F) and a neighbourhood relation (N) can be read back the same way |
| Read returned originals without summaries and graph leads | `show a1b2c3 --sources`; follow its numbered pages or read specific S references |
| Verify document identity, publication time or version | `context --ref a1b2c3:S3 --opening` reads the first indexed chunk, preserving the document version and time scope |
| Read a whole document (a whole table, a whole report) | `context --ref a1b2c3:S3 --whole`: one command, printed page by page; a document of more than 300 chunks is read in parts with `--before` / `--after` |
| See the original picture, crop a part | `image --ref a1b2c3:S6`; `crop --ref a1b2c3:S6 --bbox 0.1,0.2,0.6,0.8`. View the saved file. `crop` only cuts a part out; it is no sharper than the original |
| Walk one hop along the graph from an entity | `neighbors --ref a1b2c3:H1` (E, `H1.2` and N work the same; `--type` takes one kind of relation only, `--limit` up to 100) |
| List the facts under an entity | `facts --ref a1b2c3:H1` (add `--property name` for one property) |
| Search again inside one document | `search --question "…" --in-doc a1b2c3:S3` (S, D, G and F references work; the knowledge base follows the document; with `--kb` given and the document outside it, the command fails) |
| Look back in time | `search`, `grep`, `neighbors` and `facts` accept `--as-of 2024` (year/month forms use the last day) or `--history` (include superseded, expired and archived records with status flags) |
| Inspect types and coverage | `catalog` includes graph overviews; use `schema --kb <KB id>` for type inheritance and relation definitions, and `stats --kb <KB id>` for coverage and time spans |
| See the full text or every field of an entry | `show a1b2c3:S9 a1b2c3:S13` (full text for sources and pages, every field for the rest); `show a1b2c3` prints the compact view of that call again and `show a1b2c3 --page 2` its next page |
- Limit the scope with arguments: `--kb` (repeatable), `--top-k`, `--block-type table` (a soft preference for table lookups). Do not hard-code KB numbers and do not assume every knowledge base has a graph. Send commands that do not depend on each other together in one step instead of waiting for them one by one.
- On a connection failure (DNS, timeout, 401/403) check the address, the service and the token as described in [API and configuration](references/api.md#connection) and tell the user the cause; it does not mean the knowledge base has no content.
## File and phrase navigation
Use `docs --kb ID --name "filename fragment"` when the question names a file or version whose exact path is unknown, or asks for an inventory. `--dir`, `--limit` and `--offset` narrow or page the list. A D reference names a registered document: `search --question "…" --in-doc a1b2c3:D1`. Registration alone does not establish semantic coverage.
Use `grep --kb ID --phrase "term"` to locate an explicit term, identifier or quotation; repeat `--phrase` and use `--in-doc a1b2c3:D1` when the document is known. The default is eight snippets per phrase; adjust `--limit` as needed. Read the relevant G hit with `context --ref a1b2c3:G1`. Phrase counts are analyzer matches, with normalized literal checks on the returned snippets, not exact occurrence counts. No hit is not proof of semantic absence. `--history` and `--as-of` preserve the requested time scope.
These are optional routes for file and phrase questions, not prerequisites for every search. Once a file is located, search within it; use semantic search and graph traversal for meaning, summaries and relationships.
## Answer flow
1. **Choose the entry point.** Usually give the user's question to `search`; for explicit files, versions or phrases use the navigation routes above. The service routes and ranks evidence. Graph-source originals use the same S references as direct hits. The skill does not rerank. Preserve model numbers, symbols, abbreviations, file names and negations; name the subjects and dimensions of a comparison. Preserve the user's knowledge-base, document, version and time scope in every follow-up. Use `--as-of` for the state at a date and `提问、分享技巧或报告无法使用。按“有帮助”数量排序。