@paulkinlan/llm-starter v0.0.3

LLM Starter Kit

The LLM Starter Kit is a collection of Breadboard nodes that are helpful for building LLM-based (Generative AI) applications.

Installing

LLM Starter Kit requires Node version >=v19.0.0. To install:

npm install @google-labs/llm-starter

Node Types

Here are all node handlers that are included in the LLM Starter Kit.

The promptTemplate node

Use this node to populate simple handlebar-style templates. A reuired input is template, which is a string that contains the template prompt template. The template can contain zero or more placeholders that will be replaced with values from inputs. Specify placeholders as {{inputName}} in the template. The placeholders in the template must match the inputs wired into this node. The node will replace all placeholders with values from the input property bag and pass the result along as the prompt output property.

Example:

If we send the following inputs to promptTemplate:

{
  "template": "Question: {{question}}\nThought: {{thought}}",
  "question": "How old is planet Earth?",
  "thought": "I wonder how old planet Earth is?"
}

We will get this output:

{
  "prompt": "Question: How old is planet Earth?\nThought: I wonder how old planet Earth is?"
}

Inputs:

• template - required property
• zero or more inputs that will be used to replace placeholders in the template.

Outputs:

• prompts a string that contains the result of replacing placeholders in the template with values from the inputs.

Implementation:

• src/nodes/prompt-template.ts

The append node

Use this node to accumulate local state, like context in a prompt.

The node looks for property called accumulator in its input. All other properties are appended to this property, and returned as accumulator output property.

The way the properties are appended depends on the type of the accumulator input property.

