---

name: cold-email-deliverability-diagnostics description: "Email deliverability best practices and troubleshooting"

Cold Email Deliverability Diagnostics

Email deliverability best practices and troubleshooting

Required Aident Actions

• <action-tag>composio:instantly_tools:instantly_inbox_placement_analytics_deliverability_insights</action-tag> (required inputs: test_id): Tool to retrieve deliverability insights for inbox placement tests. Use when you need detailed percentage breakdowns of emails landing in spam, inbox, and category folders with optional date range filtering and...

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source Action · Inbox Placement Analytics Deliverability Insightselow to create a concrete plan. Resolve ambiguity before invoking an Action.
2. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
3. Inspect the current schema and prepare the minimum valid input for each selected Action.
4. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
5. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Keep the workflow scoped to the source-derived objective: Email deliverability best practices and troubleshooting
• When needed, use composio:instantly_tools:instantly_inbox_placement_analytics_deliverability_insights only for this supported effect: Tool to retrieve deliverability insights for inbox placement tests. Use when you need detailed percentage breakdowns of emails landing in spam, inbox, and category folders with...
• Verify the returned artifact or provider state against the requested acceptance criteria before reporting completion.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.