Menú
Provides tools for managing MarkEdit, a macOS markdown editor
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Foundational skill-authoring knowledge to use alongside the skill-creator skill. You MUST always load this skill before loading the skill-creator skill, when creating or updating skills.
Disciplined, measurable iteration for a substantial refinement or investigation: loop against verifiable pass/fail conditions, fan work out to subagents, and keep the main context lean. Use when improving something measurable over repeated cycles (tuning a metric or detector, refactoring against a regression bar), chasing a surprising or suspicious number, or driving a long multi-step task where delegation and context discipline matter. Not for one-shot edits or quick lookups that don't warrant a loop.
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) as plain markdown, optionally opened as an Obsidian vault. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing the reasoning in a source or article, superseding stale knowledge, 'add to wiki', or any mention of 'LLM wiki' or 'Karpathy wiki'.
Use this skill after completing multiple, complex software development tasks before informing the user that work is complete.
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about, or when you need to lookup documentation or usage reference a specific library, framework, SDK, CLI tool, or cloud service - even if well-known as your training data may be outdated. Prefer this over web search for library documentation and API details.
Provides fast document to markdown extraction. Use this skill when the user asks to parse, perform multi-format document conversion or spatially extract text from an unstructured file (PDF, DOCX, PPTX, XLSX, images, etc.) locally.
| name | markedit-tools |
| description | Provides tools for managing MarkEdit, a macOS markdown editor |
Help users configure and extend MarkEdit, a free and open-source markdown editor for macOS.
| 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 |
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 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:
https://api.github.com/repos/MarkEdit-app/extension-name/releases/latesttag_name field from the response.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.
.dmg or apple-silicon.dmg.app bundle from the .dmg.app bundle to /Applicationsosascript -e 'quit app "MarkEdit"' -e 'delay 1' -e 'launch app "MarkEdit"'
Use the filename derived from the URL. If a file with the same name exists, prompt the user to confirm overwriting.
List all .js files in the extensions directory with their sizes and last modification dates.
.js suffix to the name if neededsettings.json directlyWhen users ask questions:
settings.json is malformed, suggest validating JSON syntaxWhen answering questions, refer to the MarkEdit Wiki:
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 repository too.
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.