Slim/sql (#31)

* setup sql agent graph

* Refactor the sub-graph prompt injection

* Move prompts over to examples

* Update graph for sql agent

Author: slimslenderslacks

graphs/prompts/journals/2024_09_03.md

@@ -46,8 +46,9 @@
 		- if the project being analyzed is located somewhere other than $PWD then the `--host-dir` will need to be updated.
 - [[Running the Prompt Engine]]
 - [[Authoring Prompts]]
-- ---
-  id:: 66d7f3ff-8769-40b3-b6b5-fc4fceea879e
+- id:: 66d7f3ff-8769-40b3-b6b5-fc4fceea879e
+  ```
+  ---
   extractors:
     - name: linguist
       image: vonwig/go-linguist:latest
@@ -84,4 +85,5 @@
   This project contains {{language}} code.
   {{/linguist}}
   
-  Can you find any language specific project files and list them?
+  Can you find any language specific project files and list them?
+  ```

graphs/prompts/pages/Authoring Prompts.md

@@ -4,4 +4,6 @@ A prompt file can also contain metadata about how to generate and run the prompt
 {{embed ((66d7f3ff-8769-40b3-b6b5-fc4fceea879e)) }}
 The example above defines a lot of metadata.  A prompt file might also be very simple.
 {{embed ((66d8a396-9268-4917-882f-da4c52b7b5dd)) }}
-Use the [prompt engine]([[Running the Prompt Engine]]) to run this prompt file against an LLM.
+Use the [prompt engine]([[Running the Prompt Engine]]) to run this prompt file against an LLM.
+- ## Prompt Metadata
+-

graphs/prompts/pages/interpolation.md

@@ -0,0 +1,37 @@
+- When defining tools in prompt metadata, users can _interpolate_ tool parameters into the `commands` section of a container definition.  For example, in the following definition of a sqlite tool, the `database` and `sql` parameters from the tool definition will be used to create the container.
+  ```
+    - name: sqlite
+      description: run the sqlite command
+      parameters:
+        type: object
+        properties:
+          database:
+            type: string
+            description: the path to the database
+          sql:
+            type: string
+            description: the sql statement to run
+      container:
+        image: vonwig/sqlite:latest
+        command:
+          - "{{database}}"
+          - "{{sql|safe}}"
+  ```
+- You can also splice array parameters into the command definition using the `into` filter keyword:
+  ```
+    - name: docker
+      description: run any docker command with arguments
+      parameters:
+        type: object
+        properties:
+          args:
+            type: array
+            items:
+              type: string
+            description: arguments to pass to the docker CLI
+      container:
+        image: docker:cli
+        command:
+          - "{{args|into}}"
+  ```
+  In this example, the array of strings passed to the `args` parameter of the function will be spliced into the `command` parameter of the container definition.