القائمة
Email service operations via Cronus. Triggers: email, cronus, smtp, template, email usage, sending. NOT for: monitoring alerts (use sapcc-metrics/Maia).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | sapcc-email |
| description | Email service operations via Cronus. Triggers: email, cronus, smtp, template, email usage, sending. NOT for: monitoring alerts (use sapcc-metrics/Maia). |
| version | 1.0.0 |
| metadata | {"service":["cronus"],"task":["manage","inspect","debug"],"persona":["developer","platform-engineer"]} |
Inspect email service status: check sending usage and list available email templates for the current project.
Note: Cronus MCP tools are planned but not yet implemented in the MCP server. The skill documents the service for reference. When tools become available, they will follow the
cronus_prefix pattern.
| Tool | Purpose | Expected Parameters |
|---|---|---|
cronus_list_senders | List verified sender addresses | project_id |
cronus_get_usage | Get email sending usage/limits | project_id |
Until Cronus MCP tools are available:
hermes_list_events(target_type=email/*) for email audit trailNo parameters on either tool. Both Cronus tools operate on the current project scope determined by the authenticated credentials. You cannot query a different project without re-scoping.
Usage is project-scoped, not user-scoped. The usage endpoint shows aggregate email sending statistics for the entire project, not per-user breakdowns.
Templates are pre-configured, not arbitrary. Cronus templates are set up by project administrators. You cannot create or modify templates via MCP tools — these are read-only inspection tools.
Cronus is SAP CC-specific. This is not a standard OpenStack service. It is a SAP Converged Cloud extension for managed email sending. Do not confuse with external SMTP services or third-party email providers.
Rate limits and quotas are enforced server-side. If usage shows high volume, the project may be approaching sending limits. The usage response typically includes rate/quota information.
Email sending failures are not shown here. Cronus usage shows aggregate stats. For individual delivery failures or bounces, check application logs or the Cronus dashboard (not available via MCP).
cronus_get_usage — inspect current sending volume, quotas, and status.cronus_list_senders — see all configured templates.cronus_get_usage — check if the project has hit sending limits.hermes_list_events filtered to Cronus actions.| Need | Service | Tool |
|---|---|---|
| Who configured email templates | Hermes | hermes_list_events(target_type=template) |
| Project identity and scope | Keystone | keystone_list_projects |
| Monitoring alerts (not email) | Maia | maia_list_alerts |
| Application credentials for SMTP auth | Keystone | keystone_list_application_credentials |
Audit trail investigation on SAP Converged Cloud using Hermes. Triggers: audit, who changed, what happened, hermes, events, compliance, CADF, activity log, trace action, who did, what was done, event history
Autoscaling operations via Castellum. Triggers: autoscaling, castellum, resize, scaling, threshold, auto-resize, capacity management. NOT for: manual quota changes (use sapcc-quota/Limes).
Bare metal node operations via Ironic. Triggers: baremetal, bare metal, ironic, node, provision state, hardware, physical server. NOT for: virtual servers (use sapcc-compute/Nova).
Manage compute instances on SAP Converged Cloud. Covers server lifecycle, flavor selection, status transitions, and cross-service correlation with networking and storage. Use when: listing VMs, checking server status, debugging instance issues, performing server actions (start/stop/reboot), selecting flavors, or investigating why a server won't start. NOT for container workloads (use sapcc-registry) or bare metal.
Archer endpoint service management for private network connectivity in SAP Converged Cloud. Triggers: endpoint service, private link, archer, private connectivity, service endpoint, internal access, cross-project access
DNS zone and recordset operations via Designate. Triggers: dns, zone, recordset, domain, designate. NOT for: network ports, floating IPs (use sapcc-networking).