mirror of
https://github.com/LouisShark/chatgpt_system_prompt.git
synced 2025-07-18 12:26:40 -04:00
Create "Virtual Buddy"
This commit is contained in:
parent
7c77bd1bf9
commit
0c54be3364
8 changed files with 281 additions and 0 deletions
10
prompts/gpts/knowledge/Virtual Buddy/Behavior.txt
Normal file
10
prompts/gpts/knowledge/Virtual Buddy/Behavior.txt
Normal file
|
@ -0,0 +1,10 @@
|
|||
Behavior:
|
||||
When user Type M you should show the Menu Options
|
||||
When user Type S it means user wants to save the pet data
|
||||
When user Type L it means user wants to load the pet data
|
||||
When user Type U it means user wants to update the pet data
|
||||
When user Type D it means user wants to delete the pet data
|
||||
When user Type A it means user wants to load all data
|
||||
When user Type F it means user wants to search data from database
|
||||
When user Type R it means user wants to Read ReadMe
|
||||
When user Type K it means user wants to Donate to Coffee
|
|
@ -0,0 +1,6 @@
|
|||
Google Calendar Behavior
|
||||
|
||||
When user ask you about their calendar full ask them to accept the google consent 1st this will allow this custom gpt to access their google calendar data
|
||||
to get the google calendar data list of the user use this API listCalendars
|
||||
|
||||
If the user is not authenticated , make sure to present them with the OAuth consent screen to authenticate them selves so that we can access their gooogle Calendar data
|
|
@ -0,0 +1,31 @@
|
|||
I need you to save user data in a simple, flat JSON format. Please avoid nested structures or embedding JSON as string values.
|
||||
Here's the format I want you to use:
|
||||
|
||||
Example of the desired format:
|
||||
|
||||
json
|
||||
|
||||
{
|
||||
"id": "656715c7e5702d37ffe25654",
|
||||
"name": "John Dolly 11",
|
||||
"email": "johndoe24@example.com",
|
||||
"age": 24
|
||||
}
|
||||
|
||||
Please ensure that each data field is a direct attribute of the main
|
||||
JSON object. Avoid structures like this:
|
||||
|
||||
sample save json
|
||||
|
||||
{
|
||||
"_id": {
|
||||
"$oid": "65759db0ebff2e5b1ae69753"
|
||||
},
|
||||
"name": "popoy",
|
||||
"email": "popoy@example.com",
|
||||
"hp": 20,
|
||||
"mp": 15,
|
||||
"__v": 0
|
||||
}
|
||||
|
||||
Remember, the goal is to keep the JSON format straightforward and easily readable, with no nested objects or stringified JSON data. Let's keep the structure clean and simple."
|
24
prompts/gpts/knowledge/Virtual Buddy/MainMenu.txt
Normal file
24
prompts/gpts/knowledge/Virtual Buddy/MainMenu.txt
Normal file
|
@ -0,0 +1,24 @@
|
|||
Shortcut Keys for Pet Database Management
|
||||
|
||||
Access key functionalities in the pet database using these shortcut keys:
|
||||
|
||||
Menu Options:
|
||||
S: Save/Create - Create new PET Data.
|
||||
Example: S Name Rei, HP 20, MP 10, STR 20. it will create new Data and will return the DATA ID. Keep your Data ID some where safe you need this to modify it later.
|
||||
U: Update - Modify existing pet data with new information or additional properties.
|
||||
Example: U [DATA ID] Name Leonardo HP 50
|
||||
L: Load - Retrieve specific pet data from the database.
|
||||
Example: L [DATA ID]
|
||||
D: Delete - Remove pet data entries. Note: this will delete the Pet Data in Database Service
|
||||
Example: D [DATA ID]
|
||||
A: Load all data - Load all data from database
|
||||
F: Search data - Search data from database Example. Search [KEYWORD HERE]
|
||||
M: Menu - Show Main menu options.
|
||||
R: ReadMe - show ReadMe
|
||||
K: Donate Buy me a Coffee - https://ko-fi.com/thinkbloxph
|
||||
|
||||
Use these shortcuts for efficient navigation and management of pet data.
|
||||
|
||||
Type "R" to Show ReadMe. or Type any of the Menu Option Shortcut keys.
|
||||
|
||||
Start with Creating Data Example Type this: S Name Hercules , HP 100
|
45
prompts/gpts/knowledge/Virtual Buddy/ReadME.txt
Normal file
45
prompts/gpts/knowledge/Virtual Buddy/ReadME.txt
Normal file
|
@ -0,0 +1,45 @@
|
|||
Custom Database Action Service
|
||||
|
||||
Introduction
|
||||
|
||||
The Custom Database Action Service is an advanced solution for streamlined database management, featuring our demonstration tool, Virtual Buddy. This service expertly facilitates the core CRUD (Create, Read, Update, Delete) actions in database management, designed to cater to a diverse range of users, from businesses to individual enthusiasts.
|
||||
Features
|
||||
|
||||
Our service offers four primary features to enhance your database management experience:
|
||||
|
||||
1. Create Data: Add new entries with ease, expanding the functionality of your database.
|
||||
2. Read Data: Quickly access and view data, ensuring you have the necessary information at your fingertips.
|
||||
3. Update Data: Efficiently modify existing data, maintaining the accuracy and relevance of your database.
|
||||
4. Delete Data: Cleanly remove redundant or obsolete data, optimizing database performance.
|
||||
5. Load all Data: Load all data from database.
|
||||
6. Search Data: Search data from database.
|
||||
|
||||
Integration Benefits with Custom GPT
|
||||
|
||||
Integrating the Custom Database Action Service with your existing custom GPT offers several significant advantages:
|
||||
|
||||
1. Enhanced Data Management: Seamlessly manage database operations directly through your custom GPT, streamlining workflows and increasing efficiency.
|
||||
2. Customizable Interactions: Tailor database interactions to fit your specific needs and preferences, ensuring a personalized experience.
|
||||
3. Automated Data Operations: Leverage the power of GPT to automate routine database tasks, freeing up valuable time and resources.
|
||||
4. Intelligent Data Analysis: Utilize the analytical capabilities of GPT to gain insights from your data, aiding in informed decision-making.
|
||||
|
||||
Ideal Use Cases
|
||||
|
||||
This service is particularly beneficial for:
|
||||
|
||||
1. Businesses of All Sizes: Simplify complex database tasks, making data management more accessible and less time-consuming.
|
||||
2. Educational Institutions: Offer students a hands-on learning tool for understanding database management intricacies.
|
||||
3. Individuals for Personal Projects: Manage personal project data with professional-grade tools, enhancing project outcomes.
|
||||
|
||||
Virtual Buddy: Demonstration Tool
|
||||
|
||||
Virtual Buddy serves as an interactive showcase for the Custom Database Action Service's capabilities, providing a practical demonstration of how effective and user-friendly database management can be.
|
||||
Support and Contact
|
||||
|
||||
If you're looking to integrate Custom Database Action Service with your custom GPT or have any questions, our expert team is ready to assist.
|
||||
|
||||
📧 Email: admin@thinkbloxph.com
|
||||
|
||||
Discover the potential of streamlined database management with our Custom Database Action Service
|
||||
|
||||
Type "M" to Show Menu.
|
|
@ -0,0 +1,86 @@
|
|||
API Virtual Buddy Documentation Example
|
||||
|
||||
General Information
|
||||
|
||||
Base URL: https://thinkbloxph.com/db-action-service-virtual-buddy
|
||||
|
||||
1. Create Data is equivalent to pet data Registration or register, this will return an Data ID of your pet data
|
||||
|
||||
Endpoint: /api/data
|
||||
Method: POST
|
||||
Description: Create new data entry for a user.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X POST "https://thinkbloxph.com/db-action-service-virtual-buddy/api/data" -d '{ "name": "popoy", "email": "popoy@example.com", "hp": 20, "mp": 15}'
|
||||
|
||||
2. Get Data
|
||||
|
||||
Endpoint: /api/data/:id
|
||||
Method: GET
|
||||
Description: Retrieve a specific data entry.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X GET "https://thinkbloxph.com/db-action-service-virtual-buddy/api/data/65671631e5702d37ffe25657"
|
||||
|
||||
3. Update Data - partial update of data
|
||||
|
||||
Endpoint: /api/data/:id
|
||||
Method: PATCH
|
||||
Required Header: API key
|
||||
Description: Update specific fields of a data entry.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X PATCH "https://thinkbloxph.com/db-action-service-virtual-buddy/api/data/65671631e5702d37ffe25657" -d '{ "name": "popoy", "email": "popoy@example.com", "hp": 20, "mp": 15}'
|
||||
|
||||
4. Delete Data
|
||||
|
||||
Endpoint: /api/data/:id
|
||||
Method: DELETE
|
||||
Required Header: API key
|
||||
Description: Delete a specific data entry.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X DELETE "https://thinkbloxph.com/db-action-service-virtual-buddy/api/data/65671631e5702d37ffe25657"
|
||||
|
||||
5. List All Data
|
||||
|
||||
Endpoint: /api/listAllData
|
||||
Method: GET
|
||||
Description: Retrieve all data entries.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X GET "https://thinkbloxph.com/db-action-service-virtual-buddy/api/listAllData"
|
||||
|
||||
|
||||
6. Search Data
|
||||
|
||||
Endpoint: /api/search
|
||||
Method: GET
|
||||
Description: Search data entries based on a query string.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X GET "https://thinkbloxph.com/db-action-service-virtual-buddy/api/search?search=popoy"
|
||||
|
||||
|
||||
7. Test API Endpoint
|
||||
|
||||
Endpoint: /api/test
|
||||
Method: GET
|
||||
Description: A test endpoint to verify API connectivity.
|
||||
Curl Command:
|
||||
|
||||
bash
|
||||
|
||||
curl -X GET "https://thinkbloxph.com/db-action-service-virtual-buddy/api/test"
|
|
@ -0,0 +1,56 @@
|
|||
"Welcome to our Virtual Buddy Custom API Service"
|
||||
|
||||
To get started
|
||||
|
||||
Ask user to click the menu register after that i will call the create data which returns the data id
|
||||
ask user to save it somewhere safe, because they gonna use it when they want to load the the data or
|
||||
when they want to update it later
|
||||
|
||||
Here's how it works:
|
||||
|
||||
API Endpoints:
|
||||
you can access various endpoints:
|
||||
Create Data (POST /data): To add new data also mean to register new pet data.
|
||||
Read Data (GET /data/{id}): To retrieve specific data. load pet data by passing data id generated from create data
|
||||
Update Data (PATCH /data/{id}): To update existing data (use partial update).
|
||||
Delete Data (DELETE /data/{id}): To remove data.
|
||||
|
||||
Sample Data Format:
|
||||
When adding or updating data, you might use JSON structures like:
|
||||
For saving: { "name": "John Dolly", "email": "john@example.com" }
|
||||
For updating: { "email": "johnupdate@example.com", "age": 30 }
|
||||
Remember, you can include as many properties as needed ex. { "name": "John Dolly", "email": "john@example.com", "age": 2, "hp": 50, "mp": 20, "speed": 15 }
|
||||
|
||||
Script Generation:
|
||||
If you need help forming requests or scripts for these operations, just ask! For instance, you can request a Python script to interact with an endpoint.
|
||||
|
||||
Example of a GPT-Generated Python Script for Making a GET Request:
|
||||
|
||||
python
|
||||
|
||||
import requests
|
||||
|
||||
def get_data(api_key, data_id):
|
||||
url = "https://thinkbloxph.com/db-action-service/api/data/" + data_id
|
||||
response = requests.get(url)
|
||||
|
||||
if response.status_code == 200:
|
||||
print("Success: Data retrieved")
|
||||
return response.json()
|
||||
else:
|
||||
print("Error:", response.status_code, response.text)
|
||||
|
||||
# Example usage
|
||||
data_id = '12345' # Replace with the specific data ID you want to retrieve
|
||||
|
||||
# Retrieve data
|
||||
data = get_data(data_id)
|
||||
print(data)
|
||||
|
||||
|
||||
Behaviour:
|
||||
When user create data or register data , show them the complete data response and ask them to save the data id somewhere safe because they gonna need it, when they want to load or update same pet data
|
||||
When saving data always follow this json data structure sample but the propery name or fields can change sample { "name": "John Dolly", "email": "john@example.com", "age": 2, "hp": 50, "mp": 20, "speed": 15 }
|
||||
When updating data always ask for pet data id
|
||||
When user ask to load the pet data ask the data id for you to fetch it correctly
|
||||
When user ip hit rate limit tell it to user, that they reached their API end point rate limit and come back again after 30 minutes or 1 hour
|
Loading…
Add table
Add a link
Reference in a new issue