Zambo task directory · page 4 of 4
Context guides, page 4 of 4
More context guides. Each holds every starter for its context with inputs, deliverables, review checks and stop points.
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 49–64 of 64
Creators
Sponsorship brief
The creator supplied a draft deliverable list without verified audience figures.
- approved deliverables
- disclosure obligations
- usage and review terms
32 startersExtract the requirementsFind the unanswered questions
Creators
Editorial pitch
The writer supplied an angle and two public sources but no completed interviews.
- story angle
- verified supporting material
- editor submission rules
32 startersExtract the requirementsFind the unanswered questions
Creators
Research notebook
The researcher supplied a dated bibliography and a list of unanswered questions.
- source inventory
- research question
- uncertain observations
32 startersExtract the requirementsFind the unanswered questions
Creators
Book proposal
The author supplied a synopsis and a sample chapter without publisher feedback.
- synopsis
- sample material
- substantiated author background
32 startersExtract the requirementsFind the unanswered questions
Creators
Animation storyboard
The animator supplied six scene descriptions and an approved aspect ratio.
- scene outline
- runtime constraints
- asset rights and references
32 startersExtract the requirementsFind the unanswered questions
Creators
Music release plan
The artist supplied a draft timeline with one sample-clearance question outstanding.
- approved assets
- confirmed distribution dates
- rights-clearance status
32 startersExtract the requirementsFind the unanswered questions
Creators
Portfolio case study
The designer supplied public screenshots and an approved description of their contribution.
- approved project description
- client-safe artifacts
- verified role and outcomes
32 startersExtract the requirementsFind the unanswered questions
Creators
Testimonial permission request
The owner supplied a real quote but has not obtained permission to publish it.
- exact supplied quote
- intended publication locations
- consent owner
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
AI agent task brief
The owner permits read-only research and requires approval before any external action.
- goal and constraints
- allowed tools
- human approval boundaries
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Tool integration checklist
The developer supplied a current tool schema and one missing-argument example.
- live tool contract
- required inputs
- known error responses
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
AI evaluation rubric
The evaluator supplied a task definition and three criteria but no measured results.
- task definition
- scoring criteria
- reviewer qualifications
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Benchmark run plan
The tester supplied fixed cases and wants a plan for reporting unsuccessful runs.
- fixed test cases
- environment constraints
- measurement method
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Prompt version notes
The author supplied two prompt versions and an untested regression checklist.
- old and proposed prompt
- intended behavior change
- regression cases
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Retrieval source inventory
The owner supplied three public source references with different update dates.
- source URLs or redacted excerpts
- permission and freshness notes
- coverage gaps
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Human review queue
The queue contains two proposed outputs awaiting separate authorized reviewers.
- redacted pending items
- review criteria
- authorized reviewer roles
32 startersExtract the requirementsFind the unanswered questions
Agents and power users
Multi-AI handover plan
The owner supplied a checked summary and wants a controlled continuation in another AI.
- confirmed completed work
- remaining steps
- recipient access boundaries
32 startersExtract the requirementsFind the unanswered questions
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