메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/kmavrodis/kratos-agent --skill email-draft명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Read the plant-floor Azure IoT surface — device twins (spindles, conveyors, robotic arms, vision systems), time-series telemetry with pre-annotated alarms, downtime events with cause codes and lot ids, and per-line OEE rollups (Availability × Performance × Quality).
Share generated files (PDFs, charts, CSVs) with Frank by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.
Build the downloadable incident brief PDF — cover + KPI strip + OEE chart + downtime timeline + root-cause narrative + supplier/material signals + recommended actions + sign-off, per SOP §7.1. Renders via the inline HTML template + Playwright.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | email-draft |
| description | Compose professional emails from brief instructions, bullet points, or context |
| enabled | true |
When the user asks you to write, draft, or compose an email, follow these guidelines:
Before drafting, identify:
If the user provides bullet points or rough notes, expand them into polished prose. If context is vague, ask one clarifying question — do not over-ask.
Always produce a complete email with:
Subject: <concise, actionable subject line>
<Greeting>,
<Opening — context or purpose in 1-2 sentences>
<Body — organized paragraphs or bullet list covering all key points>
<Closing — clear next step or call to action>
<Sign-off>,
<Name placeholder>
| Audience | Tone | Example greeting |
|---|---|---|
| Executive / C-suite | Formal, concise, results-focused | "Dear [Name]," |
| Colleague / team | Professional-friendly | "Hi [Name]," |
| External client | Warm but professional | "Dear [Name]," |
| Support / vendor | Direct and clear | "Hello [Team]," |
If the user asks for multiple options, provide 2-3 versions with different tones (e.g. formal vs. friendly) and let them pick.
Subject: Follow-Up — Portfolio Review Meeting [Date]
Dear [Client Name],
Thank you for taking the time to meet [today/yesterday]. Below is a summary of the key points we discussed:
- [Portfolio performance overview]
- [Rebalancing actions agreed upon]
- [Next steps and timeline]
I will [action item] by [date]. In the meantime, please don't hesitate to reach out if you have any questions.
Best regards,
[Advisor Name]
[Title] | [Firm Name]
Subject: Portfolio Rebalancing — [Client Name / Portfolio ID]
Dear [Client Name],
As discussed, we are proceeding with the following adjustments to your portfolio:
| Action | Security | Amount/Units |
|--------|----------|-------------|
| [Buy/Sell] | [Ticker — Name] | [Units/Amount] |
Rationale: [brief explanation aligned with risk profile and investment objectives].
These changes will be executed within [timeframe]. You will receive a confirmation statement once completed.
Please confirm your approval by [date], or contact me with any questions.
Best regards,
[Advisor Name]
Subject: Q[N] [Year] Portfolio Review — [Client Name]
Dear [Client Name],
Please find attached your quarterly portfolio review for Q[N] [Year].
Key highlights:
- Portfolio return: [X]% (benchmark: [Y]%)
- [Notable change or achievement]
- [Upcoming action or recommendation]
I recommend we schedule a call to discuss [specific topic]. Please let me know your availability.
Best regards,
[Advisor Name]
If the user asks to revise, adjust tone, shorten, or expand — iterate on the previous draft rather than starting from scratch.
If the user wants the email saved as a file:
code_interpreter to write the email to /tmp/email_draft.txt (or .md)[placeholder] markers[Your Name]User: "Write an email to my manager asking for time off next week"
Output:
Subject: PTO Request — [Date Range]
Hi [Manager Name],
I'd like to request paid time off from [Start Date] through [End Date]. I've ensured my current deliverables are on track and will hand off any pending items to [Colleague Name] before I leave.
Please let me know if you need any additional details or if this timing works for the team.
Thanks,
[Your Name]
User: "Draft a client follow-up after our demo yesterday, mention the pricing proposal"
Output:
Subject: Great Connecting Yesterday — Next Steps on Pricing
Dear [Client Name],
Thank you for taking the time to join yesterday's demo. It was great to walk through the platform with your team, and I appreciated the thoughtful questions.
As discussed, I've attached our pricing proposal for your review. Here's a quick summary:
- **Starter tier**: [details]
- **Enterprise tier**: [details]
- **Custom options**: Available based on your team's requirements
I'd love to schedule a follow-up call next week to discuss any questions. Would [Day] at [Time] work for you?
Looking forward to hearing from you.
Best regards,
[Your Name]