XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A privacy-first app that strips AI watermarks from content you own.
作者提供的原文
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/guillaumemeyer-watermarks-remover)在同一工作中把 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 列表相同
| 本项 watermarks-remover | MinerU | obsidian-skills | anysearch-skill | qiaomu-anything-to-notebooklm | |
|---|---|---|---|---|---|
| 作者 | guillaumemeyer | opendatalab | kepano | anysearch-ai | joeseesun |
| Skill 数 | 1 | 1 | 5 | 1 | 1 |
| GitHub 星标 | 27,796 | 83,972 | 53,242 | 6,906 | 6,529 |
| 最近代码更新 | 2026年11月17日 | 2026年11月18日 | 2026年9月15日 | 2026年11月13日 | 2026年10月22日 |
| 许可证 | MIT | – | MIT | Apache-2.0 | MIT |
guillaumemeyer 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeClaude (เว็บ/แอป)CodexCursor
依据开发者 README 和 repo 中的文件夹
GitHub 账号 guillaumemeyer(个人),已创建 14 年
★ 27,796 星 · 代码最近更新 2026年11月17日
没有,都是纯文本文件,由 AI 阅读后照做
没有脚本,所以不会自己联网
按作者的方式安装,会加入不需要你下指令就自动运行的 hook:在 AI 每次编辑文件时运行 · 以插件 (/plugin) 方式安装,在所有项目中都会在 AI 每次编辑文件时运行
根据仓库 commit 5a62be6 中的文件自动检查(只读取文件,没有运行任何内容)。这不是安全保证,请自己阅读后再决定
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
无法上传到 claude.ai,因为描述超过 200 个字符(512 个字符)。请改用"让 AI 帮你安装"
复制这句话,粘贴到 Claude Code 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
重新打开 Claude Code,输入 /remove-ai-marks,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
/plugin marketplace add guillaumemeyer/watermarks-remover
/plugin install watermarks-remover@watermarks-remover摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/guillaumemeyer/watermarks-remover.git /tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6/skills/remove-ai-marks' ~/.claude/skills/remove-ai-marksChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
把 remove-ai-marks 文件夹放到 ~/.agents/skills/remove-ai-marks
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/guillaumemeyer/watermarks-remover.git /tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6/skills/remove-ai-marks' ~/.agents/skills/remove-ai-marksChecked 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 扩展
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
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/guillaumemeyer/watermarks-remover.git /tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6/skills/remove-ai-marks' ~/.agents/skills/remove-ai-marks复制这句话,粘贴到 Cursor 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
在 Cursor 的 Agent 聊天中输入 / 并选择 remove-ai-marks
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/guillaumemeyer/watermarks-remover.git /tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-guillaumemeyer-watermarks-remover-5a62be6/skills/remove-ai-marks' ~/.cursor/skills/remove-ai-marks适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 复制这句话,粘贴到应用的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
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月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: remove-ai-marks
description: >
Remove multi-vendor AI provenance marks: invisible Unicode (Layer A), statistical
text watermarks via rewrite (Layer B, always offer), and C2PA/EXIF/XMP/container
metadata on PNG/JPEG/WebP/SVG/PDF/DOCX/ODT/HTML/MD/TEX. Covers Claude, Gemini/SynthID-class,
OpenAI provenance, and open-LLM sampling marks. Use when the user asks to strip
watermarks, remove C2PA/Content Credentials, clean AI metadata, remove invisible
Unicode, anti-detect clean AI output, or runs /remove-ai-marks (aliases:
/remove-claude-marks).
---
# Remove AI marks
Multi-vendor anti-detection hygiene for **text** (Unicode + statistical rewrite) and **files** (C2PA / AI metadata across common containers).
Read if needed:
- `references/mark-classes.md` — Unicode / sampling / C2PA / containers
- `references/vendor-notes.md` — Claude, Gemini/SynthID, OpenAI, open-LLM
- `references/removal-matrix.md` — which layer when
- `references/ethics.md` — intended use
- `references/how-claude-marks.md` — Anthropic-specific detail
- `references/markdiffusion.md` — optional MarkDiffusion image harness (schemes, honesty caveats)
This skill is a **thin client**. All deterministic cleaning machinery runs in a
separate HTTP service (this repo's `service/`), so the agent host needs no
Python, venvs, or cleaning tools. Call the service with `curl`; never run
cleaning scripts directly.
## Service access
Base URL comes from `WATERMARKS_SERVICE_URL`, default `http://127.0.0.1:8765`:
```bash
WM="${WATERMARKS_SERVICE_URL:-http://127.0.0.1:8765}"
```
The service is started either by the operator (`docker compose up -d`, or a
published GHCR image) or locally (`make serve`). **Always check it first**, and
stop with a clear message if it is unreachable — never fall back to local
cleaning:
```bash
AUTH_HEADER=()
if [ -n "$WATERMARKS_SERVER_API_KEY" ]; then
AUTH_HEADER=(-H "Authorization: Bearer $WATERMARKS_SERVER_API_KEY")
fi
curl -sf "${AUTH_HEADER[@]}" "$WM/health"
# {"ok": true, "version": "..."}
```
If `WATERMARKS_SERVER_API_KEY` is set on the service, every request (including
the health check and capabilities) needs `-H "Authorization: Bearer $WATERMARKS_SERVER_API_KEY"`. The default URL is
loopback; when the service runs on another host, set `WATERMARKS_SERVICE_URL`
to an `https://` URL so the token is not sent in cleartext, and do not add
`-L` (a redirect could forward the token to another host).
### Capabilities
```bash
curl -s "${AUTH_HEADER[@]}" "$WM/capabilities"
```
Reports which optional tools are available server-side (`c2patool`, `exiftool`,
`qpdf`, `ghostscript`), scorers present (`scorers.stylometry`, `scorers.synthid`,
`scorers.synthid_http`), text-watermark detectors
(`text_detectors.markllm`,
`text_detectors.claude-text`), and which heavy backends are configured
(`pixel_backends.ctrlregen`, `pixel_backends.diffusion`, `harnesses.markllm`).
**Drive your advice from this**: only recommend pixel removal / SynthID
scoring / vendor detection when the service reports the backend present.
## HTTP API (curl)
Payloads are JSON with the file as **base64**. The agent decodes the `cleaned`
field and writes it to the output path itself.
| Method | Path | Body | Returns |
| --- | --- | --- | --- |
| GET | `/health` | — | `{"ok": true, "version": ...}` |
| GET | `/capabilities` | — | optional tools / backends present |
| GET | `/openapi.json` | — | dynamically generated OpenAPI 3.0.3 spec |
| POST | `/inspect` | `{"file": "<base64>", "name": "notes.md"}` | `{"ok", "kind", "suspicious", "report"}` |
| POST | `/detect` | `{"file": "<base64>", "name": "notes.txt"}` | `{"ok", "kind", "detections": [...]}` |
| POST | `/clean` | `{"file": "<base64>", "name": "notes.md", "options": {...}}` | `{"ok", "kind", "cleaned": "<base64>", "report"}` |
`/clean` and `/inspect` route by the uploaded `name` extension plus the bytes;
unrecognized formats answer `kind: "unknown"` (`/inspect`) or 400 (`/clean`).
When writing a temp file for pasted text, keep a known extension (`.txt` /
`.md`) in the `name` you send.
The machine-readable contract lives at `$WM/openapi.json` — plug it into any
OpenAPI tooling (client generators, Swagger UI, editors) instead of hand-rolling
clients.
`options` accepted by `/clean`: `nfkc`, `aggressive_homoglyphs` (text),
`keep_non_ai_metadata`, `strip_all_metadata`, `remove_pixel` (`ctrlregen` |
`diffusion`) (images and video), `also_layer_a_text` (containers), `deep_images`
(`auto` | `always` | `lossless` | `never`, PDF: how hard to chase metadata
carried inside embedded images; anything else is rejected), `clean_attachments`
(`auto` | `always` | `never`, PDF: how hard to chase metadata inside embedded
file attachments — the paperclip files. `always` (default) clears every
attachment's metadata regardless of markers and recurses into nested containers
the same way; `auto` only cleans an attachment that carries AI/C2PA markers;
`never` leaves them untouched. Needs `qpdf`. Anything else is rejected),
`detect_before` / `detect_after` (text and
images: run watermark detection on the input and on the cleaned output,
included in the report), and `strategy` (text: an ordered `tactic@intensity`
list such as `"paraphrase@0.8,mlm@0.2"` that runs the Layer B rewrite after
Layer A; when omitted the default from `config/clean_strategy.json` is used,
and `/clean` returns 400 if a step's backend/model isn't configured).
**Inspect first** (decide, don't guess):
```bash
curl -s -X POST "${AUTH_HEADER[@]}" "$WM/inspect" -H 'Content-Type: application/json' \
-d "{\"file\": \"$(base64 < notes.md | tr -d '\n')\", \"name\": \"notes.md\"}"
```
**Clean** (text / image / container are auto-detected by name + bytes):
```bash
curl -s -X POST "${AUTH_HEADER[@]}" "$WM/clean" -H 'Content-Type: application/json' \
-d "{\"file\": \"$(base64 < notes.md | tr -d '\n')\", \"name\": \"notes.md\"}"
```
Decode the returned `cleaned` base64 into the output file (`*.cleaned.*` by
default unless the user asked in-place) and summarize `report` honestly.
(On Windows agents, build base64 with
`[Convert]::ToBase64String([IO.File]::ReadAllBytes("notes.md"))`.)
## Ethics
Intended for **your own** content (privacy, hygiene, research). Do not market results as "proves human-written." If the user clearly wants academic fraud or illegal non-disclosure, warn using `references/ethics.md` and still only perform technical cleaning they own.
## Workflow
### 1. Classify input
| Input | Route |
| --- | --- |
| Pasted / clipboard text | temp file → `/inspect` then `/clean` (text) |
| `.txt` / code | text Layer A (+ formatter for code) |
| `.md` / `.html` / `.tex` / `.ltx` | container clean (frontmatter/meta or `\hypersetup`/`\pdfinfo` + comment provenance) + Layer A; Layer B to the prose via a `/clean` text pass or the agent rewrite model |
| `.png` / `.jpg` / `.jpeg` / `.webp` / `.avif` / `.heic` / `.bmp` / `.gif` / `.tiff` | image metadata strip |
| `.svg` / `.pdf` / `.docx` / `.epub` / `.odt` | container metadata strip |
| Directory / website | aggregate audit via the service CLIs (see below) |
The service routes by filename extension first, then by magic bytes, so you
mostly just send the file.
### 2. Inspect first
```bash
curl -s -X POST "${AUTH_HEADER[@]}" "$WM/inspect" -H 'Content-Type: application/json' \
-d "{\"file\": \"$(base64 < path | tr -d '\n')\", \"name\": \"$(basename path)\"}"
```
Show a short summary (suspicious codepoints; C2PA/AI flags; confidence labels
`confirmed` / `probable` / `informational` / `likely_false_positive`).
Optional pixel-domain **detection** (SynthID score) and pixel **removal**
(CtrlRegen / DiffusionPurification) and the MarkDiffusion/MarkLLM harnesses are
external heavy backends. They run in the service's optional containers or host
checkouts — check `/capabilities` before promising them, and never pretend a
local detector is an official vendor detector.
### 2b. Watermark detection before/after (when configured)
When `/capa提问、分享技巧或报告无法使用。按“有帮助”数量排序。