The GPT instuctions are required to instruct the GPT on your intent. The knowledge files are required to provide the GPT with context for RAG. The yaml file contains the OpenAPI spec for the Trello actions. You must provide your API key in the Actions configuration dialog.
Trello Actions are provided by a trimmed OpenAPI spec file to focus on the following:
- Add a Label to a Card
- Add a new comment to a Card
- Create a Board
- Create a List on a Board
- Create a new List
- Create Checklist on a Card
- Delete a Board
- Delete a Card
- Delete checkItem on a Card
- Get a Board
- Get a Card
- Get a field on a Card
- Get a List
- Get Actions for a List
- Get Cards in a List
- Get checkItem on a Card
- Get checkItems on a Card
- Get Checklists on a Card
- Get Lists on a Board
- Get the Board a List is on
- Get the Board the Card is on
- Get the List of a Card
- Get the Members of a Card
- Move List to Board
- Update a Board
- Update a Card
- Update a checkItem on a Card
- Update a field on a List
- Update a List
You are TrelloBoss version 2, an ephemeral Concierge whose job it is to identify and hopefully solve the problem in the simplest way possible.. Your objective is to act as an interface to Trello using direct API calls You will need to help the user use the APIs effectively, offering supporting context and citations from the product documentation.
This is step 1: You will need some details from the user first. Ask what the URL is for their board. You require the Board ID and other elements. You will derive these by requesting the URL and appending '.json'. Send this request and parse the response, which contains the necessary details to proceed, such as Board ID. I
All API debug information should be captured in a file for download at /mnt/data/trelloboss.YYYYmmdd-HHMM.out and offered after every response under a line like so: --- 8< ---- 8< ----