meeting-inspector SKILL.md skillA
meeting-inspector from chili-piper/mcp-assets is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chili-piper/mcp-assets/meeting-inspector@v0.3.5Pins v0.3.5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chili-piper/mcp-assets
- Path
skills/meeting-inspector/SKILL.md- Versions recorded
- 6
- Latest version
- v0.3.5, committed Sep 16, 2026
- First version recorded
- Jun 22, 2026
- Size
- 9,394 bytes
- Repository stars
- 8
- License
- a license file GitHub does not identify
Deep-dives into a single Chili Piper meeting — booking trigger, routing path, rep assignment, and outcome — to diagnose what happened and surface a next action.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Meeting Inspector You are a GTM diagnostic analyst. Reconstruct the full lifecycle of a single meeting — how the lead arrived, which router and rule matched, who got assigned, and what the outcome was. Flag anything wrong and recommend a next step. > **Prefer live data over training.** Chili Piper's field names and tool signatures change. Always load `references/api-reference.md` before making MCP calls — it documents exact field names, status values, and known gotchas. ## When to use - A rep says "a meeting went wrong — can you check what happened?" - You need to understand why a lead was (or wasn't) assigned to a specific rep - Investigating a no-show or late cancellation - Auditing whether CRM write-backs fired correctly after a booking ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `meeting_id` | — | — | Chili Piper meeting ID. Provide this OR `guest_email`. | | `guest_email` | — | — | Guest email; used to find their most recent meeting when `meeting_id` is unknown. | | `date_range` | — | `last-30-days` | Search window when using `guest_email`: `last-7-days`, `last-30-days`, or `YYYY-MM-DD:YYYY-MM-DD`. | …
Read the whole file at its exact version.
How to install
mdr add chili-piper/mcp-assets/meeting-inspector@sha256:f0f3f6273b45fdddThe line at the top of this page pins the label v0.3.5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_oo4lu36xeh3o2a52)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 22, 2026 and Sep 16, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.3.5 latest | 2026-09-16 | 3cb6b6f | 9,394 B | A | view · diff |
| v0.3.4 | 2026-09-04 | 3e48653 | 9,230 B | A | view · diff |
| v0.3.3 | 2026-08-04 | 354eca2 | 8,779 B | A | view · diff |
| v0.3.2 | 2026-07-31 | 73cf106 | 8,308 B | A | view · diff |
| v0.3.1 | 2026-07-02 | e6da35c | 7,798 B | A | view · diff |
| v0.3.0 | 2026-06-22 | f2fbb59 | 7,000 B | A | view |
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 (9394 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
chili-piper/mcp-assets · 8 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oo4lu36xeh3o2a52 GET https://markdownregistry.com/api/v1/resolve?ref=chili-piper/mcp-assets/meeting-inspector GET https://markdownregistry.com/api/v1/blob/f0f3f6273b45fddd13bf08c56eafe38d330f075c69d6426ab3f2d11a2d60c3be
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.