---

name: e-commerce-product-title-generator description: "Generate platform-aware product titles from verified product facts."

E-commerce Product Title Generator

Generate platform-aware product titles from verified product facts.

Required Aident Actions

• <action-tag>composio:textcortex_tools:textcortex_create_product_title</action-tag> (required inputs: inspect the current schema): Tool to generate catchy product titles for listings. Use when you need to create compelling titles for product listings or descriptions.

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 material, destination, audience, constraints, and acceptance criteria.
2. Apply the sAction · Create Product Titlenvoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. 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

• Collect the product facts, brand, differentiators, target platform, audience, keyword priorities, and title limits.
• Separate verified facts from optional positioning and prohibit unsupported claims.
• Use composio:textcortex_tools:textcortex_create_product_title with the reviewed context.
• Evaluate the returned titles for accuracy, readability, keyword use, prohibited terms, and platform length.
• Return ranked title options and do not claim that full descriptions or listings were created.

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.