npx skills add https://github.com/rysweet/amplihack --skill email-drafter根据要点或对话摘要生成专业、结构良好的电子邮件,保持一致的语调和格式。
向 Claude 提供:
Claude 会将输入内容转化为一封精炼、专业的电子邮件,包含:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
目的:告知收件人当前进展、已完成的工作和后续步骤
结构:
最适合:每周更新、冲刺评审、项目进度报告
目的:向收件人请求行动、批准、资源或意见
结构:
最适合:预算请求、请假、资源、批准、反馈
目的:向团队或利益相关者群体传达新闻、变更或信息
结构:
最适合:产品发布、政策变更、团队更新、组织变更
目的:延续对话、提醒承诺事项或推动事项进展
结构:
最适合:会议后、确认决策、确保进展
目的:回复询问、提议或问题
结构:
最适合:回复询问、解答问题、回应提案
目的:为记录目的总结会议、对话或决策
结构:
最适合:会议摘要、决策记录、行动项跟踪
输入:
输出:
Dear Team,
I am writing to provide a status update on the authentication module project for the week of November 4-8.
Completed Items:
The authentication module implementation has been completed and is ready for integration testing. Unit test coverage has reached 94%, demonstrating comprehensive code validation. Performance benchmarks indicate a 15% improvement over the previous implementation.
In Progress:
Database migration testing is currently underway to ensure data integrity during the transition. We anticipate completion by end of day Friday.
Upcoming:
The team will gather on Thursday to discuss and potentially approve the proposed API schema changes. Your input on this matter would be greatly appreciated.
Please let me know if you have any questions or concerns regarding this update.
Best regards,
[Your Name]
输入:
输出:
Hi [Manager Name],
I wanted to reach out about an opportunity I'd like to pursue. I've been selected to give a talk on distributed systems architecture at the upcoming tech conference on March 15-17. It's a great chance to represent the company and share what we've learned.
Here's what I'd need:
- Travel and lodging budget (I'll keep it reasonable)
- Time off for the conference dates
- Conference registration fee
I'll definitely share key learnings and insights with the team when I get back, so we can all benefit from the experience. I'm happy to discuss this further if you have any questions.
Let me know what you think!
Thanks,
[Your Name]
输入:
输出:
Subject: New Deployment Pipeline Now Available
Dear Team,
We are pleased to announce the launch of our new automated deployment pipeline, effective immediately. This infrastructure improvement represents a significant operational enhancement for our entire organization.
Key Benefits:
Deployment time has been reduced from 2 hours to approximately 15 minutes, enabling more frequent and reliable releases. Additionally, all development teams now have self-service deployment capabilities, reducing dependency on centralized operations.
What You Need to Know:
A comprehensive training session will be held on Thursday at 2:00 PM to walk through the new process. A detailed FAQ document has been posted to our internal wiki for reference.
Next Steps:
Please plan to attend the training session or review the documentation at your earliest convenience. If you have questions or encounter any issues, please reach out to the DevOps team.
We are confident this will improve our development velocity and system reliability.
Best regards,
Platform Operations Team
输入:
输出:
Hi everyone,
Just wanted to follow up on our design review from Tuesday. We got some great feedback on the dashboard mockups and made some solid decisions moving forward.
Here's where we landed:
We're going with the three-column layout design, which the team felt was the cleanest option. This will require some updates to our design system for the new component types we're using.
Who's doing what:
James will take point on the chart widgets, and Sarah will handle the data table component. I'll coordinate the design system updates to support both.
Next steps:
We'll reconvene in two weeks for the next design review. If anyone spots issues before then, just ping the group.
Thanks for the great collaboration!
[Your Name]
输入:
输出:
Thank you for your inquiry regarding our caching architecture.
The caching layer is implemented using a Redis-based distributed cache with the following specifications:
Configuration:
- Default TTL: 3600 seconds (1 hour)
- TTL is configurable per endpoint via the cache_ttl decorator
- Cache key format: namespace:resource_id:version_hash
- Compression enabled for values exceeding 1KB
Invalidation Strategy:
The system employs a hybrid invalidation approach:
- Event-driven invalidation triggered by data mutation operations
- Time-based expiration using the configured TTL
- Manual invalidation available via administrative interface
Performance Characteristics:
Implementation of this caching strategy has resulted in a 40% reduction in 95th percentile latency for read-heavy operations.
Implementation Details:
Complete code examples and configuration documentation are available in the repository under /docs/caching-architecture. The cache client library provides both synchronous and asynchronous interfaces.
Please reach out if you require additional technical details or have further questions.
Best regards,
[Your Name]
输入:
输出:
Subject: Q4 Planning Session - Summary and Action Items
Dear Team,
This message summarizes the key outcomes and decisions from our Q4 Planning Session held today.
Key Decisions:
1. Platform stability has been prioritized over the addition of new features for Q4
2. The API gateway migration initiative has been rescheduled for Q1 to align with resource availability
3. Budget has been approved for a third-party vendor assessment to evaluate infrastructure options
Assigned Responsibilities:
- Alex Chen will lead the comprehensive architecture review
- All team leads will provide vendor proposals by November 20
- Architecture recommendations document is due November 25
Next Steps:
The next planning meeting is scheduled for December 1 at 10:00 AM. Please come prepared with your respective departmental updates and any outstanding questions.
Should you require clarification on any of the decisions or action items outlined above, please do not hesitate to contact me.
Best regards,
[Your Name]
每封邮件始终保持一致的语调,避免在正式程度或语言级别上出现突兀的转换。
每种上下文类型都遵循适当的结构,以逻辑方式引导读者阅读信息。
发送前请务必审阅生成的邮件。您仍需对最终内容和准确性负责。
每周安装次数
98
代码仓库
GitHub 星标数
43
首次出现
Jan 23, 2026
安全审计
安装于
opencode92
codex85
cursor85
gemini-cli84
github-copilot83
claude-code83
Generate professional, well-structured emails from bullet points or conversation summaries with consistent tone and formatting.
Provide Claude with:
Claude will transform the input into a polished, professional email with:
Purpose : Inform recipients about current progress, completed work, and next steps
Structure :
Best for : Weekly updates, sprint reviews, project progress reports
Purpose : Ask for action, approval, resources, or input from recipients
Structure :
Best for : Budget requests, time off, resources, approvals, feedback
Purpose : Communicate news, changes, or information to a team or stakeholder group
Structure :
Best for : Product launches, policy changes, team updates, organizational changes
Purpose : Continue a conversation, remind about commitments, or move items forward
Structure :
Best for : After meetings, checking on decisions, ensuring progress
Purpose : Reply to an inquiry, offer, or question
Structure :
Best for : Replying to inquiries, addressing questions, responding to proposals
Purpose : Summarize a meeting, conversation, or decision for the record
Structure :
Best for : Meeting summaries, decision documentation, action item tracking
Input :
Output :
Dear Team,
I am writing to provide a status update on the authentication module project for the week of November 4-8.
Completed Items:
The authentication module implementation has been completed and is ready for integration testing. Unit test coverage has reached 94%, demonstrating comprehensive code validation. Performance benchmarks indicate a 15% improvement over the previous implementation.
In Progress:
Database migration testing is currently underway to ensure data integrity during the transition. We anticipate completion by end of day Friday.
Upcoming:
The team will gather on Thursday to discuss and potentially approve the proposed API schema changes. Your input on this matter would be greatly appreciated.
Please let me know if you have any questions or concerns regarding this update.
Best regards,
[Your Name]
Input :
Output :
Hi [Manager Name],
I wanted to reach out about an opportunity I'd like to pursue. I've been selected to give a talk on distributed systems architecture at the upcoming tech conference on March 15-17. It's a great chance to represent the company and share what we've learned.
Here's what I'd need:
- Travel and lodging budget (I'll keep it reasonable)
- Time off for the conference dates
- Conference registration fee
I'll definitely share key learnings and insights with the team when I get back, so we can all benefit from the experience. I'm happy to discuss this further if you have any questions.
Let me know what you think!
Thanks,
[Your Name]
Input :
Output :
Subject: New Deployment Pipeline Now Available
Dear Team,
We are pleased to announce the launch of our new automated deployment pipeline, effective immediately. This infrastructure improvement represents a significant operational enhancement for our entire organization.
Key Benefits:
Deployment time has been reduced from 2 hours to approximately 15 minutes, enabling more frequent and reliable releases. Additionally, all development teams now have self-service deployment capabilities, reducing dependency on centralized operations.
What You Need to Know:
A comprehensive training session will be held on Thursday at 2:00 PM to walk through the new process. A detailed FAQ document has been posted to our internal wiki for reference.
Next Steps:
Please plan to attend the training session or review the documentation at your earliest convenience. If you have questions or encounter any issues, please reach out to the DevOps team.
We are confident this will improve our development velocity and system reliability.
Best regards,
Platform Operations Team
Input :
Output :
Hi everyone,
Just wanted to follow up on our design review from Tuesday. We got some great feedback on the dashboard mockups and made some solid decisions moving forward.
Here's where we landed:
We're going with the three-column layout design, which the team felt was the cleanest option. This will require some updates to our design system for the new component types we're using.
Who's doing what:
James will take point on the chart widgets, and Sarah will handle the data table component. I'll coordinate the design system updates to support both.
Next steps:
We'll reconvene in two weeks for the next design review. If anyone spots issues before then, just ping the group.
Thanks for the great collaboration!
[Your Name]
Input :
Output :
Thank you for your inquiry regarding our caching architecture.
The caching layer is implemented using a Redis-based distributed cache with the following specifications:
Configuration:
- Default TTL: 3600 seconds (1 hour)
- TTL is configurable per endpoint via the cache_ttl decorator
- Cache key format: namespace:resource_id:version_hash
- Compression enabled for values exceeding 1KB
Invalidation Strategy:
The system employs a hybrid invalidation approach:
- Event-driven invalidation triggered by data mutation operations
- Time-based expiration using the configured TTL
- Manual invalidation available via administrative interface
Performance Characteristics:
Implementation of this caching strategy has resulted in a 40% reduction in 95th percentile latency for read-heavy operations.
Implementation Details:
Complete code examples and configuration documentation are available in the repository under /docs/caching-architecture. The cache client library provides both synchronous and asynchronous interfaces.
Please reach out if you require additional technical details or have further questions.
Best regards,
[Your Name]
Input :
Output :
Subject: Q4 Planning Session - Summary and Action Items
Dear Team,
This message summarizes the key outcomes and decisions from our Q4 Planning Session held today.
Key Decisions:
1. Platform stability has been prioritized over the addition of new features for Q4
2. The API gateway migration initiative has been rescheduled for Q1 to align with resource availability
3. Budget has been approved for a third-party vendor assessment to evaluate infrastructure options
Assigned Responsibilities:
- Alex Chen will lead the comprehensive architecture review
- All team leads will provide vendor proposals by November 20
- Architecture recommendations document is due November 25
Next Steps:
The next planning meeting is scheduled for December 1 at 10:00 AM. Please come prepared with your respective departmental updates and any outstanding questions.
Should you require clarification on any of the decisions or action items outlined above, please do not hesitate to contact me.
Best regards,
[Your Name]
Each email maintains consistent tone throughout, avoiding jarring switches in formality or language level.
Each context type follows an appropriate structure that guides readers through the information logically.
Always review generated emails before sending. You remain responsible for final content and accuracy.
Weekly Installs
98
Repository
GitHub Stars
43
First Seen
Jan 23, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode92
codex85
cursor85
gemini-cli84
github-copilot83
claude-code83
头脑风暴技能:AI协作设计流程,将创意转化为完整规范与实施计划
89,200 周安装