Skip to main content

Prompt Engineering with Weaver

Good prompt ⇒ Great agent
Weaver will try its best with whatever you throw at it, but the clearer the ask, the cleaner the wiring.
Think tasks, not code ... your job is to explain specifically what you want and let Weaver do the rest.

TL;DR
State a goal ➜ list skills ➜ add constraints. That’s 95 % of prompt craft.

Mind-set Shift: Describe Jobs, Not Code​

Bad habit (thinking like a developer):

“Call the summarise() function with the weekly_sales dataset.”

Better habit (thinking like a PM):

“Summarise weekly sales data for Monday stand-up.”

More examples:

  • “Translate this blog post to Spanish.”
  • “Email the summary to the team every Friday at 4 PM.”
  • “Resize all images in /uploads to 1024 px wide.”

The Universal Prompt Framework​

Goal: [What you want to achieve]

Skills:

  1. [Skill 1]
  2. [Skill 2]
  3. …

Constraints:

  • [Any mandatory formats, limits, sources]

Use Goal → Skills → Constraints every time.

Good vs Poor Prompts (Kyoto Edition)​

Blog Prompt: Travel
SEOFormal toneMarkdown
Goal: Draft a 600-word travel article about Kyoto. Skills: 1. Research attractions and local cuisine 2. Generate SEO-friendly title and slug 3. Produce Markdown article 4. Extract five focus keywords Constraints: – For...
Show more
Write something about Kyoto. Make it good for SEO.

The first prompt gives Weaver four precise blocks to assemble. The second leaves enough ambiguity to fill a Zen garden.

Advanced Examples​

Weekly Sales Digest​

Goal: Deliver a Monday-morning sales digest email.

Skills:

  1. Fetch weekly_sales.csv from S3
  2. Summarise trends into 5 bullet points
  3. Generate chart PNG
  4. Email to sales-team@acme.com

Constraints:

  • Use “Sales Digest” as subject
  • Skip weeks with less than 100 rows

Multilingual Blog Pipeline​

Goal: Publish each post in EN → ES → FR.

Skills:

  1. Detect new post published to WordPress
  2. Translate Markdown to Spanish
  3. Translate Spanish to French
  4. Post translations under /es/ and /fr/

Constraints:

  • Preserve Markdown formatting
  • Keep code blocks untouched

Airtable → Slack Snapshot​

Goal: Send daily Airtable summary to Slack.

Skills:

  1. Query “Tasks” base, get today’s records
  2. Count tasks by status
  3. Format a Slack message
  4. Post to #daily-ops

Constraints:

  • Run at 17:00 UTC
  • Use Slack block-kit

Prompt Debugging 101​

  1. Locate the misbehaving component (red border).
  2. Click on the component and ask Weaver to fix it and explain what changed (or click Fix with AI button on the componenet):
    Output missed the bullet list. Ensure summary is bullet-pointed.
  3. Re-run just that block with debug mode enabled and step through it, not the whole agent.
  4. Rinse, repeat, ship.

Still wrong? Break the skill in two. Smaller skills fail more loudly.

Get the best out of Weaver

Remember: A clear goal, numbered Skills, and explicit constraints let Weaver be the best AI workflow composer you’ve ever met.

Cheatsheet​

If you want…Add this to Skills
Ranking or classification“Classify text sentiment”
Extraction“Extract company names”
Transformation“Convert JSON to CSV”
Messaging“Send message to Teams channel”

Next Up​