fadeleke/prompt-to-signature
1
3
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

(no commit message)

Browse Source
This commit is contained in:
Farouk Adeleke
2025-11-04 13:29:58 -05:00
parent 87433012c0
commit 22d47004cd
6 changed files with 143 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
agent.json
View File

@@ -1,5 +1,5 @@
{
"signature_generator.generator.predict": {
"signature_generator.generator": {
"traces": [],
"train": [],
"demos": [],
@@ -10,17 +10,13 @@
"prefix": "Prompt:",
"description": "Natural language description of the desired functionality."
},
{
"prefix": "Reasoning: Let's think step by step in order to",
"description": "${reasoning}"
},
{
"prefix": "Task Description:",
"description": "Clear description of what the signature aims to accomplish."
},
{
"prefix": "Signature Fields:",
"description": "List of input and output fields for the signature.\n\nCRITICAL RULES:\n1. If the prompt describes a structured output with multiple nested fields (e.g., medical records, user profiles, complex forms), you MUST use type='pydantic' with a full PydanticModelSchema\n2. NEVER use type='str' with a description like 'JSON string containing...' for complex outputs\n3. For Pydantic models: define ALL nested fields properly in the schema with correct types\n4. Simple outputs (single values) can use basic types like str, int, bool\n5. Use Literal types for enumerated values (e.g., severity levels, status codes)\n\nExamples:\n- BAD: structured_output: str = \"A JSON containing patient data...\"\n- GOOD: medical_record: MedicalRecord (with full PydanticModelSchema defining all nested fields)"
"description": "List of input and output fields for the signature.\n\n CRITICAL RULES:\n 1. If the prompt describes a structured output with multiple nested fields (e.g., medical records, user profiles, complex forms), you MUST use type='pydantic' with a full PydanticModelSchema\n 2. NEVER use type='str' with a description like 'JSON string containing...' for complex outputs\n 3. For Pydantic models: define ALL nested fields properly in the schema with correct types\n 4. Simple outputs (single values) can use basic types like str, int, bool\n 5. Use Literal types for enumerated values (e.g., severity levels, status codes)\n\n Examples:\n - BAD: structured_output: str = \"A JSON containing patient data...\"\n - GOOD: medical_record: MedicalRecord (with full PydanticModelSchema defining all nested fields)\n \n "
},
{
"prefix": "Signature Name:",
@@ -29,7 +25,7 @@
]
},
"lm": {
"model": "gpt-5-2025-08-07",
"model": "openai/gpt-4o",
"model_type": "chat",
"cache": true,
"num_retries": 3,
@@ -37,7 +33,7 @@
"launch_kwargs": {},
"train_kwargs": {},
"temperature": 1.0,
"max_completion_tokens": 16000
"max_tokens": 16000
}
},
"metadata": {