Maya Brooks

AI agents source worksheet file: use this as a comparison ledger before another broad note goes into the ai agents playbooks folio. The attached AI agent evaluation checklist gives the post a document to work from: check OpenAI agent guide, compare it with OpenAI Agents SDK for JavaScript, then write the decision that changes.

The ledger fields are reader problem, source checked, claim to verify, decision affected, missing context, and next test. They keep the post useful after the first read because the next person can download the file, copy the tracker row, and see where the evidence is still thin.

OpenAI agent guide is the primary reference. It should settle one concrete AI agents decision, checklist item, tracker row, worksheet field, or template example, not just make the topic sound more complete.

OpenAI Agents SDK for JavaScript is the comparison source. If it agrees with the primary reference, keep the shared rule, route, setting, policy, metric, or pattern. If it conflicts, put the disagreement in the worksheet instead of sanding it down.

OpenAI Agents JS source adds the artifact angle: document, dataset, repository, guide, API, checklist, or worked example. File the note under ai-agents, agent-workflows, tool-use, evals only where those labels match a real worksheet field.

Video cross-check: OpenAI video archive belongs here for workflow texture. Look for the exact screen, demo, route, process step, cut setting, or session moment that changes how the ledger is filled out.

Two sources to open first: platform.openai.com/docs/guides/agents and youtube.com/@OpenAI/videos. Use the attached file to record which claim each source supports, which claim remains opinion, and which detail should be removed if nobody can verify it.

The post earns a reply when someone improves one field: a better source, sharper caveat, stronger example, or missing beginner trap. The pass-fail test is whether the worksheet still helps after the title and author are removed.