skill-recorder

Least-privilege permissions

• Limit recording scope: Only record the specific application or browser tab needed for the task, not your entire desktop. Close or minimize email, chat, and other apps before recording.
• Use a dedicated account: Create a separate Windows user account with minimal permissions just for recording sessions; avoid using your main admin account.
• Restrict skill deployment: When publishing generated skills to Autopilot environments, deploy them to test groups first and require approval before they can run on production systems or access shared resources.
• Review skill permissions before use: Before deploying any generated automation, verify it only has access to the specific systems or data it needs—reject skills that request broad file access or cloud permissions.

Network isolation

• Record offline when possible: Disconnect from the internet or use an isolated network during sensitive recording sessions to prevent accidental transmission of recorded data.
• Audit SDK connections: Verify that the Copilot SDK only sends recorded sessions to authorized Microsoft services; disable telemetry or analytics features if your organization's policy requires it.
• Control where skills execute: Ensure generated automations only run on designated machines or environments where data sensitivity is acceptable; never allow them to run on systems handling regulated data without approval.

Monitoring

• Log all recordings: Enable detailed audit logs showing when sessions are recorded, what was captured, and who accessed the generated skills.
• Track skill executions: Monitor when and where deployed automations run, what actions they perform, and which data they access.
• Review generated intents: Before finalizing a skill, have a human reviewer check the AI-reconstructed intent and steps to confirm no sensitive information was extracted or misunderstood.

Red flags to watch for

• Passwords, API keys, or tokens visible on-screen: If you see credentials during recording, stop immediately and re-record after clearing sensitive data from view.
• Skills requesting unexpected access: If a generated skill asks for permission to access email, file storage, or systems beyond what you recorded, reject it—this may indicate prompt injection or misconfiguration.
• Unexplained delays or network traffic during recording: Unusual lag or outbound connections during a session may signal unintended data transmission; check your firewall logs.
• Skills behaving differently than your recorded steps: If a deployed automation performs unintended actions or accesses systems you didn't demonstrate, immediately disable it and investigate before re-deploying.