|
| 1 | +analyze_document_task: |
| 2 | + description: > |
| 3 | + Analyze all provided documents in the directory and extract key information, including: |
| 4 | + - Main topics and themes |
| 5 | + - Key entities (people, places, organizations) |
| 6 | + - Important dates and events |
| 7 | + - Relationships between entities |
| 8 | + - Any specific requirements or actions needed |
| 9 | +
|
| 10 | + Provide concise and clear markdown that segments summaries of each document. |
| 11 | + Make sure to provide the **exact** file path when summarizing each document. |
| 12 | + expected_output: > |
| 13 | + A concise GFM markdown analysis of each document including all key information. |
| 14 | + This is to be used as input for the collection creation task. |
| 15 | + output_file: "agent/analysis.md" |
| 16 | + |
| 17 | +create_collection_task: |
| 18 | + description: > |
| 19 | + Create a collection based on the provided analysis from the analyzed document task. |
| 20 | +
|
| 21 | + Ensure that the instructions are comprehensive and based off of the analysis provided. |
| 22 | + You are only allowed to create **table** categories, any other category is not allowed. |
| 23 | +
|
| 24 | + - Tables must have bullet point list of what each column should contain |
| 25 | + - All instructions should be clear concise bullet points |
| 26 | + expected_output: > |
| 27 | + Provide a concise GFM markdown summary of what the collection is about. |
| 28 | + After running the createCollection tool, make sure to explicitly state the collection id. |
| 29 | + output_file: "agent/collection.md" |
| 30 | + |
| 31 | +upload_document_task: |
| 32 | + description: > |
| 33 | + After a collection has been created. Upload all documents to the collection just created. |
| 34 | +
|
| 35 | + To upload a document you are required to do the following: |
| 36 | + - You are required to provide the **exact** path to the tool for the "file" field. |
| 37 | + - You are required to provide the "name" field with an extension. |
| 38 | + - Additional instructions are NOT needed for each file uploaded and should be an empty string. |
| 39 | + expected_output: > |
| 40 | + A concise GFM markdown list confirmation of successful upload including: |
| 41 | + - List of uploaded documents |
| 42 | + - Any warnings or issues encountered |
| 43 | + - Summary of the upload process |
| 44 | + output_file: "agent/upload_summary.md" |
| 45 | + |
| 46 | +research_task: |
| 47 | + description: > |
| 48 | + Analyze the collection and then conduct research and generate a comprehensive GFM markdown report. |
| 49 | +
|
| 50 | + Identify the types of questions to ask using the file provided. As well as to retrieve the collection id. |
| 51 | +
|
| 52 | + Use the searchCollectionSimple and promptCollectionSimple tool calls to research the collection. |
| 53 | + The prompt field should be used to ask questions about the collection. |
| 54 | +
|
| 55 | + The report should be well-structured and include: |
| 56 | + - Executive summary of key findings |
| 57 | + - Main topics and themes from the documents |
| 58 | + - Important data points and statistics |
| 59 | + - Key insights and recommendations |
| 60 | + - Any relevant quotes or references |
| 61 | +
|
| 62 | + Format the report using GitHub Flavored Markdown with proper: |
| 63 | + - Headers and subheaders |
| 64 | + - Bullet points and numbered lists |
| 65 | + - Tables for data comparison |
| 66 | + - Code blocks for any technical details |
| 67 | + - Links to sources where applicable |
| 68 | +
|
| 69 | + Keep the language clear, concise, and professional. |
| 70 | + expected_output: > |
| 71 | + A well-formatted GFM markdown report that provides a comprehensive overview |
| 72 | + of the research findings, ready for sharing and collaboration. |
| 73 | + output_file: "agent/research_report.md" |
| 74 | + |
0 commit comments