Individual skill

conference-meeting-cards

Use this skill before a conference, roadshow, or any day of back-to-back in-person meetings when the person walking the floor needs one phone-ready screen per meeting, not a chat brief. For each meeting it enriches the attendees (photo, title, LinkedIn), pulls the live deal amount, stage, and next step from your CRM, and writes at most six short deal-context bullets in a fixed order: what they do, amount, stage plus next step, use cases, the people who matter, relationship context, and an optional key risk. It renders one self-contained HTML file per day, printable to PDF with one meeting per page, and DMs a share link to the teammates who are at the event.

skills/jeremy-hurst/conference-meeting-cards/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

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

# Conference meeting cards

## Template placeholders

Replace every `{{...}}` before enabling. See the setup checklist reference for the full setup list.

- `{{CARD_OWNER}}` - The person the cards are written for (usually the seller walking the floor)
- `{{CRM}}` - Your CRM (e.g. HubSpot, Attio, Salesforce) and the field names for deal amount, stage, next step, and close date
- `{{STAGE_LABELS}}` - Your CRM stage identifiers mapped to the human labels that should print on a card
- `{{MEETING_NOTES_TOOL}}` - Your meeting-notes or call-recording tool (e.g. Circleback, Gong, Fireflies), used as the next-step fallback
- `{{NEXT_STEP_LOOKBACK_DAYS}}` - How far back to search meeting notes for a next step when the CRM field is empty (default: 60)
- `{{FULL_BRIEF_SKILL}}` - Your full pre-call meeting-prep skill. This skill is the walking-floor card, not that brief.
- `{{DESIGN_TOKENS}}` - Your brand colors and type, if you have a design reference the template should follow
- `{{OUTPUT_FOLDER}}` - Where day files are saved (default: `events/{event-slug}/meeting-cards/{YYYY-MM-DD}.html`)
Back to top