Individual skill
moss-writing-guidelines
Writing and scannability guidelines for Moss notes. Use when creating, editing, restructuring, or reviewing a note for reader-first structure, node choice, scannability, note quality, or writing guidelines.
plugins/moss-skills/skills/moss-writing-guidelines/SKILL.md
Source commit 071be4f2e0f8473657fdc867a64342608b58a387
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12
- Repository last updated
- Aug 25, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- codex Repository topic
- codex-plugin Repository topic
- markdown Repository topic
- mockups Repository topic
- note-taking Repository topic
- mossnotes Repository topic
- writing Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Moss Writing Guidelines
Write every Moss note for a reader who skims first and reads second. This skill owns note structure and composition; `moss-notes` owns file layout, node selection, and persisted syntax.
## Summary First
Frontmatter and the single H1 title come first when present. The first body paragraph after the H1 should state the answer, decision, status, or takeaway without requiring background from later sections.
- Open with the answer, decision, or takeaway — not background or process.
- State conclusions before evidence; put caveats and supporting detail after.
## Progressive Disclosure
- Order sections most- to least-important. Front-load what most readers need.