Moss links

Skill brsbl/moss-skills/plugins/moss-skills/skills/moss-links

Skills for working with https://www.mossnotes.app/

Install

npx -y skills add brsbl/moss-skills --skill moss-links

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create or edit Moss links, including wiki note links, heading links, aliases, Markdown links, YouTube embeds, and media/link preservation rules.

SKILL.md

3.6 KB, as published. Nobody here has run it

Moss Links

Use this skill when adding, editing, or reviewing links in Moss notes: note links, heading links, display aliases, Markdown links, YouTube links, and media references.

Wiki Note Links

Wiki links connect notes and headings inside the Moss workspace.

[[Project Plan]]
[[#Local Heading]]
[[Project Plan#Scope]]
[[Project Plan|display text]]

Rules:

Use the exact note title for cross-note links.
Verify the target note exists before adding a cross-note link.
Use [[#Heading]] for a heading in the current note.
Use [[Note#Heading]] for a heading in another note.
Use [[Note|display text]] when the visible label should differ from the note title.
Do not escape brackets inside [[...]]; brackets in note titles are allowed, so write the exact title.

Markdown Links

Use standard Markdown links for web URLs, external references, and non-Moss destinations.

[Website](https://www.mossnotes.app/)
[Repository](https://github.com/brsbl/moss-skills)

Preserve existing URLs exactly unless the user asks to change them.
Prefer descriptive link text over raw URLs in prose.
Use wiki links for Moss note-to-note navigation; use Markdown links for external destinations.

YouTube Links and Video

Moss treats YouTube URLs as video-capable references when written as image/video markdown.

![Demo walkthrough](https://youtu.be/dQw4w9WgXcQ)

Use image/video markdown when the user wants an embedded playable video preview.
A bare standalone YouTube URL on its own line also becomes an embedded video.
Use a named Markdown link like [demo](https://youtu.be/...) when the user only wants a text link to YouTube.
Remote non-YouTube video files are not video nodes; use local video assets for .mp4, .webm, or .mov.

URL Previews and In-App Browser

Use a bare browser-safe URL for an inline preview, ![Title](url) for a visual webpage preview, and [Title](url) for a text link. Images, video, YouTube, and tweets remain media previews.

https://example.com/research
Research link: https://example.com/research
![Research board](https://example.com/research)
http://localhost:3000/prototype
[https://example.com/research](https://example.com/research)
[Research](https://example.com/research)

Standalone image, YouTube, and tweet URLs render as media. Inline and visual webpage previews save as bare URLs and ![Title](url) respectively.
Public pages must use HTTPS. Loopback development URLs such as localhost, *.localhost, 127.0.0.1, and ::1 may use HTTP or HTTPS because they open in the browser surface.
Private network, link-local, .local, credentialed, and obvious downloadable-file URLs stay plain text or open externally instead of becoming browser previews.

Local Assets and Media Links

Use note-local assets for files stored with the note.

![Screenshot](assets/screenshot.png)
![Demo recording](assets/demo.mp4)

Prefer assets/... paths for note-local media.
Do not use file:// or absolute local paths in notes.
Preserve existing asset paths unless relocating the asset is part of the task.

Review Checklist

Link type matches destination: wiki for Moss notes, Markdown for external URLs, image/video markdown for media.
Cross-note wiki targets use exact note titles.
YouTube embeds use image/video markdown only when an embedded video is intended.
No accidental changes to existing URLs, aliases, heading fragments, or asset paths.