Menu
Comment annotation syntax for Moss notes. Use when adding, preserving, or editing note comments and their sidecar metadata.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create or edit Moss canvas blocks and choose between moss-canvas and plain ASCII sketches for proposal notes, UI option cards, ASCII wireframes, rough diagrams, flows, and spatial visual thinking.
Create or edit Moss formulas and variables, including editable anchors, derived values, bound references, display values, IDs, metadata, and table-cell usage.
YAML frontmatter rules for Moss note metadata. Use when adding or editing the optional metadata block at the top of a note.
Author self-contained moss-html blocks for HTML previews, embedded HTML, interactive prototypes, and behavior demos in Moss notes.
Create or edit Moss links, including wiki note links, heading links, aliases, Markdown links, YouTube embeds, and media/link preservation rules.
Syntax and file rules for creating or editing Moss notes under ~/Moss/Notes/. Use when authoring or modifying notes, choosing a node type, or following Moss markdown conventions.
| name | moss-comments |
| description | Comment annotation syntax for Moss notes. Use when adding, preserving, or editing note comments and their sidecar metadata. |
Root comments need both body markers and a matching comments.json entry. Reply IDs carry a parentId, live only in comments.json, and must be reachable from a root comment.
Wrap the exact annotated range:
The %%m:c1:start%%current layout%%m:c1:end%% needs work.
%%m:a,b:start%%text%%m:a,b:end%%.Workspace note comments use comments.json beside the markdown file in its note directory. For a standalone external markdown file, use only the sidecar path Moss provides.
This example is for a writer editing files outside Moss. The in-app Moss agent must use "source":"agent" instead.
{"c1":{"text":"Tighten this wording.","createdAt":1707900000,"updatedAt":1707900000,"source":"external"}}
parentId live only in sidecar metadata and must be reachable from a root comment.source to your execution context: "agent" for the in-app Moss agent, "external" for writers editing files outside Moss, and "user" only for human/UI-authored comments.source or resolvedBy metadata. Preserve existing attribution fields unless the user explicitly asks to change them.source. Treat missing source as legacy/unknown; do not backfill it or infer it from context.resolvedAt (Unix timestamp in seconds), set resolvedBy to your execution context when known, and update updatedAt on the root comment and every descendant reply.Thread replies live in comments.json; body markers only anchor root comments.
This example continues the external-writer context above.
{
"c1": {"text":"Original.","createdAt":1707900000,"updatedAt":1707900000,"source":"user"},
"c1-r1": {"text":"Following up.","createdAt":1707900100,"updatedAt":1707900100,"source":"external","parentId":"c1"}
}
comments.json sidecar metadata.parentId is optional and may point at a root comment or another reply.source, when present, is independent of its parent's source.parentId at a missing id.%%m:x:start%%[[Project Plan]]%%m:x:end%%.%%m:b1:start%%
%%m:b1:end%%
Do not place markers inside wiki links, formula/variable pills, color code pills, fenced block payloads, or raw HTML comments. Treat atomic inline pills as indivisible; wrap the whole node or surrounding phrase instead. For color literals such as #4f8a6b, rebeccapurple, or rgb(72, 67, 60), prefer annotating the surrounding sentence or phrase rather than trying to split the literal itself.
resolvedAt, resolvedBy, and updatedAt on the root comment and every descendant reply.comments.json and are hidden by default in the UI.When the in-app Moss agent receives comment context from the prompt box, the prompt carries compact comment IDs instead of full quoted comment text.
source to "agent"; external writers editing files outside Moss should set "external".resolvedAt, resolvedBy, and updatedAt.comments.json or leave it open; do not set resolved fields.Comments may include image attachments stored under the note's assets/ directory:
This example also uses external-writer attribution; the in-app Moss agent must use "source":"agent".
{"c1":{"text":"See screenshot.","createdAt":1707900000,"updatedAt":1707900000,"source":"external","imageUrls":["assets/comment-abc.png"]}}
imageUrls array with note-relative paths under assets/.assets/.Mentions in comment text are references to notes, files, or folders. Each displayed mention is wrapped with U+2063 (INVISIBLE SEPARATOR) before and U+2064 (INVISIBLE PLUS) after, e.g. Re: @Project Plan scope.
~/Moss/Notes/.