When to use this workflow
Use this workflow when you know the repeated task but do not yet know which available skill fits it. Start with a concrete outcome and your agent host. A list of popular skills is less useful than a procedure that matches the tools, files, and review requirements of your actual work.
A worked example
For a token-audit need, compare candidates by their required inputs, supported environment, editing behavior, and output evidence. Read the source instructions before installing. Prefer a bounded first test on one component so you can judge whether the skill finds real issues and respects project conventions.
Decisions and common mistakes
A familiar name is not proof of quality or compatibility. Watch for missing prerequisites, unsupported integrations, vague claims, and overlapping versions. If the host cannot load the skill or access the required source, record the gap instead of interpreting an improvised answer as a successful run.
What to hand off
Keep the selected source, installation scope, and acceptance example with the team’s onboarding notes. Review updates as changes to a working process. If no candidate fits, use the skill-creation guide to capture a procedure you have already performed successfully.
Set up and try the skill
1. Start with one concrete task
Bring: One repeated task, your agent host, and the tools or files that task requires.
First task: Compare candidate skill sources, supported hosts, dependencies, and maintenance before installing.
Choose a small task for “find an agent skill.” Provide the relevant file, screen, or brief and define what a useful result should contain. Keep the original version available for comparison.
2. Install and verify the instructions
Run this command from the project where you want the skill available. Follow the installer’s host selection, then confirm the skill appears in that host. The command is the installation method documented by the TDP repository.
npx skills add thedesignproject/agent-skills -s find-skillsRead the full skill instructions for prerequisites and supported tools. Installing a skill does not automatically connect Figma or grant access to external tools.
3. Apply it with your project context
Use the starter request below with the relevant inputs attached or referenced. Confirm that the host loaded the intended skill; a matching name alone is not evidence that its instructions were applied.
4. Review the result
Read the selected instructions and run a small representative task to verify that the host can use them.
Compare the output with the task’s acceptance criteria. Check factual claims, unsupported assumptions, and any changes to the interface. For code or design changes, review real states and behavior before treating the result as finished.
5. Keep what works
Save approved outputs with their source and ownership. Note which instructions helped, where the result needed correction, and what must be checked next time. Use the workflow below to connect this task to its next step.
A starter request
Adapt this example to your files, audience, and requirements.
Find a maintained skill for this repeated task. Compare its scope, dependencies, source, and installation requirements before recommending one.
Completion checklist
- The inputs and intended result are explicit.
- Required files and tools are available in the chosen host.
- The result has been reviewed against the actual task.
- Limitations and follow-up checks are recorded.