Target Audience
Skills
Submission Type
About
Suggested Prerequisites
Rubric
CategoryWeightWhat we're evaluatingNeeds ImprovementMeets ExpectationsExcellent
Prove you can build, test and run a production-ready agent with AI Marketer. Give it a clear job and goal, real brand context, deliberate permissions and a trigger that runs it on its own.

| Category | Weight | What we're evaluating | Needs Improvement | Meets Expectations | Excellent |
|---|---|---|---|---|---|
| Goal & Instructions | 25% | Can you give an agent one scoped, repeatable job and instructions it follows without you? | The goal is a task rather than an outcome, the agent does several jobs, or the instructions are AI Marketer’s first version or an installed template with no edits. | The agent does one job for a named reader, with a success check and instructions that give a role, ordered steps and defaults. One thing is missing or unexplained: the judgment step, or the named edits to AI Marketer’s first version. | The agent does one job for a named reader, and the walkthrough says what decision that reader makes with the output. At least one step uses judgment, such as selecting, ranking or drafting from data. The instructions include a success check someone could apply to the output. They give a role, ordered steps, and a default or fallback for every optional input. Version history shows AI Marketer’s first version, and the candidate names at least two edits they made to it. |
| Context | 20% | Can you give an agent context that changes its output in a way you can check? | A context source is connected, but the instructions never mention it, or the outputs show no effect from it. | A context source is connected, the instructions say what it’s for, and outputs from the same input show a difference. The candidate doesn’t name an effect anyone can check, or the only effect is cosmetic. | At least one context source is connected: a knowledge base, the Brand Kit, a skill, or a Profound document or sheet. The instructions say what each source is for. Outputs from the same input show the context’s effect, and the candidate names one effect anyone can check, such as a topic skipped or a term used. |
| Tools & Permissions | 20% | Can you connect only what the job needs and defend every permission? | Tools or capabilities are left on by default, every action is set to Allow with no reason given, or the permissions are never shown. | Only the tools the job needs are connected, unused capabilities are off, and the walkthrough shows the permissions for the actions the run uses. The riskiest action isn’t named, or the reason for its setting is missing. | Only the tools and Profound data the job uses are connected. An agent that delivers a doc or sheet inside Profound needs no connector. Capabilities the job doesn’t use are off in Advanced settings. The walkthrough shows the Allow, Ask or Block setting for every action the run uses and every action with side effects. The candidate names the riskiest action and says what a different setting would cause. |
| Testing & Iteration | 20% | Can you critique an agent’s first output and improve it with deliberate changes? | Only one change, only trivial edits such as a typo or a rename, a different input for the second run, or no first output shown. | The first output comes from the earliest run in run history, and version history shows at least two changes beyond a typo or a rename. The candidate doesn’t tie each change to a defect, doesn’t explain the order of the changes, or doesn’t rerun the same input. | The first output comes from the earliest run in run history, and the candidate names its defects. Version history shows at least two changes beyond a typo or a rename, each fixing a named defect, and the first change fixes the largest one. The same input is run again, and each named defect is gone. |
| Unattended Operation & Sharing | 15% | Can you make an agent run with no one present, deliver output its reader can use, and control who can use it? | There’s no trigger, the agent isn’t published, or the setup would stall: questions are on, approvals are set to Ask, or the agent relies on approvals granted while testing. | The agent is published with a trigger that fits the job. Allow questions is off, and approvals are set to Approve or Deny with a reason. At least two of these are also shown: a finished run the trigger started, inputs that stay correct between runs, output sized for its reader, and sharing with a reason. | The agent is published with a trigger that fits the job. A run that trigger started is opened from run history, and it finished with its output shown. Allow questions is off, and When a tool needs approval is set to Approve or Deny, consistent with the tool permissions and explained. Any input that changes between runs, such as a date, stays correct. The output lands where the reader uses it, in a size they can use. The walkthrough shows who the agent is shared with and why; keeping it private is fine when the reason is given. |