본문으로 건너뛰기
cccskills
무료GitHub에 공개

screenpipe-chats

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Search what was said in existing screenpipe, Codex, Claude, Cursor, and Gemini CLI chats, then continue or steer one exact chat when the user explicitly asks. Use for requests about finding another agent conversation, recalling what an agent said, or sending work to one.

설치 방법 보기

이럴 때 유용합니다

  • Finding a conversation using a remembered phrase
  • Recalling what an agent previously said
  • Sending follow-up work to a specific chat
  • Redirecting a running screenpipe chat

포함된 파일(1)

  • SKILL.md2.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

existing agent chats

screenpipe exposes search_chats and send_to_chat as agent tools. They use a private core capability passed into the current chat process; do not scrape transcript folders, guess runtime commands, or call a localhost app route.

search

  1. Call search_chats with a short title, message, workspace, or exact id. The query also matches the transcript, so a phrase said mid-conversation finds the chat even when the title never mentions it. Omit the query to list recent chats. Filter sources only when the user named a runtime.
  2. Show enough title, source, preview, and workspace information to distinguish ambiguous results.
  3. Treat the returned source and id as the address. Never derive an id from a title or reuse a stale result after the target disappears.
  4. Read the warnings array. Transcript reading is bounded to the most recent chats per runtime, so report that older chats were not searched instead of claiming a phrase was never said.

Searching is read-only and does not require confirmation.

send

  1. Require an exact result from search_chats in the current turn.
  2. Require explicit user authorization for that target and message. A draft, suggestion, or request to inspect chats is not permission to send.
  3. Call send_to_chat with the exact source, id, message, and confirmed: true.
  4. Use mode: queue by default. Use mode: steer only when the user asked to redirect a currently running screenpipe chat.
  5. Report the returned status and exact target. Do not retry an uncertain or failed send until the result is reconciled.

Gemini CLI chats are search-only: Gemini has no non-interactive resume, so send_to_chat rejects them instead of opening an interactive session. Say so and offer to summarize what the chat already contains.

The tool refuses self-sends, guessed ids, dormant-chat steering, oversized messages, unsendable sources, and sends without confirmation. Cross-chat sending is disabled in unattended scheduled runs.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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/screenpipe2.2만2026년 10월 18일 업데이트

release

무료

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/screenpipe2.2만2026년 10월 18일 업데이트

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/screenpipe2.2만2026년 10월 18일 업데이트

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/screenpipe2.2만2026년 10월 18일 업데이트

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/screenpipe2.2만2026년 10월 18일 업데이트

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/screenpipe2.2만2026년 10월 18일 업데이트

screenpipe의 스킬 모두 보기

이 스킬의 문제 신고