Speaking ops: invites, keynotes, panels, Gmail/calendar, conferences.
56
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/speaking/SKILL.mdUse this for Peter's speaking-opportunity workflow.
/Users/steipete/Projects/conferencesPeter Steinberger InboundsInvitations/Users/steipete/Projects/conferences/conference-opportunities.md/Users/steipete/Projects/conferences/opportunities/NNN-slug.mdUse gog first for Google data when available:
gog gmail search 'speaker OR keynote OR panel OR fireside OR conference OR summit after:2026-01-01' --json --no-input
gog gmail read <thread-or-message-id> --json --no-input
gog calendar events primary --time-min 2026-01-01T00:00:00Z --time-max 2026-12-31T23:59:59Z --json --no-input
gog sheets get 1dNt5EjgfgvPoAx5fa-igk681gniCkzL-IZ2FmjFl8fs 'Invitations!A1:Q110' --json --no-inputTrack:
Do not track in the conference list:
Talks and firesides are welcome. Do not delete them just because they are not classic conferences.
Score with these heuristics:
Priority language:
accept: committed or clearly worth doing.strong consider: high value but needs missing logistics/details.review: plausible, needs more info.pass: declined, stale, low leverage, bad fit, or user explicitly said no.Before changing status:
Useful status meanings:
CALENDARED: calendar plus email evidence, or accepted invite.INBOX: needs response or still open.INBOX / CALENDAR HOLD: calendar hold exists, but details still need confirmation.PASS: do not pursue.Done: declined, stale, or already passed.Per-opportunity files should stay short and structured:
# Event Name
- Number: N
- Index: [Conference Opportunities Brief](../conference-opportunities.md)
## Brief
- Date/location:
- Host/ask:
- Format:
- Audience/scale:
- Impact:
- Fit:
- Risks:
- Status:
- Recommendation:
- Sources:When adding an opportunity:
opportunities/*.md.opportunities/NNN-slug.md.conference-opportunities.md.Use the sheet headers from Invitations!A1:Q1:
Invitation Name, Primary Category, Recommendation, Date, Location, Subcategory, Geography, Recommended Rep, Response Status, Status, Outlet / Event, Contact Name, Contact Email, Topic / Subject, Notes, Source File, From Raw
Sync rules:
Primary Category can remain Conference as the broad bucket, while Subcategory explains keynote/panel/fireside/talk/retreat.Invitations.Use gog sheets update ... --values-json for bulk updates. Avoid one-cell micro-edits.
bb36883
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.