Never ghost a candidate again
Generates stage-appropriate candidate updates — including delays — that are human, respectful, and specific about next steps. Protects candidate experience and employer brand.
Create a skill called "Candidate Status Update Generator". Inputs: - Stage (applied / screening / interview / final / offer / rejected) - What happened and what's next - Timeline (exact if possible; otherwise a range) - Tone (warm, neutral, formal) - Any constraints (cannot share feedback, headcount pause, etc.) Output: 1) Message to candidate (80–160 words) 2) Subject line (if email) 3) A short internal note version (for ATS) Must include: clarity, respect, and a clear next step.
Tell the skill what stage the candidate is in, what happened, and what's next.
It writes a message with clarity, respect, and a clear next step.
Kind, compliant rejections that preserve goodwill
Produces rejection messages that are dignified and clear, with optional constructive feedback that avoids legal risk and protects the organization.
Replace meeting sprawl with agendas, pre-reads, slim cadences, and async artifacts
Meeting overload and multi-channel communication sprawl are a major PM drag. This recipe designs a minimal meeting system: which meetings exist, why, with what agenda, what pre-work, and what async artifacts replace the rest.
Stop being the family project manager
Build a weekly schedule, decision rules, and scripts that prevent one parent from becoming the household operations manager. Coverage grid, handoff protocol, and conflict-prevention rules included.
Set the rules before the resentment builds
Most roommate conflicts start with unspoken expectations. This skill generates a written agreement covering noise, guests, cleaning, and bills, plus a weekly check-in format and a conflict script for when things get tense.