What do you explain again every time?
You open a new conversation and explain who you write for, the report format you like, the information that must appear, and mistakes you want to avoid repeating. If the same kind of work recurs, keep the context and process somewhere easy to return to.
But not every prompt needs a skill. Clear instructions are enough to rewrite a message once. For a client, subject, or ongoing project, you need to organize conversations and files. When recurring work has inputs, steps, and standards, a skill is worth trying.
We will use a hypothetical example: after every team meeting, you prepare a summary, required tasks, who is responsible, and what remains open. The aim is a consistent review and presentation method while changing the information for each meeting.
A project collects context, and a skill saves the process
Project: An organized space for work-related conversations, files, and instructions, depending on the product. For example, a project for your team with role definitions, past weekly reports, and current materials.
Skill: A package of instructions and resources for a recurring task or process. In the meeting example: read the transcript, separate discussion from what the team agreed, extract tasks, flag gaps, and check the result against the source. Another project can use the same process with different information.
Memory: Preferences and information the assistant may retain, depending on settings. Do not rely on it instead of an updated source or task instructions. Connections: A way to access information or take an action in an app, depending on tools and permissions. A skill can guide their use but cannot create permissions that do not exist.
Choose an example close to your work
Writing content in your style
Inputs: an idea, audience, information, and approved samples. Key instructions: understand the content angle, consult style samples, ask about important gaps, and after drafting, review meaning, facts, and voice separately. If the skill is only called “Content writer,” without a defined type of work or standard, the result may still be generic.
Meeting summary and follow-up tasks
Inputs: a transcript or notes and meeting date. Instructions: tie each task to supporting words and do not assign an owner or deadline yourself. For example, “We need someone to review the presentation” does not assign it to a specific person. The output should be a summary, clear tasks, and points needing confirmation, without automatically sending them to the team.
A lesson explanation and activities
Inputs: approved content, student level, and lesson goal. Instructions: prepare an explanation and example, then an activity testing the goal with the reason for the answer. Check question difficulty and accuracy. Changing lessons means more than changing a title; the process must adapt to the idea and students.
Data report or dashboard
Inputs: a spreadsheet, column definitions, period, and the question the data will answer. Instructions: check missing values, duplicates, and units; explain calculations; and compare totals before designing. If “new customer” is undefined, ask before calculating it. An attractive chart does not prove the numbers are right.
A skill can combine related work, but you do not need to put every specialty and output into one skill.
Start with a process you tried and a result you reviewed
Prepare a meeting summary yourself or with the assistant, and review what worked and what needed changing. For example: the summary was clear, but treated a suggestion as an agreed task. Instead of saying “Be accurate,” turn the correction into an instruction: distinguish a suggestion for discussion from a clear assignment, and place unresolved items under “Needs confirmation.”
Choose a good output example and explain why it works. You can add a poor example with the reason for rejecting it. Let the reference aid understanding, with an explicit instruction not to copy names or tasks from the old meeting into new work.
You can try explanation and writing prompts with any of these. File reading, execution, and connections depend on what is available in your account.
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
A skill contains instructions and resources when needed
In the open Agent Skills format, a skill is a folder with a main file called SKILL.md. It contains a name and description followed by instructions. You can add references, templates, or scripts if the task needs them. Not every skill needs code.
The name explains the function, and the description explains what it does and when to use it. “An excellent work assistant” is broad. “Turns meeting notes into a summary, tasks, and points needing confirmation” has a clearer scope. The instructions then explain the method, limits, and delivery checks.
Put lengthy details in organized references and explain when the assistant should consult each file. A table of contents and clear links help, but do not guarantee it will read every word.
If you move it to another product, check that the format is supported and the required tools and files are available. The file format may be compatible, but installation, activation, and permissions are not necessarily identical. Downloading a skill is one thing. Running it successfully is something you need to test.
Test the skill on more than one type of request
Start with test materials you are allowed to use. In the meeting example, we want to know whether the method remains useful with a complete or incomplete source, and whether the skill recognizes its limits instead of taking on any work.
- A suitable request: notes with clear tasks, owners, and deadlines. Did it transfer them correctly without additions?
- An incomplete request: an assignment without an owner or deadline. Did it flag the gap instead of inventing the details?
- An out-of-scope request: ask it to design a video. Did it explain that this falls outside meeting summarization instead of forcing the summary template onto it?
- Different wording: ask for the same result in different natural wording and see whether the appropriate skill was actually used.
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
If a case fails, identify the cause: was the skill not opened? Were the instructions ambiguous? Was the source incomplete? Was the required tool unavailable? Each cause needs a different fix, not a longer list of prohibitions.
Update what changes and keep an accepted example
Keep a copy of the instructions and the result you reviewed. If the report format changes, update the reference instead of leaving two conflicting templates. If you add a rule, test the failing case alongside a working case so you do not fix one part and break another.
A skill does not improve itself automatically just because you corrected an output in chat. Save the change in the place you rely on, then test the new version. Moving a file or installing an extension does not mean it is available on every account or device.
If you use a ready-made skill from someone else, understand its function, requirements, and source. Review the files and tools it runs, and adapt it to your style and work. Do not add sensitive work files just because the original example used the same type.
Two free skills: try them on real work you have
We prepared two complete skills you can download. Choose one based on what you need now: finding and examining an existing skill, or building your own workflow. Both include searching for what exists. The discovery skill focuses on comparison and selection, while the builder continues through designing, testing, and improving a package.
Find a suitable skill and understand why to choose it
Tell it your work, the result you need, and the platform you will use it on. It can search for existing skills, examine available instructions and resources, compare candidates against your work, and explain requirements, adaptations, and how to obtain the package.
See a trial example and review the result
For example, you are a teacher preparing activities that involve thinking and trying, not just recall questions. Specify the grade level, lesson, and activity format instead of asking generally for “the best education skills.”
Find a skill that helps me prepare science activities for middle school students. I want the activity to start with a student attempt, followed by hints and a separate teacher answer. I will use it on the platform I specify. Examine the files of serious candidates, compare the best options you actually inspected, and explain what I need to customize. Ask me about details that would affect the search. Do not install anything automatically.
What should you check? Did it open the instructions or rely on a description? Are the differences between options clear? Are resources, compatibility information, and licensing available? If search or skill testing is unavailable, it should explain the comparison's limits.
Turn your method into a complete skill you can develop
Start with a repeated task, or sources, experience, and sample results. The skill helps you understand the requirements, review existing options, and build or revise instructions, resources, and test cases. It can also repair a weak skill instead of starting over.
See a trial example and review the result
Return to the meeting summary example in the guide. Upload a template without private data, a summary you reviewed and liked, and an example showing what is unacceptable.
Build a skill that turns a meeting transcript into a summary and follow-up points. My reviewed output template is attached. Distinguish what was explicitly said from your suggestions, and do not invent an owner or deadline if none was mentioned. Start by understanding the differences that will affect the work, and ask me about important gaps. Prepare the full package, with a normal test, a test with missing information, and an out-of-scope request. Explain what you actually tested and what still needs testing.
What should you check? Open the result and see whether it actually followed your method. Are gaps clear? Do the package files exist and connect properly? Written test cases are different from running them successfully.
Downloaded the file? Learn how to use the package
- Keep the complete ZIP file. Inside is the skill folder, containing SKILL.md and its resources. Do not just copy the first file and leave the rest.
- Choose a platform that supports skills and follow its available installation method. Import methods and skill availability differ by app and account. A file attachment box does not necessarily install a skill.
- In ChatGPT, standalone skills have an installation route in the desktop app, and skills may also be available through plugins. If the option does not appear, check what your app supports before assuming the package was installed.
- After adding it, request the task clearly and try a small example. If installation is unavailable, you can attach the files in an environment that can read them and ask it to use them in the conversation. That is use within the conversation, not permanent installation.
A research skill needs a search capability, and building a downloadable file needs an environment that allows file creation. The package preserves a workflow. It does not add capabilities or a subscription your account lacks.
Try one skill before collecting dozens
Choose a repeated task, write a simple definition of an acceptable result, and prepare two test examples. Make a small version, test it, and change one thing for a reason you identified. If the instructions do not improve your work or add useless steps, simplify them or use a clear prompt instead.
You can later use the skill within a larger workflow: reading meeting notes from a connected app and preparing a summary file. But gathering the source, applying the method, saving the file, and sending it are different actions, each requiring support and clear instructions. Start with the help you need, and review the output before expanding execution.