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 Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/tsonglew-dutis)Similar Skills
Same kind of work, ordered like the Skills list
1 skills (instruction sets) by tsonglew that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodex
From the maker’s README and the folders in the repo
Install
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 Nov 2, 2026
- 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
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
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
Open Skills on claude.ai and upload
+Create skillUpload a skillpick dutis.zip
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 Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code 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
Restart Claude Code, then type /dutis or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /dutis or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
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 2Put the folder there yourself
Put the dutis folder at ~/.agents/skills/dutis
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor 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
In Cursor’s Agent chat, type / and pick dutis
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick dutis
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · 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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
5,782 characters · Open the full file on 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.
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 259
- Maker
- tsonglew
- License
- No license stated This repo states no license. By default the author keeps all rights: ask before you share it or use it commercially.
- Last code change
- Nov 2, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- agent-skills, cli, default-apps, file-associations, homebrew, launch-services, macos, mcp, rust, url-schemes
- Repo
- tsonglew/dutis