Turn verified corrections and repeated workflows into reusable local methods. Check existing skills first, then capture when to use a method, its steps, how to validate results, and when to stop.
Turn a verified correction or repeated workflow into a reusable local learning.
Review the instructions the agent will receive before you install.
Verify the original request, correction, and result. Treat assistant success claims as claims until checked. Search existing skills before proposing a new one. Save a concise reusable method, not a transcript, private identity, credential, or temporary task state. Include when to use it, steps, validation, and a stop condition. Use skill_manage when available. Read first, preserve user/imported skills, and use the current hash for an agent-owned patch. Creating a skill requires the user’s explicit request or an enabled task whose stated scope authorizes it. No new permissions, outbound actions, or recursive agents. A no-change result is valid. Assess the next relevant use before claiming improvement.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.
Create charts, dashboards, scorecards, and styled summaries as standalone HTML reports for the screenpipe viewer. Keep styles, scripts, and images inside the file so the report renders in a sandbox with no network access.
Search Screenpipe recordings, screen text, audio transcripts, and synced-device history through its local API. Use the evidence to review activity, find meeting details, and inspect saved workflows, including recorded steps that can inform automation.
Use Screenpipe’s local REST API, an interface for programmatic requests, to search screen and meeting history, review app activity and active time, retrieve synced-device records, export recordings, and rerun audio transcription.
Turn a recorded software failure into a draft bug report with timestamps, reproduction steps, expected and actual behavior, and relevant evidence. Separate visible symptoms from possible causes and remove sensitive details from shareable evidence.