If the accumulator property is "string-ey" (that is, it's a string, number, boolean, bigint, null or undefined), the properties will be appended as strings, formatted as {{property_name}}: {{proprety_value}} and joined with "\n".

If the accumulator property is an array, the properties will be appended as array items, formatted as {{property_name}}: {{proprety_value}},

Otherwise, the accumulator property will be treated as an object and the properties will be added as properties on this object.

Example

If we send the append node an input of Question with the value of How old is planet Earth? and the accumulator value of \n:

{
  "accumulator": "\n",
  "Question": "How old is planet Earth?"
}

We will see the following output:

{
  "accumulator": "\n\nQuestion: How old is planet Earth?"
}

If we send the node an input of Question with the value of How old is planet Earth? and the accumulator value of []:

{
  "accumulator": [],
  "Question": "How old is planet Earth?"
}

We will get the output:

{
  "accumulator": ["Question: How old is planet Earth?"]
}

If we send the node an input of Question with the value of How old is planet Earth? and the accumulator value of {}:

{
  "accumulator": {},
  "Question": "How old is planet Earth?"
}

We'll get the output of:

{
  "accumulator": {
    "Question": "How old is planet Earth?"
  }
}

Implementation:

• src/nodes/append.ts

The runJavascript node

Use this node to execute JavaScript code. The node recognizes a required code input property, which is a string that contains the code to be executed. It also recognizes a name input property, which is a string that specifies the name of the function that will be invoked to execute the code. If not supplied, the run function name will be used.

All other input properties will be passed as arguments to the function.

The code is executed in a new V8 context in Node or a Web Worker in the browser, which means that it cannot access any variables or functions from the outside.

The node will pass the result of the execution as the result output property.

Example:

If we send the following inputs to runJavascript:

{
  "code": "function run() { return 1 + 1; }"
}

We will get this output:

{
  "result": 2
}

If we send:

{
  "code": "function run({ what }) { return `hello ${what}`; }",
  "what": "world"
}

We will get:

{
  "result": "hello world"
}

Inputs:

• code - required, must contain the code to execute
• name - optional, must contain the name of the function to invoke (default: run)
• zero or more inputs that will be passed as arguments to the function.

Outputs:

• result - the result of the execution

Implementation:

• src/nodes/run-javascript.ts

The secrets node

Use this node to access secrets, such as API keys or other valuable bits of information that you might not want to store in the graph itself. The node takes in an array of strings named keys, matches the process environment values, and returns them as outputs. This enables connecting edges from environment variables.

Example:

Use this node to pass the PALM_KEY environment variable to the text-completion node. The input:

{
  "keys": ["PALM_KEY"]
}

Will produce this output:

{
  "PALM_KEY": "<value of the API key from the environment>"
}

Inputs:

• keys - required, must contain an array of strings that represent the keys to look up in the environment. If not supplied, empty output is returned.

Outputs:

• one output for each key that was found in the environment.

Implementation:

• src/nodes/secrets.ts

The generateText node

This is a PaLM API text completion node. This node is probably the main reason this starter kit exists. To produce useful output, the node needs an PALM_KEY input and the text input.

Example:

Given this input:

{
  "PALM_KEY": "<your API key>",
  "text": "How old is planet Earth?"
}

The node will produce this output:

{
  "completion": "It is about 4.5 billion years old."
}

Inputs:

• PALM_KEY required, must contain the Google Cloud Platform API key for the project has the "Generative Language API" API enabled.
• text required, sent as the prompt for the completion.
• stopSequences optional array of strings. These will be passed as the stop sequences to the completion API.

Outputs:

• completion - result of the PaLM API text completion.

The urlTemplate node

Use this node to safely construct URLs. It's similar in spirit to the promptTemplate node, except it ensures that the handlebar parameters are properly encoded as part of the URL.

Example:

If we send the following inputs to urlTemplate:

{
  "template": "https://example.com?question={{question}}",
  "question": "How old is planet Earth?"
}

We will get this output:

{
  "url": "https://example.com?question=How%20old%20is%20planet%20Earth%3F"
}

Inputs:

• template -- required, a template for the URL. It can contain zero or more placeholders that will be replaced with values from the input property bag. Specify placeholders as {{propertyName}} in the template.
• zero or more inputs that will be used to replace placeholders in the template.

Outputs:

• url a string that contains the result of replacing placeholders in the template with values from the inputs.

Implementation:

• src/nodes/url-template.ts

The fetch node

Use this node to fetch data from the Internet. Practically, this is a wrapper around fetch

Example:

If we would like to fetch data from https://example.com, we would send the following inputs to fetch:

{
  "url": "https://example.com"
}

And receive this output:

{
  "response": "<response from https://example.com>"
}

Inputs:

• url -- required, URL to fetch. For now, this node can only make a GET request.
• headers -- object (optional), a set of headers to be passed to the request.
• raw boolean (optional), specifies whether or not to return raw text (true) or parse the response as JSON (false). The default value is false.

Outputs:

• response -- the response from the server. If raw is false, the response will be parsed as JSON.

Implementation:

• src/nodes/fetch.ts

The jsonata node

Use this node to execute JSONata expressions. JSONata is a versatile JSON query language.

Example:

If we send the following inputs to jsonata:

{
  "expression": "$join(items.snippet, '\n')",
  "json": {
    "items": [
      {
        "snippet": "Question: How old is planet Earth?"
      },
      {
        "snippet": "Thought: I wonder how old planet Earth is?"
      }
    ]
  }
}

We will get this output:

{
  "result": "Question: How old is planet Earth?\nThought: I wonder how old planet Earth is?"
}

Inputs:

• expression -- required, a string that contains the JSONata expression to be executed.
• json -- a required JSON object that will be used as the context for the expression.
• raw -- an optional boolean that specifies whether the result of the expression should be passed as-is (true), or it should be passed as the result output property (false, default).

Outputs:

• result -- the result of the expression, unless raw is true. In the latter case, the result is passed as-is.

Implementation:

• src/nodes/jsonata.ts

The xmlToJson node

Use this node to convert XML to JSON. Most nodes in the starter kit are designed to work with JSON, so this node is useful when you have XML data.

This nodes takes one required xml property, which it treats as XML and converts to it to JSON as the json output property. The format of JSON follows the alt-json convention that is described in https://developers.google.com/gdata/docs/json.

Example:

If we send the following inputs to xml-to-json:

{
  "xml": "<root><question>How old is planet Earth?</question><thought>I wonder how old planet Earth is?</thought></root>"
}

We will get this output:

{
  "json": {
    "root": {
      "question": { "$t": "How old is planet Earth?" },
      "thought": { "$t": "I wonder how old planet Earth is?" }
    }
  }
}

Inputs:

• xml - required, must contain a string that represents XML.

Outputs:

• json - the result of converting XML to JSON.

Implementation:

• src/nodes/xml-to-json.ts