When to use this workflow
Use this resource when a skill exists but its instructions leave room for inconsistent interpretation. Collect the actual failures: missing context, ambiguous decisions, wrong activation, or unreviewable output. Editing the prose without identifying the failure can make the document clearer while leaving the workflow unchanged.
A worked example
For a component-documentation skill, compare the requested contract with a generated result. Did it omit invalid combinations, infer unsupported states, or fail to identify sources? Add explicit decision rules for those gaps and a compact example that demonstrates the expected distinction between facts and recommendations.
Decisions and common mistakes
Avoid adding every past exception to the main procedure. Keep the core sequence readable and link specialist cases where the host can retrieve them. Remove duplicated project rules that already have a maintained source, and make missing-input behavior explicit.
What to hand off
Run the revised skill in a fresh session on both familiar and unfamiliar inputs. Record regressions as well as improvements. Share the change with a concrete explanation of the failure it addresses so teammates know when the updated procedure matters.
Set up and try the skill
1. Start with one concrete task
Bring: An existing skill, its intended audience, and cases where its instructions were ambiguous.
First task: Turn ambiguity into explicit decisions and exercise the revised workflow on representative cases.
Choose a small task for “write and verify shared skills.” 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 writing-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
Have a fresh session follow the instructions; record missing context and regressions before sharing.
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.
Review this shared skill for ambiguous instructions. Add representative success and failure cases, test the workflow, and document unresolved limitations.
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.