القائمة
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.
التثبيت باستخدام 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.
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.
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.
| name | job-apply |
| description | 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. |
Purpose: Streamline job application process by analyzing role fit, drafting responses to application questions, identifying hiring managers, and creating follow-up outreach emails.
Craft and RYLLCStrong Fit:
Medium Fit:
Weak Fit:
Evaluate each role on these dimensions:
Common questions and approach:
Structure:
Tone: Genuine, specific, technical. Avoid generic statements.
Example for climate tech:
"I'm deeply committed to working on climate solutions, and [Company]'s approach to [specific problem] resonates with me. At QuitCarbon, I saw firsthand how technical execution can accelerate decarbonization. I'm particularly excited about [specific technical challenge from job posting] because at Gremlin, we wrestled with similar distributed systems challenges around [relevant experience]. I believe my experience scaling [relevant system] could help [Company] achieve [specific goal from their mission]."
Structure:
Tone: Concrete, technical, impact-focused. No bragging about metrics unless specifically asked.
Example:
"At Gremlin, we faced a critical challenge: how do you quantify the value of failures that didn't happen? I led the architecture of our reliability scoring system, designing a distributed event processing pipeline that correlated chaos experiments with production incidents. This required building consensus across engineering and product on what 'resilience' meant quantitatively. The system became core to our product value proposition and enabled customers to demonstrate ROI to their executives. I'm proud of both the technical architecture and the cross-functional collaboration required to ship it."
Approach:
Example response:
"I'm targeting $[X]-$[Y] base salary, which I believe aligns with market rates for Staff+ engineers in climate tech. I'm flexible on the exact number depending on equity, benefits, and the overall compensation package. Most important to me is working on meaningful climate solutions with a strong technical team."
Purpose: Every job application should include a tailored cover letter that demonstrates genuine interest and technical fit.
Length: 250-350 words (3-4 paragraphs)
Tone: Professional but conversational, specific to the role and company, shows research and genuine interest
Paragraph 1: Opening and Mission Alignment (2-3 sentences)
Paragraph 2: Technical Fit and Relevant Experience (3-4 sentences)
Paragraph 3: Why This Role/Why Now (2-3 sentences)
Paragraph 4: Closing (1-2 sentences)
I'm writing to express my strong interest in the [Job Title] position at [Company]. [Specific aspect of their mission/technology] resonates deeply with my commitment to [relevant value/goal], and I'm excited about the opportunity to contribute to [specific company goal or technical challenge].
I spent six years as CTO and co-founder of Gremlin, where I [relevant technical achievement tied to their needs]. Before that, I [relevant prior experience]. At QuitCarbon, I served as Head of Engineering and saw firsthand how [relevant insight about climate tech/their domain]. I'm particularly drawn to [specific technical challenge from posting] because [connection to your experience], and I believe my background in [relevant expertise] would enable me to [specific contribution to their goals].
I'm looking for Staff+ IC engineering work where I can focus on deep technical challenges in [relevant domain] while contributing to climate solutions. [Company's] approach to [specific aspect of their work] represents exactly the kind of meaningful technical problem I want to spend my time on. The opportunity to [specific aspect from job posting] while [another specific aspect] aligns perfectly with how I work best.
I'd welcome the opportunity to discuss how my experience in [relevant areas] could help [Company] [specific goal]. Thank you for considering my application.
Best regards,
Matthew Fornaciari
Priority 1: LinkedIn Search
[Company Name] (Director of Engineering OR VP Engineering OR Head of Engineering OR CTO OR Engineering Manager)
Filter by:
Startup (< 50 people):
Scale-up (50-200 people):
Growth Stage (200-500 people):
Large Company (500+ people):
Use template: ~/Craft/vocation/templates/07-job-posting-cold-outreach.md
Subject: [Role Title] at [Company]
Hi [First Name],
[Opening: Found posting + forward request]
[Brief credentials: Gremlin CTO + relevant experience]
[Specific interest: What excites you about their tech/mission]
[Fractional pitch: Position as alternative or complement]
[Close: Scheduling link]
Matthew Fornaciari
After generating email:
draft_email toolCraft and RYLLCWhen skill is invoked with job posting URL:
Craft and RYLLC labels# Job Application Analysis: [Company] - [Role]
## Fit Assessment
- **Mission Alignment:** [score]/10 - [brief explanation]
- **Technical Fit:** [score]/10 - [brief explanation]
- **Role Level:** [score]/10 - [brief explanation]
- **Work Style:** [score]/10 - [brief explanation]
- **Overall:** [average score]/10 - [Strong/Medium/Weak Fit]
**Recommendation:** [Apply / Reconsider / Skip]
---
## Cover Letter
[Full cover letter text, 250-350 words]
---
## Application Question Responses
### [Question 1]
[Response]
### [Question 2]
[Response]
[etc.]
---
## Hiring Manager Research
**Identified:** [Name], [Title]
**LinkedIn:** [URL if found]
**Email:** [If found, otherwise "Not found - will send to general hiring contact"]
---
## Follow-Up Email
**Status:** [Draft created in Gmail / Ready to send]
**Labels:** Craft, RYLLC
**Subject:** [Subject line]
[Email preview]
---
## Next Steps
1. [Copy cover letter to job application]
2. [Copy application question responses to job portal]
3. [Review and send Gmail draft to hiring manager]
4. [Track in vocation repo: companies/[company-name].md]
Email template:
~/Craft/vocation/templates/07-job-posting-cold-outreach.mdProject guidelines:
~/Craft/vocation/CLAUDE.mdContact tracking:
~/Craft/vocation/network/contacts.mdCompany profiles:
~/Craft/vocation/companies/