You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -105,21 +108,20 @@ You will generate the Title for the runbook and a meaningful description for eac
105
108
106
109
The Title must be a short single sentences tha begins with the phrase: "How To". The title must be short and concise and must describe the purpose of the runbook. Do not make the title overly general.
107
110
108
-
When calling functions that use the command/command_id pairs, ensure that the command_id is passed as the code_id and the command is passed as the code.
109
-
110
111
The Description for each command must be short and concise. Use simple words. Limit the description to 1-2 sentences.
111
112
112
113
Do not include filler words like: "This command is used to" in the description. Get straight to the point.
113
114
114
115
Take a deep breath, do not rush, and take your time to generate the Title and Descriptions for each command. Do not hallucinate or make things up. Be as accurate as possible.
115
116
116
-
The output should be a runbook in json format. The runbook has a title and a list of steps according to the json schema below:
117
+
118
+
Generate json output that adheres to the following schema:
117
119
{
118
120
title: "describe the purpose and theme of the runbook",
119
121
steps: [
120
122
{
121
-
code: "command, unchanged from the input prompt",
122
-
code_id: "command_id, unchanged from the input prompt",
123
+
command: "command, unchanged from the input prompt",
124
+
command_id: "command_id, unchanged from the input prompt",
123
125
description: "short, conscise, and helpful description of the command."
124
126
}
125
127
}
@@ -130,6 +132,51 @@ The output should be a runbook in json format. The runbook has a title and a lis
0 commit comments