Official recipe · Tool workflows

Generate invitation options with a reusable intake skill

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Event organizers want invitation choices that reflect the same details without repeatedly explaining the brief for each design.

Agent job

Collect event information through the reusable intake skill and generate three invitation designs with editable links.

Expected output

Three PNG invitation previews and corresponding editable designs for the user to select and revise.

Where this framing comes from

Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing

Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

An organizer choosing invitation artwork may repeatedly explain the same event facts to obtain different visual options. Small inconsistencies between designs can leave one attractive version with the wrong time, venue or RSVP detail.
This job could keep a single approved event brief behind several editable alternatives. The organizer can compare aesthetic choices while checking that all versions communicate the same essential information before selecting one.

Why an agent / simpler alternative

Useful judgment: Translate event tone into distinct visual directions while preserving factual content and readability.
Simpler alternative: Use one invitation template when the visual direction and text are already settled.
Unsuitable when: Event details are unresolved or the designs would expose private addresses or guest information without approval.

Proposed inputs

Name
Event brief
Owner
Organizer
Minimum scope
Title, date, time, venue wording and RSVP method
Quality check
Confirm year, timezone and public/private information scope
Name
Design preferences
Owner
Organizer
Minimum scope
Audience, tone, authorized assets and format
Quality check
Separate mandatory details from optional styling

Access and setup — proposed or unknown

Proposed minimum: Start with a shared content checklist and three layout descriptions; no design-platform access or image generation.
Compatibility unknowns: Current reusable-skill support, design integration, editable links and runtime compatibility are unknown.
External actions requiring approval: Uploading assets, creating external drafts, publishing or sending invitations requires authorization.

Expected deliverable and review checks

Proposed artifact: Three proposed invitation directions with a common fact checklist and editability/review requirements.
Critical checks: Match dates and RSVP details across variants; check text hierarchy, contrast and room for longer venue names.
Missing output evidence: This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

Signal
A decorative font obscures essential details
Why it matters
The invitation becomes harder to use
Proposed response
Reserve decorative treatment for noncritical elements.
Signal
One variant retains an earlier event time
Why it matters
Visual revisions conceal a factual inconsistency
Proposed response
Reconcile all variants against the approved brief.

Effort and cost — unknown

Setup work: Finalize event facts and reusable intake fields.
Ongoing review: Organizer chooses a direction and rechecks final content after edits.
Unknowns: Asset rights, design-generation costs, export quality and editability are unknown.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Invent an event brief and three layout descriptions, one with an old time and another with overcrowded RSVP text; review options only.
Acceptance checks: Flag both content/legibility issues; preserve shared facts; make no design upload or send.
Stop conditions: Stop if essential event details or permission to disclose the venue is unresolved.

Limits

Preview images and editable designs do not establish that invitations were delivered, accepted or accessible to every guest.

Tasks: Customer service

Useful for: Event planner Designer Personal and household

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

ManusIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://www.manus.im/blog/deep-dive-canva-connector ↗

Attributed to: Manus

Official recipe

Original action type: tool_action
What the source supports: Collect event details through a saved skill, create three invitation designs and return PNG previews with editable links.
Source outcome limits: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: User selects and edits a preferred design; no sending described.
Named tools: Manus Skills; Canva
Model or version: Unknown
Publication date: 2026-06-12
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: confirm venue timezone, date format and permitted use of guest names or photos.
Recommended approval boundaries: Approve source access and data scope first; require human review before production changes, external sharing or consequential decisions.