Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update task generation prompt #473

Merged
merged 1 commit into from
Jun 14, 2024
Merged

Conversation

ykeremy
Copy link
Contributor

@ykeremy ykeremy commented Jun 14, 2024

🚀 This description was created by Ellipsis for commit c73f830

Summary:

Updated task generation template to conditionally require navigation_goal and data_extraction_goal based on new reasoning fields in skyvern/forge/prompts/skyvern/generate-task.j2.

Key points:

  • Updated skyvern/forge/prompts/skyvern/generate-task.j2
  • Added navigation_goal_reasoning and is_navigation_goal_required fields
  • Added data_extraction_goal_reasoning and is_data_extraction_goal_required fields
  • Made navigation_goal and data_extraction_goal conditionally required based on the new reasoning fields
  • Removed redundant instruction about goal requirements

Generated with ❤️ by ellipsis.dev

<!-- ELLIPSIS_HIDDEN -->

| 🚀 | This description was created by [Ellipsis](https://www.ellipsis.dev) for commit 7a59079e9fc6e76aabc149d1170ad77432e24034  |
|--------|--------|

### Summary:
This PR updates the task generation template to conditionally require `navigation_goal` and `data_extraction_goal`, enhancing task clarity and directive for the AI agent.

**Key points**:
- Updated `skyvern/forge/prompts/skyvern/generate-task.j2`
- Made `navigation_goal` and `data_extraction_goal` conditionally required based on new reasoning fields
- Removed redundant instruction about goal requirements

----
Generated with ❤️ by [ellipsis.dev](https://www.ellipsis.dev)

<!-- ELLIPSIS_HIDDEN -->
@ykeremy ykeremy added the sync label Jun 14, 2024
Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Incremental review on c73f830 in 2 minutes and 14 seconds

More details
  • Looked at 26 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 0 drafted comments based on config settings.

Workflow ID: wflow_f0mMSQNKHj8JzNCH


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

is_data_extraction_goal_required: bool. This is a required field. Based on data_extraction_goal_reasoning, whether the data extraction goal is required to achieve the goal.
data_extraction_goal: str. This is an optional field. The value should be a string that we can use as an input to a Large Language Modal. It needs to tell the agent the goal in terms of extracting data. It needs to be a single goal.
navigation_payload: json. This is an optional field. The value should be JSON. Use this field if there is any information for the agent to be able to complete the task such as values that can help fill a form, parameters for queries and so on.
extracted_information_schema: json. This is an optional field. The exact schema of the data to be extracted. This field should be provided if there is a data_extraction_goal. This should be a JSON object that defines the schema of the data to be extracted.

At least one of navigation goal or data extraction goal should be provided. The agent can't proceed without any goals.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement 'At least one of navigation goal or data extraction goal should be provided' might be contradictory with the new fields is_navigation_goal_required and is_data_extraction_goal_required. If both are set to false based on the reasoning fields, this line could be misleading. Consider revising or removing this line to align with the new conditional requirements.

@msalihaltun msalihaltun merged commit 265cb99 into main Jun 14, 2024
2 checks passed
@msalihaltun msalihaltun deleted the salih/task-generation-prompt-update branch June 14, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants