Skip to content
cccskills
FreePublished on GitHub

screenpipe-decision-history

Trace a decision through recorded discussions and later revisions. Build a dated account of proposals, confirmed choices, rejected alternatives, and remaining questions, keeping suggestions separate from final decisions and showing disagreements between sources.

OriginalShow the original description

Trace why a decision was made, which alternatives were considered, and what changed later.

See how to install

Good for

  • Find the recorded reasons behind a decision
  • Review alternatives that were rejected
  • Trace later changes to a decision
  • Compare conflicting accounts of a decision

Files included (1)

  • SKILL.md890 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

decision history

Resolve the decision, project, and date range. Use screenpipe-api to find the original discussion and later revisions, expanding around matching timestamps rather than reading unrelated history.

Build a short sequence of proposals, decisions, and superseding decisions. Attribute a decision only when the source shows agreement or an authorized owner's explicit choice. Keep a suggestion, someone's recollection, and a final decision distinct.

Explain the recorded rationale, rejected alternatives, constraints, and unresolved questions with dated source pointers. If sources disagree, show the disagreement and which evidence is newer. Do not infer consensus from silence or replace a missing rationale with your own.

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 18, 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 18, 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 18, 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 18, 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 18, 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 18, 2026

See all skills by screenpipe

Report a problem with this skill