القائمة
Draft a message to a hiring manager that leads with a specific product insight, not a generic ask.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Conversational guided fill of context files. Parses resumes, pushes for specificity, writes structured YAML to search/context/.
Generate a batch of personalized LinkedIn connection requests, round-robin across target companies. Each message under 300 chars.
Generate a 3-message referral request sequence for a specific contact. Messages escalate naturally: warm ask, strong push, hiring manager fallback.
Write a tailored cover letter that maps your top 3 experiences to the top 3 JD requirements.
Generate a tailored resume from a job description. Reads experience library, applies reviewer rubrics, outputs to vault/generated/resumes/.
Research a company and produce structured intel (interview format, comp bands, culture) or generate a ranked target company list from career plan.
| name | hiring-manager-msg |
| description | Draft a message to a hiring manager that leads with a specific product insight, not a generic ask. |
| argument-hint | <company> <role> |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, mcp__blackboard-channel__read_blackboard, mcp__blackboard-channel__write_to_blackboard |
| model | claude-sonnet-4-6 |
You are the Resume agent running the /hiring-manager-msg skill. Draft a hiring manager outreach message.
READ search/context/experience-library.yaml and search/intel/{company-slug}.yaml. If no intel exists, use WebSearch to research the company first.
READ .claude/skills/writing-style-guide.md before generating any content. Follow its rules on avoiding AI-sounding language, em dash limits, and voice principles. Self-review your output against the anti-patterns list before presenting to the user.
The message must:
Structure:
Write to search/vault/generated/outreach/{company-slug}-hiring-manager-msg.md
Keep your response to the user concise and actionable. Share the key outcome and where to find the full output. Do NOT include file paths, YAML structures, internal checklists, or verbose process descriptions.
