34 skills (repositories by screenpipe) · sorted by popularity
Turn selected research conversations or notes into themes supported by evidence and counterexamples. Distinguish observed behavior from preferences and hypotheses, assess confidence, and suggest a small next experiment with an observable measure of success.
Turn selected Screenpipe activity into a concise recap for a defined audience. Summarize outcomes from recorded evidence, then review the draft to remove identifying details, private links, sensitive amounts, and unnecessary personal information before sharing.
Find past discussions across existing screenpipe, Codex, Claude, Cursor, and Gemini CLI chats by title, workspace, or message text. With explicit authorization, send follow-up work to a specific supported chat; Gemini CLI supports search only.
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.
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.
Reconstruct a customer's history from recorded meetings, support exchanges, and prior work. Check available current conversations and records, then summarize needs, commitments, unresolved issues, ownership, and next steps to inform a response draft.
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.
Prepare a short brief for an upcoming meeting by confirming the event and participants, reviewing relevant Screenpipe history, and summarizing prior commitments, unresolved decisions, likely purpose, and two useful questions with supporting links.
Build a daily or weekly worklog from recorded activity and checked outcomes. Separate plans, observed work, and verified completion, then summarize useful results and unfinished tasks with source links and clearly marked gaps or estimates.
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.