Skip to content
cccskills
FreePublished on GitHub

screenpipe-research-synthesis

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.

OriginalShow the original description

Synthesize repeated themes from selected research conversations or notes.

See how to install

Good for

  • Finding recurring themes across research interviews
  • Comparing evidence, counterexamples, and confidence
  • Planning a small experiment to test findings
  • Preparing research findings for sharing

Files included (1)

  • SKILL.md719 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

research synthesis

Confirm the source set and research question. Extract observations with source pointers before grouping them. A repeated claim in one conversation is one source, not multiple participants. For each theme, state the supporting evidence, counterexamples, confidence, and practical implication. Separate observed behavior from preferences and hypotheses. Do not force consensus or invent prevalence. Recommend a small next experiment with an observable success criterion. Use role labels in shareable output and avoid identifying quotes unless explicitly requested.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

  • Test Windows-specific capture and permission behavior
  • Investigate compiler, process, or service issues
  • Preserve desktop video and logs for a pull request
screenpipe/screenpipe22KUpdated Oct 19, 2026

release

FreeSummary

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.

  • Preparing a desktop app release
  • Checking whether Rust changes require a CLI release
  • Updating MCP versions and checking publication
screenpipe/screenpipe22KUpdated Oct 19, 2026

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.

  • Create a visual report of daily work time
  • Present key metrics in a dashboard
  • Summarize results with charts and scorecards
screenpipe/screenpipe22KUpdated Oct 19, 2026

screenpipe-api

FreeSummary

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.

  • Reviewing daily app use and active screen time
  • Finding decisions in recorded meetings
  • Searching history from a synced device
screenpipe/screenpipe22KUpdated Oct 19, 2026

screenpipe-api

FreeSummary

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.

  • Review activity from a specific day or time range
  • Find recorded meeting remarks and screen text
  • Search work history on another synced device
screenpipe/screenpipe22KUpdated Oct 19, 2026

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.

  • Drafting a bug report from recorded activity
  • Recovering steps taken before and after a failure
  • Comparing expected behavior with observed results
screenpipe/screenpipe22KUpdated Oct 19, 2026

See all skills by screenpipe

Report a problem with this skill