PDigger
1. Record the steps you want to reuse
Keep the relevant app visible while you perform the task, including before and after states. A screenshot of a finished result may not establish how you got there. Imported video does not establish keystrokes or unseen steps.
2. Describe the procedure
Open Skills. Ask for a specific workflow and date, or start from Ask about this on relevant evidence. Choose Build procedure. The example below is a prompt ready to submit, not a generated procedure.
3. Review before using it
A general macOS question can produce a Suggested guide. Its steps are labelled as general guidance, not actions proven by your recordings. A demonstrated procedure still requires original evidence for its steps.
Read each step and expected result, follow its evidence links, and review uncertainties. PDigger may reject a procedure when the recording cannot support its steps. Narrow the request or record the missing work; do not treat a plausible instruction as an observed action.
Saved procedures appear in Library. Choose Open procedure to read or edit one. Saving an edit does not create new recorded evidence.
4. Export or install
Use the procedure’s Markdown or JSON export buttons to save a file. The available Install into… buttons prepare it for the named assistant. Review the destination and any result message. PDigger does not execute the procedure for you.
5. Share a problem with useful details
If generation fails, choose Details & report…. Add what you tried, review the details, then copy the report or open an email draft. Nothing is emailed automatically.
