Explain why each step exists
A useful demonstration includes the decision behind each action. Describe the source, the expected result, and the exceptions a person handles. Screens alone cannot explain which business decisions require judgment.
Make a written skill
Translate the demonstration into a skill with inputs, steps, and an output standard. Use the skill editor and the supporting files your workspace offers. Recording-to-automation availability depends on the product features enabled for your workspace.
Check the proposed process
Read the resulting instruction before treating it as team policy. Remove accidental private details from examples. Keep external writes and sensitive decisions behind an explicit review point.
Try a different example
Test the written process on another representative input. A skill should express the repeatable logic, not memorize one demonstration. Record where the process needs a human decision.
Open the relevant screen
Use Teach Spinrun a workflow in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.