Skip to main content
skill CX Codex

markedit-tools — Claude Code skill: what it does, how to install

markedit-tools manages the MarkEdit markdown editor on macOS: installs updates, handles extensions, and edits settings via Claude Code.

Apache-2.0 ★ 173 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sammcj/agentic-coding --skill markedit-tools -a claude-code
Open on GitHub

What markedit-tools does

This skill automates maintenance tasks for MarkEdit on macOS. It retrieves releases directly from GitHub, asks which DMG build to download, moves the app bundle into /Applications, and relaunches the editor using AppleScript.

It also handles scripts and styling. The skill downloads extension files into the app container folder, supports lite builds, and updates settings.json. Because configuration files are tracked with chezmoi, the skill runs chezmoi add --encrypt on modified files but leaves git commits untouched.

What it helps with

  • download and deploy the latest MarkEdit release
  • install or remove JavaScript extensions for MarkEdit
  • inspect installed extensions with file sizes and dates
  • update advanced parameters in settings.json

Example prompts for the agent

  • Upgrade MarkEdit to the latest release
  • Install the lite version of the MarkEdit Preview extension
  • Turn on idle auto-save in MarkEdit settings

How to install markedit-tools

1Skills CLI (Vercel)

npx skills add sammcj/agentic-coding --skill markedit-tools -a claude-code

2Manually: put the files in place

~/.claude/skills/markedit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/markedit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about markedit-tools

How to install markedit-tools in Claude Code?

Run npx skills add sammcj/agentic-coding --skill markedit -a claude-code. Alternatively, place the file directly at ~/.claude/skills/markedit/SKILL.md.

What does markedit-tools do?

It coordinates app updates, downloads extensions from GitHub into the container folder, and edits editor configuration files.

Where does the skill store extension files?

Extensions are saved to ~/Library/Containers/app.cyan.markedit/Data/Documents/scripts/ before the editor relaunches.

Source text

SKILL.md · Apache-2.0
---
name: markedit-tools
description: Provides tools for managing MarkEdit, a macOS markdown editor
---

# Purpose

