Zambo task directory
2048 starter workflows, grouped into 64 guides
Pick the situation you are in. Each guide holds every starter for that context with what to have ready, what comes back, how to review it and when to stop.
These are starter recipes, not executed or certified automations. They do not promise outcomes, search ranking, accuracy, or that any outside provider is available.
Search all 2048 starters
Search runs in this browser on a local copy of the catalog. Your words are not saved, added to the address, or sent anywhere.
Type a word or pick a category.
Guides 1–16 of 64
Client work
Website brief
The supplied brief asks for a five-page site with a keyboard-accessible menu.
- pages and navigation
- visitor goals
- content owner
32 startersExtract the requirementsFind the unanswered questions
Client work
Brand identity brief
The owner requests a calm visual identity and editable vector files.
- brand attributes
- approved references
- asset formats
32 startersExtract the requirementsFind the unanswered questions
Client work
Logo handoff
The approved package needs light and dark SVG versions and a usage sheet.
- approved mark versions
- export sizes
- usage restrictions
32 startersExtract the requirementsFind the unanswered questions
Client work
Video editing brief
The supplied edit notes request a vertical cut with captions and a shorter intro.
- source footage inventory
- runtime and aspect ratios
- review timestamps
32 startersExtract the requirementsFind the unanswered questions
Client work
Podcast production brief
The producer supplied a transcript and wants chapter markers and an episode summary.
- episode outline
- guest permissions
- audio delivery format
32 startersExtract the requirementsFind the unanswered questions
Client work
Photography shot list
The supplied brief lists product close-ups and a team portrait at an approved location.
- required subjects
- locations and timings
- usage permissions
32 startersExtract the requirementsFind the unanswered questions
Client work
Copywriting brief
The client supplied three verified features and asked for plain-language service copy.
- intended audience
- substantiated product claims
- voice examples
32 startersExtract the requirementsFind the unanswered questions
Client work
Translation brief
The owner supplied a short product guide and an approved terminology list.
- source and target languages
- approved glossary
- locale constraints
32 startersExtract the requirementsFind the unanswered questions
Software
Product requirements document
The brief requires account export but explicitly excludes bulk account deletion.
- user problems
- acceptance criteria
- out-of-scope items
32 startersExtract the requirementsFind the unanswered questions
Software
Bug report
The report says the save button fails after a browser refresh on a named version.
- reproduction steps
- expected and observed behavior
- environment details
32 startersExtract the requirementsFind the unanswered questions
Software
Release notes
The supplied change list includes one fix and a migration note still awaiting review.
- merged changes
- known issues
- rollout audience
32 startersExtract the requirementsFind the unanswered questions
Software
Software migration plan
The owner wants a plan for a version upgrade with a reversible first stage.
- current and target versions
- backup and rollback approach
- compatibility constraints
32 startersExtract the requirementsFind the unanswered questions
Software
Software test plan
The supplied journeys cover sign-in export and an expired-session error.
- critical user journeys
- test environments
- expected results
32 startersExtract the requirementsFind the unanswered questions
Software
Accessibility review notes
The reviewer noted a missing focus indicator on the supplied checkout mockup.
- tested pages
- observed keyboard behavior
- assistive-technology notes
32 startersExtract the requirementsFind the unanswered questions
Software
API integration plan
The API notes list a read endpoint and a write endpoint with an idempotency key.
- documented endpoints
- authentication method
- rate limits and retries
32 startersExtract the requirementsFind the unanswered questions
Software
Incident review
The timeline records elevated errors and a later recovery with an uncertain cause.
- confirmed timeline
- observed impact
- follow-up owners
32 startersExtract the requirementsFind the unanswered questions
All 64 context guides by category
Client work
Software
Marketing
Operations
Community
Small business
Creators
Use a starter in four steps
- Connect. Open Add Zambo and follow the steps for the AI app you already use.
- Paste. Copy one starter prompt below and paste it into a new chat in that app.
- Answer. Give the real inputs it asks for. It should ask rather than guess, and stop before anything leaves the chat.
- Check. When the work closes, open the returned workflow link and confirm it at /verify/. A receipt shows which Zambo calls were recorded, not that an answer is correct.
Large files, code or a multi-day client job?
- Make a work manifest. List the goal, files and revisions, acceptance checks, private material, approved tools and budget. Ask your AI for a plan before running it.
- Keep files in your client. Use your AI app to extract PDF text, OCR images or inspect a repository. Zambo is not a general file-storage service or code-execution sandbox. Never paste credentials or private client material into public receipts.
- Analyze in tracked parts. The complete MCP request must fit 64 KiB. For
doc_intel, public UTF-8 text URLs can be up to 1 MiB. Each call covers at most 24,000 UTF-16 code units. Follownext_offsetandsource_sha256, retain the same job ID and record every range. Source changes must stop the continuation. - Check outside work where it happened. Run code and tests in your own authorized environment. Retain diffs, commands, exit codes and source references. A receipt records a call; it does not prove deployment, correctness or client approval.
- Resume deliberately. Save completed ranges, unresolved questions, failed steps and the next action in a private handover. Review partial results before closing the job; never replay a purchase, publish or send action without checking its previous outcome.
Day Pass and Zambo Pass provide the same access for different lengths of time. Paying removes Zambo's applicable daily caps, not file-size limits, provider outages, third-party costs or approval requirements. Choose the duration that fits your job.
What it costs
- Free
- 20 metered calls per UTC day, shared across tools, plus one free wrap-up handover each day.
- Day Pass
- $0.99 for 24 hours, one payment.
- Zambo Pass
- $29 for 30 days, one payment, same access as the Day Pass for longer.
- Lifetime
- $250 one payment, for a human buyer only, while Zambo operates. Current Level 2 features; not future features or third-party provider costs.
No subscription and no automatic renewal. Some tools have smaller free allowances: doc_intel allows 3 analyses/day. A pass does not pay for third-party AI plans or outside services, and longer jobs can use more calls than the free allowance. See pass details
For agents and tools
- /workflows/tasks/catalog.json manifest: version, total, contexts, items
- /workflows/tasks/catalog.jsonl one task record per line
- /workflows/recipes/tasks/<id>.v1.json per-starter recipe, status
illustrative_not_executed - /workflows/recipes/schema.v1.json recipe format