events-and-field-marketing skillA
events-and-field-marketing is agent-read markdown (skill) from cbrock84/headcount: Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline..
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
# Events and field marketing Events are the most expensive marketing channel per contact and the easiest to spend badly on, because the outputs — booth traffic, badge scans, attendance — feel like results and are not. ## Decide before you sponsor The question is never "should we be at this event" but "what specifically do we expect, and what is that worth." Answer three things first: - **Who is actually there.** Attendee seniority and function, not the headline number. A ten-thousand-person event where forty of your buyers attend is a forty-person event. - **What the goal is**, and pick one: pipeline from new accounts, advancing deals already open, customer retention and advocacy, or category presence. These need different booths, different staff, and different follow-up, and an event asked to do all four does none. - **Total cost.** Sponsorship is often under half. Add booth build, shipping, travel, staff time out of the field, and the content produced for it. The fully loaded figure changes decisions. Small, self-hosted, targeted formats — a dinner for fifteen right accounts, a focused workshop — …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/events-and-field-marketing@git:20260916.e72e404mdr add cbrock84/headcount/events-and-field-marketing@sha256:b6a1bfffa57df754Pin 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_xitrn7pauur2wihp)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 4,307 B | A | view · diff |
| git:20260901.49e89d6 | 2026-09-01 | 49e89d6 | 3,968 B | A | view · diff |
| git:20260829.4a2c133 | 2026-08-29 | 4a2c133 | 3,370 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 (4307 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xitrn7pauur2wihp GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/events-and-field-marketing GET https://markdownregistry.com/api/v1/blob/b6a1bfffa57df75450cff19069604a1689573155604685e8872c3f07dc5de930
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.