Find facts, relevant examples, and prior wording in work history to support a writing draft. Use source evidence to separate completed work from plans and opinions, verify quotations, and remove sensitive details from public drafts unless disclosure is authorized.
Recover facts and relevant examples from work history to support a requested piece of writing.
Review the instructions the agent will receive before you install.
Resolve the writing topic, audience, format, and period. Use screenpipe-api to find relevant outcomes, examples, and the user's own prior phrasing. Select only evidence needed for this piece; unrelated private activity is out of scope.
Build the draft around supported facts and distinguish completed work, plans, opinions, and uncertain recollections. Verify quoted wording against the source. Preserve the user's stated voice preferences without copying other people's private messages as the user's words.
Remove customer identifiers, credentials, and internal metrics from public drafts unless their disclosure is authorized. Present the draft in chat unless another destination was requested. Writing a draft does not authorize sending, posting, scheduling, or inventing results.
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.
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.
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.
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.