一键导入
log-activity
Log a new activity (call, meeting, email, task, note) on a Salesforce account timeline — draft first, confirm with the user, then write
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Log a new activity (call, meeting, email, task, note) on a Salesforce account timeline — draft first, confirm with the user, then write
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Microsoft 365 surface — READ Frank's mailbox / Wes's calendar / OneDrive (shift reports, SOPs) AND a strict H-I-T-L workflow to draft and send an email (e.g. brief Wes on the morning incident).
Compute and plot OEE — a 7-day trend chart with target/threshold lines, an overlay of telemetry alarms and downtime stops, plus a flat CSV export. Saves /tmp/oee-trend-<plant>-line-<N>-<date>.png + .csv.
The Olympus Cleveland-plant Standard Operating Procedure — alarm thresholds, escalation matrix, supplier quality-hold rules, OEE definitions, incident-brief template requirements. Cite the section number when answering.
| name | log-activity |
| description | Log a new activity (call, meeting, email, task, note) on a Salesforce account timeline — draft first, confirm with the user, then write |
| enabled | true |
Use this skill when the user wants to log something to a Salesforce account's activity timeline — e.g. "Log the QBR outcome on Acme", "Note that I have a follow-up task with Margaret next Tue", "Email logged with Stark — they signed".
This calls salesforce_log_activity, which is a write tool. Always draft and confirm before writing.
salesforce_search_accounts_by_name first to resolve to an ACC-*.USR-101 Alex Rivera) unless the user explicitly says they're logging it on behalf of someone else.Show the draft as a small block:
I'll log this to Acme Corp (ACC-001):
Type: Meeting
Subject: QBR with CFO + FP&A
Date: 9 Jun 2026
Owner: Alex Rivera (USR-101)
Summary: Reviewed Q2 usage growth (32% YoY). Margaret reconfirmed
Analytics expansion budget — procurement red-lines back this
week. Action: Devon to walk Priya through new SLA addendum
by 6/13.
Confirm to log? (yes / edit / cancel)
Use ask_user to pause. Wait.
salesforce_log_activityAfter the write succeeds:
ACT-* idsalesforce_log_activity without explicit confirmation in the same turn.YYYY-MM-DD) in the tool call.salesforce_get_account → owner_user_id).