Use a slightly smaller model. Reduce concurreny. Be more clear in the prompts

2026-04-02 20:10:57 +01:00
parent 7e586fe17d
commit 10f2644408
6 changed files with 10 additions and 21 deletions
@@ -17,6 +17,10 @@ Include a url to a source for your trigger event (not a web search, a specific u
 Include the date that the event happened ("March 2022" for exmaple)

 Use a JSON format with each entry containing "Event,ReasoningWhyRelevant,SearchQuery,Url,Date".
+Return ONLY valid JSON.
+Do not include explanations.
+Do not wrap in markdown.
+Do not label where the json is using colons

 Multiple tool invocations should be requested at once, if applicable.
 Use your abilities to look between the lines and produce some insightful analysis, thinking both short and long term.
@@ -26,4 +30,6 @@ Events will be reordered as part of processing, each statement must stand alone
 The preceeding messages act as examples of previous responses to potentially ficitonal events and scores given.
 Analysis should only be completed for proposed events that would graner >0.7 points

+Since URLs change frequently, use tools to retreive up to date informaiton everytime, provided examples or existing knowledge will be wrong or out of date.
+
 Lets go through it step by step