菜单
Craft Business Development emails for RYLLC fractional CTO consultancy. Handles warm reconnects, job posting outreach, rejection follow-ups, VC intros, and custom BD scenarios. Uses established templates and project voice.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Training plan scheduling, weekly retrospectives, and training adjacent constraint validation. Use this skill whenever the user mentions training, lifts, runs, climbs, the Friday long run, sauna timing, cold plunge timing, recovery days, cutback weeks, altitude weeks, race week, training restructure, Fitbod, asking to schedule a training session, or asking to look back / retrospect on a past training week. Also trigger for "/assist:plan-training", "schedule my long run", "what does training look like this week", "how did last week go", "training retro", or any request that touches the training plan in `Constitution/Fitness/`. Independently usable, and also called by `/assist:plan-week` during Monday planning.
Weekly planning, calendar management, and Monday morning task slotting. Use this skill whenever the user mentions weekly planning, the Monday planning session, slotting tasks, finding free time, checking what their week looks like, moving or swapping calendar events, or wants help fitting something into their week. Also trigger when the user asks about V2MOM measure coverage. Training plan scheduling lives in `assist:plan-training` and meal planning in `assist:plan-meals`; this skill calls into both during Monday planning.
Audit and redesign the context architecture (every CLAUDE.md, learned-rules.md, and tool doc that loads into Claude Code sessions) so load-bearing rules are surfaced and enforced at the point of use rather than scattered, duplicated, or buried. Use this skill whenever Forni says "groom context", "groom-context", "we forgot a basic again", "the context is sprawling", "the rules keep getting lost", "clean up the context", or invokes "/assist:groom-context". Also invoked as a closing step by the monthly path of assist:reflect. This is the cleanup counterpart to assist:codify-context, which writes knowledge into the same architecture.
Codify knowledge from the current session into the appropriate location in the context architecture using progressive disclosure. Use this skill whenever the user says "codify" followed by a topic, wants to capture something they just figured out, asks to document a pattern or convention, or says something like "we should write this down" or "future me needs to know this." Also trigger when the user discovers a gotcha, foot-gun, or non-obvious behavior worth preserving. Works for both project directories (three-layer CLAUDE.md/README.md pattern) and skill directories (Learned Rules in SKILL.md). Named after the "plan, delegate, assess, codify" Level 4 compounding loop. This is the write-in counterpart to `assist:groom-context`, which audits and prunes the same context architecture.
Triage Gmail inbox by labeling, starring, and archiving emails. Also creates filters for recurring senders. Use this skill whenever the user mentions email triage, inbox cleanup, email labels, email filters, or wants to process their inbox. Default mode is triage.
Analyze job roles for fit, draft application question responses, find hiring managers, and create follow-up emails for RYLLC job applications. Focuses on climate tech IC product/SRE roles.
| name | assist:bd-email |
| description | Craft Business Development emails for RYLLC fractional CTO consultancy. Handles warm reconnects, job posting outreach, rejection follow-ups, VC intros, and custom BD scenarios. Uses established templates and project voice. |
Purpose: Draft professional, conversational Business Development emails for RYLLC fractional CTO consultancy outreach.
Use for: Former colleagues, VCs, advisors, warm contacts Template: templates/06-colleague-reconnect.md Key elements:
Use for: Found strong technical fit role, want to pitch fractional alternative Template: templates/07-job-posting-cold-outreach.md Key elements:
Use for: Received job rejection, want to turn into network connection Template: templates/05-rejection-follow-up.md Key elements:
Use for: Asking warm contact to intro you to specific company Key elements:
Use for: Unique situations not covered by templates Approach: Follow core principles, adapt tone to relationship warmth
Standard explanation (adjust as needed):
"I'm focused on fractional CTO work and reliability staff augmentation. On the CTO side, I'm doing the deep technical work like architecture and system design on one end, and high-level strategy like roadmap and team building on the other."
Note: Keep framing positive. Avoid negative language like "skipping all the middle management nonsense" or similar. Focus on what you DO provide, not what you avoid.
Standard positioning:
"I spent six years as CTO and co-founder of Gremlin, pioneering chaos engineering."
For energy/climate context:
"At Gremlin, we constantly wrestled with quantifying the impact of failures that didn't happen—exactly the kind of reliability challenge that's critical in [energy systems/climate infrastructure]."
Scheduling link: https://app.reclaim.ai/m/forni/chat
Signature:
Matthew Fornaciari
Warm closing (for reconnect emails): "Either way, cheers and hope things are going well."
Forward request (for cold outreach): "If I'm reaching out to the wrong person, I'd appreciate you forwarding this along to whoever's leading this hire."
gws CLI (gws gmail, per the gws-gmail skills) to search and read past email threads with the contactWarm reconnect to former colleague:
Cold outreach to job posting:
Introduction request to warm contact:
All templates available in:
~/Eudaimonia/Craft/Vocation/templates/Contact database:
Project guidelines:
~/Eudaimonia/Craft/Vocation/CLAUDE.mdDraft directly in Gmail via the gws CLI (see the gws-gmail skills): gws gmail +send --to <EMAIL> --subject '...' --html --body '<p>...</p>' --draft. Omit --draft only after explicit approval to send.