Introduction
With these new AI capabilities, CoPilot is going to be a huge assistance especially working on mundane tasks. An example could be,
- Analyzing Excel files and creating visualizations
- Understanding the summary of the meeting
- Getting the main intent of the document
- Much more.
The possibilities here are endless.
GCSE Framework
If we want to get the correct answer or information from the CoPilot, you need to talk to it. The art of talking, aka ‘Prompt Engineering’. This is going to be crucial to get the required and relevant information. Below is the framework that is taken from the MSFT Tech Community.
![GCSE Framework]()
It is required to include the right ingredients to make a recipe right. It's the same as with the CoPilot. You must follow the proper guidelines to get meaningful content.
Let’s try to write a prompt to have a presentation script from PowerPoint. I am writing this based on the above framework.
- Goal: Create an Exciting and compelling script for a 4-minute presentation.
Note: You can refer to the file by using /
- Context: This is to win a deal from the client.
- Source: Defining the source by providing the link to your file.
- Expectation: keep it natural so that the client can understand it easily.
Final Prompt
Create an exciting and compelling script for a 4 4-minute presentation from the / <Link to File>. This is to win a deal from the client. Keep it natural so that the client can understand easily.
![Final Prompt]()
Note: If the file is placed in our organization or personal one drive, it is easy to reference from Copilot.
Below is the final draft in Word I got with the help of CoPilot.
![CoPilot]()
Prompt History
Please note once you click on ‘Keep it’, then your prompt is gone, and there is no way to retrieve it. You need to always save your prompt in a separate text file before executing it with CoPilot. Hopefully, MSFT will release the history of prompts in upcoming releases.
![Prompt History]()
If you used the prompt in the CoPilot menu from the ribbon, then you could refer to the prompt.
![CoPilot menu]()
If you want to refer to the prompt while working on your document, don’t click on ‘Keep it’ unless you are completely satisfied with it. You can click on the edit button, to refine your existing prompt.
![Existing prompt]()
Currently, prompt history is scoped to document instances. When you open a new document you cannot see your previous prompts.
Points to note
- Always save the prompt before executing with CoPilot.
- You can always edit the existing prompt as long as you do not click on the 'Keep it' button from the small modal prompt.
- Only click on Keep it if you are satisfied with CoPilot-generated content.
Conclusion
Thus, in this article, we have seen how to work with a copilot to get a talking script from a presentation using GCSE Framework, aka ‘Prompt Engineering’. Also, we have come to know the current limitations of prompt history.
References