Help users configure and extend [MarkEdit](https://github.com/MarkEdit-app/MarkEdit), a free and open-source markdown editor for macOS.

## Key Capabilities

- Upgrade the MarkEdit app
- Install, upgrade, and manage MarkEdit extensions
- Configure MarkEdit advanced settings
- Answer questions related to MarkEdit

## Core Concepts

### File Locations

| Path | Description |
|------|-------------|
| `~/Library/Containers/app.cyan.markedit/Data/Documents/scripts/` | Extensions directory |
| `~/Library/Containers/app.cyan.markedit/Data/Documents/settings.json` | Advanced settings |
| `~/Library/Containers/app.cyan.markedit/Data/Documents/editor.css` | Custom stylesheets |
| `~/Library/Containers/app.cyan.markedit/Data/Documents/editor.js` | Custom JavaScript |

### Extension URLs

When a user provides an extension name, download from this URL pattern:

```
https://github.com/MarkEdit-app/extension-name/blob/main/dist/extension-name-kebab-cased.js?raw=true
```

Always normalise the extension name to kebab-case.

For example, [MarkEdit Preview](https://github.com/MarkEdit-app/MarkEdit-preview) is available at:
`https://github.com/MarkEdit-app/MarkEdit-preview/blob/main/dist/markedit-preview.js?raw=true`

When a user requests a "lite" build, it is located in the `lite` subfolder under `dist`:
`https://github.com/MarkEdit-app/MarkEdit-preview/blob/main/dist/lite/markedit-preview.js?raw=true`

The filename is identical to the standard build; do not add a `-lite` suffix.

If the dist file is not found (non-200 response), fall back to the GitHub **latest release** asset:

1. Fetch the latest release tag from the GitHub API:
   `https://api.github.com/repos/MarkEdit-app/extension-name/releases/latest`
2. Read the `tag_name` field from the response.
3. Download the asset using:

```
https://github.com/MarkEdit-app/extension-name/releases/download/{tag_name}/extension-name-kebab-cased.js
```

For example, if `dist/markedit-preview.js` is not available in the repository and the latest release tag is `v1.0.0`:
`https://github.com/MarkEdit-app/MarkEdit-preview/releases/download/v1.0.0/markedit-preview.js`

If the user provides a URL ending with `.js`, use that URL directly.

## Common Tasks

### Upgrading MarkEdit

1. Retrieve the latest release from [GitHub releases](https://github.com/MarkEdit-app/MarkEdit/releases)
2. Prompt the user to choose: `.dmg` or `apple-silicon.dmg`
3. Download the selected installer
4. Extract the `.app` bundle from the `.dmg`
5. Move the `.app` bundle to `/Applications`
6. Launch MarkEdit

### Re-Launching MarkEdit

```sh
osascript -e 'quit app "MarkEdit"' -e 'delay 1' -e 'launch app "MarkEdit"'
```

### Installing Extensions

1. Download the extension by name or URL
2. Place it in the extensions directory
3. Re-launch MarkEdit

Use the filename derived from the URL. If a file with the same name exists, prompt the user to confirm overwriting.

### Listing Extensions

List all `.js` files in the extensions directory with their sizes and last modification dates.

### Upgrading Extensions

1. Re-download the extension from the same source (lite or full)
2. Overwrite the existing file
3. Re-launch MarkEdit

### Uninstalling Extensions

1. Add `.js` suffix to the name if needed
2. Remove the file from the extensions directory
3. Re-launch MarkEdit

### Editing Preferences

1. Use the [wiki](https://github.com/MarkEdit-app/MarkEdit/wiki/Customization#advanced-settings) as reference
2. Edit `settings.json` directly
3. Re-launch MarkEdit

### Answering Questions

When users ask questions:

1. If it's a **task** (install, configure, upgrade) → perform the action
2. If it's a **customisation** question → explain editor.css, editor.js, or settings.json
3. If it's a **feature** question → fetch from wiki and issues
4. If unknown → suggest the [wiki](https://github.com/MarkEdit-app/MarkEdit/wiki) or GitHub issues

## Examples

- "Upgrade MarkEdit"
- "Install MarkEdit Preview extension"
- "Install the lite version of MarkEdit Preview"
- "Upgrade MarkEdit Preview"
- "List installed extensions"
- "Remove MarkEdit Preview"
- "Enable autoSaveWhenIdle in MarkEdit"
- "How to customise the editor appearance?"

## Error Handling

- If extension download fails from both the dist URL and the latest release, suggest checking the extension name or URL
- If `settings.json` is malformed, suggest validating JSON syntax
- If MarkEdit is not installed, suggest installation methods

## Documentation

When answering questions, refer to the [MarkEdit Wiki](https://github.com/MarkEdit-app/MarkEdit/wiki):

| Page | URL |
|------|-----|
| Customisation | https://github.com/MarkEdit-app/MarkEdit/wiki/Customization |
| Extensions | https://github.com/MarkEdit-app/MarkEdit/wiki/Extensions |
| User Manual | https://github.com/MarkEdit-app/MarkEdit/wiki/Manual |
| Text Processing | https://github.com/MarkEdit-app/MarkEdit/wiki/Text-Processing |
| Philosophy | https://github.com/MarkEdit-app/MarkEdit/wiki/Philosophy |

Search also https://github.com/MarkEdit-app/MarkEdit/issues?q=is%3Aissue%20state%3Aclosed for answered questions or discussed topics.

When answering questions related to development, refer to the [MarkEdit API](https://github.com/MarkEdit-app/MarkEdit-api) repository too.

---

## Chezmoi

The user manages their markedit config files with chezmoi.

After making changes to settings.json or other config files, ensure you add them to chezmoi (`chezmoi add --encrypt <file>`), but do not run any git commands.

© sammcj · Apache-2.0 · sammcj/agentic-coding

Similar skills

All skills for Notes, tasks and projects →

From the same set73

The whole set →
invokeai-image-gen invokeai-image-gen — a skill for generating images via local InvokeAI API, supporting FLUX.2 Klein, Z-Image Turbo, and SDXL. Auto-detects models and applies appropriate parameters, saves output as PNG. CX Codex +1 ★ 173repo stars qa-to-issues qa-to-issues runs an interactive QA session to turn reported bugs into durable GitHub issues. The agent asks quick clarifying questions, checks your codebase, and files tickets. CX Codex +1 ★ 173repo stars systematic-debugging systematic-debugging — a structured debugging skill for stubborn bugs that survived several fixes. It traces symptoms to root causes before proposing code changes. CX Codex +1 ★ 173repo stars personal-genomics personal-genomics runs pharmacogenomics, disease-risk, carrier and trait checks on raw DNA files, entirely offline — one array export or several sources merged into a single report. CX Codex +1 ★ 173repo stars raspberry-pi-pico2 Get guidance on building and debugging Raspberry Pi Pico 2 projects with the Pi Debug Probe. Useful for RP2350, SDK configuration, OpenOCD, and GDB. CX Codex +1 ★ 173repo stars prompt-enhancer prompt-enhancer transforms vague or basic prompts into the form a domain specialist would use. Useful when you need to rephrase a request for another AI system or clarify your own. CX Codex +1 ★ 173repo stars piper-tts-training piper-tts-training guides voice model training and fine-tuning for the Piper TTS engine in ONNX format. Useful for local speech synthesis on Raspberry Pi or Home Assistant. CX Codex +1 ★ 173repo stars html-design-examples The html-design-examples skill uses a gallery of single-file HTML references to shape plans, reports, prototypes, and other materials meant to be read in a browser. CX Codex +1 ★ 173repo stars

Project sponsors

Companies that keep this analytics open