5. 将鼠标悬停在该任务上并选择 **查看任务详情**.
6. 在右侧滑出面板中，选择 **交付内容。**
* 你可以查看其被检测到的日期。
7. 你可以查看 *创作者* 内容的 *截止日期*，以及 *匹配的话题标签* 以及已识别的内容。你还可以通过选择社交平台图标，在该社交平台上查看内容。
* 如果使用相同话题标签发布了多个交付内容，它们也会显示在这里供你审核。
8. 选择你想为该交付内容提交的内容，然后选择 **批准帖子**.
* 如果未自动检测到正确的帖子，请选择  **\[更多]** → **加载更多帖子** 查看更多帖子，或选择  **\[更多]** → **手动提交交付内容。**
{% endtab %}
{% endtabs %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-campaigns-for-brands/submit-campaign-tasks-on-behalf-of-your-hired-creators.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
%20copy.png?alt=media&token=404e7225-62aa-491b-8497-f698119f4d1d)