Mariete method

Test and review

Reference only. Project progress and credentials come from assessed work.

Test the configured worker before adding recurring automation.

Representative test

Use a small input that resembles real work but cannot cause material harm. The test should cover:

  • the expected path,
  • missing input,
  • unavailable tool or credential,
  • an action that requires approval,
  • a stop condition.

Review layers

  1. Configuration: correct identity, instructions, tools and MCPs.
  2. Workflow: correct template, variables and active status.
  3. Run result: correct output, cited evidence and visible gaps.
  4. Authority: no write or external action beyond the approved boundary.
  5. Recovery: a clear response to missing data, tool failure or human rejection.

Do not hide a failed test by editing the output. Change the configuration or workflow, run a new test and preserve what changed.

Example prompts

Clickable example prompts should be specific and self-contained. They help users discover the worker's supported job, but they are not a substitute for the system instructions or workflow template.

Test and review | Mariete Academy