mirror of
https://github.com/hwchase17/langchain
synced 2024-11-10 01:10:59 +00:00
ed58eeb9c5
Moved the following modules to new package langchain-community in a backwards compatible fashion: ``` mv langchain/langchain/adapters community/langchain_community mv langchain/langchain/callbacks community/langchain_community/callbacks mv langchain/langchain/chat_loaders community/langchain_community mv langchain/langchain/chat_models community/langchain_community mv langchain/langchain/document_loaders community/langchain_community mv langchain/langchain/docstore community/langchain_community mv langchain/langchain/document_transformers community/langchain_community mv langchain/langchain/embeddings community/langchain_community mv langchain/langchain/graphs community/langchain_community mv langchain/langchain/llms community/langchain_community mv langchain/langchain/memory/chat_message_histories community/langchain_community mv langchain/langchain/retrievers community/langchain_community mv langchain/langchain/storage community/langchain_community mv langchain/langchain/tools community/langchain_community mv langchain/langchain/utilities community/langchain_community mv langchain/langchain/vectorstores community/langchain_community mv langchain/langchain/agents/agent_toolkits community/langchain_community mv langchain/langchain/cache.py community/langchain_community mv langchain/langchain/adapters community/langchain_community mv langchain/langchain/callbacks community/langchain_community/callbacks mv langchain/langchain/chat_loaders community/langchain_community mv langchain/langchain/chat_models community/langchain_community mv langchain/langchain/document_loaders community/langchain_community mv langchain/langchain/docstore community/langchain_community mv langchain/langchain/document_transformers community/langchain_community mv langchain/langchain/embeddings community/langchain_community mv langchain/langchain/graphs community/langchain_community mv langchain/langchain/llms community/langchain_community mv langchain/langchain/memory/chat_message_histories community/langchain_community mv langchain/langchain/retrievers community/langchain_community mv langchain/langchain/storage community/langchain_community mv langchain/langchain/tools community/langchain_community mv langchain/langchain/utilities community/langchain_community mv langchain/langchain/vectorstores community/langchain_community mv langchain/langchain/agents/agent_toolkits community/langchain_community mv langchain/langchain/cache.py community/langchain_community ``` Moved the following to core ``` mv langchain/langchain/utils/json_schema.py core/langchain_core/utils mv langchain/langchain/utils/html.py core/langchain_core/utils mv langchain/langchain/utils/strings.py core/langchain_core/utils cat langchain/langchain/utils/env.py >> core/langchain_core/utils/env.py rm langchain/langchain/utils/env.py ``` See .scripts/community_split/script_integrations.sh for all changes
132 lines
8.1 KiB
Python
132 lines
8.1 KiB
Python
# flake8: noqa
|
|
CLICKUP_TASK_CREATE_PROMPT = """
|
|
This tool is a wrapper around clickup's create_task API, useful when you need to create a CLICKUP task.
|
|
The input to this tool is a dictionary specifying the fields of the CLICKUP task, and will be passed into clickup's CLICKUP `create_task` function.
|
|
Only add fields described by the user.
|
|
Use the following mapping in order to map the user's priority to the clickup priority: {{
|
|
Urgent = 1,
|
|
High = 2,
|
|
Normal = 3,
|
|
Low = 4,
|
|
}}. If the user passes in "urgent" replace the priority value as 1.
|
|
|
|
Here are a few task descriptions and corresponding input examples:
|
|
Task: create a task called "Daily report"
|
|
Example Input: {{"name": "Daily report"}}
|
|
Task: Make an open task called "ClickUp toolkit refactor" with description "Refactor the clickup toolkit to use dataclasses for parsing", with status "open"
|
|
Example Input: {{"name": "ClickUp toolkit refactor", "description": "Refactor the clickup toolkit to use dataclasses for parsing", "status": "Open"}}
|
|
Task: create a task with priority 3 called "New Task Name" with description "New Task Description", with status "open"
|
|
Example Input: {{"name": "New Task Name", "description": "New Task Description", "status": "Open", "priority": 3}}
|
|
Task: Add a task called "Bob's task" and assign it to Bob (user id: 81928627)
|
|
Example Input: {{"name": "Bob's task", "description": "Task for Bob", "assignees": [81928627]}}
|
|
"""
|
|
|
|
CLICKUP_LIST_CREATE_PROMPT = """
|
|
This tool is a wrapper around clickup's create_list API, useful when you need to create a CLICKUP list.
|
|
The input to this tool is a dictionary specifying the fields of a clickup list, and will be passed to clickup's create_list function.
|
|
Only add fields described by the user.
|
|
Use the following mapping in order to map the user's priority to the clickup priority: {{
|
|
Urgent = 1,
|
|
High = 2,
|
|
Normal = 3,
|
|
Low = 4,
|
|
}}. If the user passes in "urgent" replace the priority value as 1.
|
|
|
|
Here are a few list descriptions and corresponding input examples:
|
|
Description: make a list with name "General List"
|
|
Example Input: {{"name": "General List"}}
|
|
Description: add a new list ("TODOs") with low priority
|
|
Example Input: {{"name": "General List", "priority": 4}}
|
|
Description: create a list with name "List name", content "List content", priority 2, and status "red"
|
|
Example Input: {{"name": "List name", "content": "List content", "priority": 2, "status": "red"}}
|
|
"""
|
|
|
|
CLICKUP_FOLDER_CREATE_PROMPT = """
|
|
This tool is a wrapper around clickup's create_folder API, useful when you need to create a CLICKUP folder.
|
|
The input to this tool is a dictionary specifying the fields of a clickup folder, and will be passed to clickup's create_folder function.
|
|
For example, to create a folder with name "Folder name" you would pass in the following dictionary:
|
|
{{
|
|
"name": "Folder name",
|
|
}}
|
|
"""
|
|
|
|
CLICKUP_GET_TASK_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
Do NOT use to get a task specific attribute. Use get task attribute instead.
|
|
useful when you need to get a specific task for the user. Given the task id you want to create a request similar to the following dictionary:
|
|
payload = {{"task_id": "86a0t44tq"}}
|
|
"""
|
|
|
|
CLICKUP_GET_TASK_ATTRIBUTE_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to get a specific attribute from a task. Given the task id and desired attribute create a request similar to the following dictionary:
|
|
payload = {{"task_id": "<task_id_to_update>", "attribute_name": "<attribute_name_to_update>"}}
|
|
|
|
Here are some example queries their corresponding payloads:
|
|
Get the name of task 23jn23kjn -> {{"task_id": "23jn23kjn", "attribute_name": "name"}}
|
|
What is the priority of task 86a0t44tq? -> {{"task_id": "86a0t44tq", "attribute_name": "priority"}}
|
|
Output the description of task sdc9ds9jc -> {{"task_id": "sdc9ds9jc", "attribute_name": "description"}}
|
|
Who is assigned to task bgjfnbfg0 -> {{"task_id": "bgjfnbfg0", "attribute_name": "assignee"}}
|
|
Which is the status of task kjnsdcjc? -> {{"task_id": "kjnsdcjc", "attribute_name": "description"}}
|
|
How long is the time estimate of task sjncsd999? -> {{"task_id": "sjncsd999", "attribute_name": "time_estimate"}}
|
|
Is task jnsd98sd archived?-> {{"task_id": "jnsd98sd", "attribute_name": "archive"}}
|
|
"""
|
|
|
|
CLICKUP_GET_ALL_TEAMS_PROMPT = """
|
|
This tool is a wrapper around clickup's API, useful when you need to get all teams that the user is a part of.
|
|
To get a list of all the teams there is no necessary request parameters.
|
|
"""
|
|
|
|
CLICKUP_GET_LIST_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to get a specific list for the user. Given the list id you want to create a request similar to the following dictionary:
|
|
payload = {{"list_id": "901300608424"}}
|
|
"""
|
|
|
|
CLICKUP_GET_FOLDERS_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to get a specific folder for the user. Given the user's workspace id you want to create a request similar to the following dictionary:
|
|
payload = {{"folder_id": "90130119692"}}
|
|
"""
|
|
|
|
CLICKUP_GET_SPACES_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to get all the spaces available to a user. Given the user's workspace id you want to create a request similar to the following dictionary:
|
|
payload = {{"team_id": "90130119692"}}
|
|
"""
|
|
|
|
CLICKUP_GET_SPACES_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to get all the spaces available to a user. Given the user's workspace id you want to create a request similar to the following dictionary:
|
|
payload = {{"team_id": "90130119692"}}
|
|
"""
|
|
|
|
CLICKUP_UPDATE_TASK_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to update a specific attribute of a task. Given the task id, desired attribute to change and the new value you want to create a request similar to the following dictionary:
|
|
payload = {{"task_id": "<task_id_to_update>", "attribute_name": "<attribute_name_to_update>", "value": "<value_to_update_to>"}}
|
|
|
|
Here are some example queries their corresponding payloads:
|
|
Change the name of task 23jn23kjn to new task name -> {{"task_id": "23jn23kjn", "attribute_name": "name", "value": "new task name"}}
|
|
Update the priority of task 86a0t44tq to 1 -> {{"task_id": "86a0t44tq", "attribute_name": "priority", "value": 1}}
|
|
Re-write the description of task sdc9ds9jc to 'a new task description' -> {{"task_id": "sdc9ds9jc", "attribute_name": "description", "value": "a new task description"}}
|
|
Forward the status of task kjnsdcjc to done -> {{"task_id": "kjnsdcjc", "attribute_name": "description", "status": "done"}}
|
|
Increase the time estimate of task sjncsd999 to 3h -> {{"task_id": "sjncsd999", "attribute_name": "time_estimate", "value": 8000}}
|
|
Archive task jnsd98sd -> {{"task_id": "jnsd98sd", "attribute_name": "archive", "value": true}}
|
|
*IMPORTANT*: Pay attention to the exact syntax above and the correct use of quotes.
|
|
For changing priority and time estimates, we expect integers (int).
|
|
For name, description and status we expect strings (str).
|
|
For archive, we expect a boolean (bool).
|
|
"""
|
|
|
|
CLICKUP_UPDATE_TASK_ASSIGNEE_PROMPT = """
|
|
This tool is a wrapper around clickup's API,
|
|
useful when you need to update the assignees of a task. Given the task id, the operation add or remove (rem), and the list of user ids. You want to create a request similar to the following dictionary:
|
|
payload = {{"task_id": "<task_id_to_update>", "operation": "<operation, (add or rem)>", "users": [<user_id_1>, <user_id_2>]}}
|
|
|
|
Here are some example queries their corresponding payloads:
|
|
Add 81928627 and 3987234 as assignees to task 21hw21jn -> {{"task_id": "21hw21jn", "operation": "add", "users": [81928627, 3987234]}}
|
|
Remove 67823487 as assignee from task jin34ji4 -> {{"task_id": "jin34ji4", "operation": "rem", "users": [67823487]}}
|
|
*IMPORTANT*: Users id should always be ints.
|
|
"""
|