原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

dutis Skill

代码仓库 ↗

作者:tsonglew★ 2591 个 skill

安装

What it does

macOS default app manager for files and URL schemes, with a CLI, MCP server, and agent skills

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category 自动化与智能体
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/tsonglew-dutis.svg)](https://mcp.popnx.com/en/skills/tsonglew-dutis)

相似的 Skill

同类工作,排序与 Skill 列表相同

与相似项目对比
本项
dutis
skillsnacosanatomyleon
作者tsonglewvercel-labsalibabawheresryan22leon-ai
Skill 数11111
GitHub 星标25939,90833,52827,99617,693
最近代码更新2026年11月2日2026年11月17日2026年11月18日2026年10月19日2026年11月13日
许可证–MITApache-2.0MITMIT

tsonglew 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server

Skill 和 MCP 有什么不同

MCP = 手

把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。

Skill = 手册

教 AI 怎么做某项工作的文本文件,不连接任何服务。

有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。

适用的应用

Claude CodeCodex

依据开发者 README 和 repo 中的文件夹

安装

Is it safe?

  • Who made it

    GitHub account tsonglew (person), 11 years old

  • Use and upkeep

    ★ 259 stars, few users so far · code last changed 2026年11月2日

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit fa122f8 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

第一步:你用哪个 AI?

选择你用的应用,本页只显示该应用的安装方法

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/dutis folder again. The ZIP must have a dutis folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick dutis.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    SettingsCapabilitiesCode execution and file creation

    Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free

Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)

Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)

Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com

Option 1让 Claude Code 帮你安装

复制这句话,粘贴到 Claude Code 的对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

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,输入 /dutis,或直接提出相关任务,Claude 会自动选用

Checked against official docs 2026年11月12日 · Source: code.claude.com

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

开发者推荐的方式

安装 Node.js(如果还没有)

已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

node -v
  • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
  • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端

Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

打开 Node.js 下载页 ↗

装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

安装一次,所有需要 Node.js 的工具都能用

正在检查命令 · 通过后才会显示复制按钮

摘自开发者 README,会下载并运行开发者的代码

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.claude/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 重新打开 Claude Code,输入 /dutis,或直接提出相关任务,Claude 会自动选用

自己安装的 Skill 可用于 ChatGPT 桌面应用、Codex CLI 和 IDE 中的 Codex 扩展 · 网页版和手机版 ChatGPT 不能使用自己安装的 Skill,只能使用目录中插件自带的 Skill

ChatGPT 桌面应用

ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill

Option 1让 ChatGPT 帮你安装

在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

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

Option 2自己放入文件夹

把 dutis 文件夹放到 ~/.agents/skills/dutis

~ 是你的主文件夹($HOME)

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

安装之后

  • ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
  • 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
  • Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

网页版和手机版 ChatGPT

不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill

想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

Option 1让 Codex 帮你安装

复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

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

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.agents/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 重新打开 Codex 并提出相关任务,Codex 会列出这个 skill

Option 1让 Cursor 帮你安装

复制这句话,粘贴到 Cursor 的对话中

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

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 聊天中输入 / 并选择 dutis

Checked against official docs 2026年11月12日 · Source: cursor.com

For Terminal users

Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。

  1. 打开终端

    Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”

  2. 把 skill 文件夹复制到 ~/.cursor/skills

    这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹

    正在检查命令 · 通过后才会显示复制按钮

  3. 在 Cursor 的 Agent 聊天中输入 / 并选择 dutis

Option 1Let the AI install it

适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat

Where to install

正在检查命令 · 通过后才会显示复制按钮

正在检查命令 · 通过后才会显示复制按钮

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

For Terminal users

其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。

在 GitHub 上查看 ↗

已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹

查看原始 SKILL.md

以下文字来自开发者的 repo,不是 PopNx MCP 的指令

5,782 个字符 · 在 GitHub 打开完整文件

---
name: dutis
description: >-
  Inspect or manage macOS default applications and file associations with Dutis.
  Use when asked which app opens a file type, to change its default app, find
  installed apps that support it, manage URL scheme handlers, or restore previous
  associations. Covers extensions, UTIs, MIME types, and URL schemes. Use for
  macOS 默认打开方式、文件关联、默认应用或链接的默认处理程序. Do not use just
  to open or edit one file without changing its default association.
---

# Dutis

Use Dutis for macOS Launch Services associations. Preserve its
`inspect -> plan -> policy check -> approval -> apply -> verify` boundary.

## Workflow

1. Start read-only. Check readiness with `dutis doctor --json` and the effective
   policy with `dutis policy show --json`, then inspect the requested association
   targets and installed handlers. Use `dutis get <extension> --json` for the
   current default or `dutis query <extension> --json` for supporting apps.
   A restricted macOS shell can hide Launch Services associations and make
   `dutis get` report no default even when one exists. If that happens, try the
   read-only `dutis_get` or `dutis_handler_defaults` MCP tool when available;
   otherwise report the uncertainty instead of concluding that no default is set.
   Use `dutis handler get` or
   `dutis_handler_get` for UTIs, MIME types, URL schemes, and role-specific
   defaults. Use `dutis handler query` or `dutis_handler_query` to discover apps that
   explicitly register the requested kind and compatible role. Treat imported
   or exported UTI definitions as type evidence, not handler capability.
   When roles may differ, use `dutis handler defaults` or
   `dutis_handler_defaults` to inspect the native Launch Services role matrix
   before planning a change.
   If an event command reports a delivery failure, inspect `events health`
   (`dutis_event_health` over MCP), then inspect `events pending` only when
   event-level details are necessary. Use `events replay` only after confirming
   the configured sink is healthy.
   Preview `events archive` and `events purge` before using `--yes`; purge is
   permanent and applies only to events already moved into dead-letter storage.
2. If the user asks for a general setup or is unsure which application to use,
   inspect `dutis_profiles` / `dutis_profile`, then use `dutis_recommend` (or
   the equivalent CLI commands). Present candidate evidence and treat the
   recommendation strictly as a proposal, never as approval.
   Treat profiles returned by Dutis as the effective catalog: local
   `profiles.toml` overlays may extend built-ins or add custom typed profiles.
   Never accept caller-supplied overlay contents through MCP.
   Treat candidate `policy_eligible`, `policy_reasons`, and `source` fields as
   required evidence; do not substitute caller-provided preferences for the
   effective local policy. For UTI, MIME, and URL-scheme recommendations,
   require `declares_target = true`; typed fleet preferences apply to every
   profile recommendation but never authorize a mutation.
3. Express multi-target changes as version 2 TOML. Build a fresh plan and
   run the policy check. Treat unresolved selectors or policy violations as a
   stop condition.
4. Show the user the exact changed kinds, identifiers, roles, target bundle IDs, plan digest,
   and any policy constraints. Run dry-run before requesting approval.
5. Ask for explicit approval immediately before a write. Never infer approval
   from an earlier inspection request.
6. Apply only the reviewed digest, include a meaningful requester identity,
   and report the resulting safety snapshot and audit IDs.
7. Verify with `dutis get`, then use `dutis audit` when the user needs the full
   local record.

When the user requests integration with another local tool, prefer the global
`--event-log` or `--event-command` sink. Treat an event command as executable
code: require a user-chosen trusted absolute path, and never generate or enable
one implicitly. Events may contain application paths, bundle IDs, requester
identity, and complete plans, but never approval tokens.

For HTTPS delivery, prefer the packaged `dutis-event-http` external command.
Keep `DUTIS_HTTP_ENDPOINT` and `DUTIS_HTTP_BEARER_TOKEN` out of Dutis TOML,
plans, prompts, and audit records. Run `dutis-event-http --check --json` before
enabling it, and use a Keychain-backed wrapper for a LaunchAgent rather than
persisting transport credentials in its plist.

For monitoring requests, use `dutis_drift` or `dutis watch <config> --once`
first. Explain whether the report is `in_sync`, `drift_detected`, or
`unresolved`. Do not enable `--remediate` or install a remediating LaunchAgent
without explicit user authorization for continuous system changes. A
notification-only LaunchAgent is the safe default.

For CLI workflows, prefer `dutis plan`, `dutis policy check`, and
`dutis apply --dry-run` before the confirmed `dutis apply` command with
`--yes`, `--plan-digest`, and `--requester`. For rollback, preview with
`dutis rollback <id> --dry-run` before the confirmed command.

For MCP workflows, use `dutis_diff` and `dutis_policy_check` before
`dutis_apply`, or `dutis_rollback_plan` before `dutis_rollback`. Mutation tools
must be advertised by the server and require a fresh digest, an approval token,
and `requester`. Never invent, persist, echo, or request disclosure of a secret
token; use only a token supplied through the authorized workflow.

Do not pass recommendation output directly to a write tool. Rebuild the plan
from the reviewed proposed TOML so current state and policy are checked again.

Do not bypass Dutis with raw `duti` mutation commands. Do not weaken or rewrite
the local policy unless the user explicitly asks to change that policy.

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

来自 GitHub

GitHub 星标
259
开发者
tsonglew
许可证
未注明许可证 此 repo 未注明许可证,默认作者保留所有权利;转发或商用前请先询问作者。
最近代码更新
2026年11月2日
repo 中的 SKILL.md 文件(含译本和模板)
1
主题
agent-skills, cli, default-apps, file-associations, homebrew, launch-services, macos, mcp, rust, url-schemes