meeting-prep skillA
meeting-prep is agent-read markdown (skill) from nano-muse/nanomuse: Prepare for a meeting — who is in it, what was last said with them, what the user owes them and wants from them — as a one-page brief. Use when the user asks to prepare for or get ready for a meeting, a call or a visit; a trigger can run it before every meeting with a client..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Meeting prep A brief at `meetings/YYYY-MM-DD-<slug>.md` in the workspace, and its gist in chat. Works with any of the connectors; the more are there, the fuller the brief. ## Find the meeting - If the user named it, `calendar` action=search for it; otherwise `calendar` action=agenda for today and tomorrow and take the next one that has other people in it. If nothing fits, ask with one `ask_user`: which meeting, and with whom. - A trigger (kind=event) gives you the event as context: use it as is, do not search again. ## The people - Each attendee: `contacts` action=search by name or address — company, role, how the user knows them. Unknown people stay a bare name; do not look them up on the web unless the user asks. - With the mail connector: `read_emails` `search=<their name or address>`, the last few weeks. You want the last thing said in each direction, open questions, and anything the user promised. - `recall` each name and the company: past notes, preferences, what went wrong last time. ## The matter - Related files in the workspace: `files` action=search for the company, the project or the meeting's title; list the two or three that matter with a one-line note. …
Read the whole file at its exact version.
How to install
mdr add nano-muse/nanomuse/meeting-prep@v1mdr add nano-muse/nanomuse/meeting-prep@sha256:97d3179b4c459bf0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7kexk7zn7odx6set)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2652 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nano-muse/nanomuse · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7kexk7zn7odx6set GET https://markdownregistry.com/api/v1/resolve?ref=nano-muse/nanomuse/meeting-prep GET https://markdownregistry.com/api/v1/blob/97d3179b4c459bf087eeb0cd0b5517bb254ba8a8a62edf06e6f6000ad1ec93fb
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nano-muse/nanomuse
Every file in nano-muse/nanomuse