Choose a suitable skill and try it on your work
Start with a need, compare the source, instructions, and compatibility, then test on a small task.
Let's understand the idea
Gathering dozens of skills doesn't mean your work improved. First write the task you repeat and the part that falls short. Then find a skill with actual instructions and examples, a clear source, and compatibility with your environment.
Read files, licenses, and requirements before installing. If scripts or permissions are involved, understand their role. Don't run them just because the name fits. Test a copy on a small, nonsensitive sample. Compare the result with your criteria and previous attempt.
Tools for this workflow
Choose from what's available to you. You can use these prompts with several tools. What they can carry out depends on supported features and files.
See tool details and uses in the Tools library →Examples to expand the idea
An HR employee wants a skill for writing job descriptions. They find several ready-made skills and open each instruction file to understand its approach. They test the closest two on the same role and choose the one that asks about responsibilities and level before starting.
Customize an open-source skill
Keep the license and creator attribution. Adapt criteria and examples while documenting your version.
Finding skills for Diploma students
Recommend based on the learner's level, environment, and required task, rather than a generic best-of list.
An exploration bonus
The skills guide includes the full Skill Discovery Studio file, with a test prompt and criteria for reviewing results.
Steps from start to delivery
Open any step by its heading. Each explains what to do, why, and what to check before continuing.
1Describe the needA need you can test.Details
A broad label brings irrelevant recommendations.
What should I do?
- Define the task, format, environment, and problem.
- Write a sample and a criterion to compare against.
2Find original filesCandidates with sources and actual instructions.Details
A marketing post doesn't replace reading the instructions.
What should I do?
- Ask for the repository or package link, creator, and license.
- Distinguish a link whose files you opened from an unexamined recommendation.
3Check compatibility and requirementsClear requirements without universal compatibility promises.Details
A skill from a different environment may need adapting.
What should I do?
- Read the inputs, outputs, resources, and dependencies.
- Understand code execution or account access before installing. Exclude unknown sources.
4Test and compareA comparison you can review.Details
A small result is stronger evidence than an impressive description.
What should I do?
- Test the same task with suitable inputs and no sensitive data.
- Review the source, format, gaps, and style. Record the difference.
5Keep what helpsA skill you know why you use and how to review.Details
A few useful tools are easier to maintain.
What should I do?
- Choose a skill for a specific reason and keep its link and version.
- Customize examples and criteria if needed, respect the license, and retest.
Prompts for your work
Open a prompt and fill in your details. Empty fields remain visible so you don't forget them.
Find skills for my needsOpen it to copy or tailor the prompt
Prepare the listed inputs and start with the prompt in an available tool. Open the output and review it against your work.
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
Why is the prompt written this way?
Choosing and building requires testing on your own work, rather than an attractive skill name or a description promising guaranteed results.
Evaluate a candidate on an exampleOpen it to copy or tailor the prompt
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
Did the result serve your original goal?
Return to the inputs and sources, and open the output where you'll use it. Check these points before relying on it.
- Are the source and license clear?
- Was compatibility checked?
- Did testing demonstrate a specific benefit?
If there's a problem, name the unsuitable part, show an example, and request a specific edit.