draft-offer
Draft an offer letter with comp details and terms. Use when a candidate is ready for an offer, assembling a total comp package (base, equity, signing bonus), writing the offer letter text itself, or prepping negotiation guidance for the hiring manager.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- draft-offer
- description
- Draft an offer letter with comp details and terms. Use when a candidate is ready for an offer, assembling a total comp package (base, equity, signing bonus), writing the offer letter text itself, or prepping negotiation guidance for the hiring manager.
- argument-hint
- <role and level>
02 资源文件 1
- 参考文档CONNECTORS.md1.0 KB
03 SKILL.md 正文
<!-- Provenance: adapted from anthropics/knowledge-work-plugins (Apache-2.0, (c) Anthropic). Original skill: https://github.com/anthropics/knowledge-work-plugins/tree/main/human-resources/skills/draft-offer. Changes for Muse AI: Claude/Cowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; /plugin:command refs -> skill refs. -->
/draft-offer
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Draft a complete offer letter for a new hire.
Usage
/draft-offer $ARGUMENTS
What I Need From You
- Role and title: What position?
- Level: Junior, Mid, Senior, Staff, etc.
- Location: Where will they be based? (affects comp and benefits)
- Compensation: Base salary, equity, signing bonus (if applicable)
- Start date: When should they start?
- Hiring manager: Who will they report to?
If you don't have all details, I'll help you think through them.
Output
## Offer Letter Draft: [Role] — [Level]
### Compensation Package
| Component | Details |
|-----------|---------|
| **Base Salary** | $[X]/year |
| **Equity** | [X shares/units], [vesting schedule] |
| **Signing Bonus** | $[X] (if applicable) |
| **Target Bonus** | [X]% of base (if applicable) |
| **Total First-Year Comp** | $[X] |
### Terms
- **Start Date**: [Date]
- **Reports To**: [Manager]
- **Location**: [Office / Remote / Hybrid]
- **Employment Type**: [Full-time, Exempt]
### Benefits Summary
[Key benefits highlights relevant to the candidate]
### Offer Letter Text
Dear [Candidate Name],
We are pleased to offer you the position of [Title] at [Company]...
[Complete offer letter text]
### Notes for Hiring Manager
- [Negotiation guidance if needed]
- [Comp band context]
- [Any flags or considerations]
If Connectors Available
If ~~HRIS is connected:
- Pull comp band data for the level/role
- Verify headcount approval
- Auto-populate benefits details
If ~~ATS is connected:
- Pull candidate details from the application
- Update offer status in the pipeline
Tips
- Include total comp — Candidates compare total compensation, not just base.
- Be specific about equity — Share count, current valuation method, vesting schedule.
- Personalize — Reference something from the interview process to make it warm.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).