Screenpipe Workflow Discovery
Identify repeated work from recorded activity or starred examples and assess which steps could be automated.
Install
npx skills add screenpipe/screenpipe --skill screenpipe-workflow-discoverygit clone --depth 1 https://github.com/screenpipe/screenpipe.git /tmp/screenpipe
mkdir -p ~/.claude/skills
cp -r /tmp/screenpipe/crates/screenpipe-core/assets/skills/screenpipe-workflow-discovery ~/.claude/skills/screenpipe-workflow-discoveryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# workflow discovery Resolve the work area and review period. Use screenpipe-api to find multiple distinct occurrences of a candidate workflow. Describe the trigger, inputs, observed steps, outputs, exceptions, and human decisions with source pointers. Count independent occurrences, not repeated frames or repeated discussion of one occurrence. Separate observed steps from inferred steps. If timing matters, use authoritative active time where available and label missing coverage; frame counts are not effort. Assess a small automation candidate by its available tools, permissions, reversible boundaries, and observable completion criterion. Identify the decisions that still require a person. Do not claim time savings without a baseline or create a schedule, integration, or external action merely from discovering a pattern. For starred work, retrieve captured evidence directly with screenpipe-api's starred-only search and a bounded time range. For broader workflow review, use the activity summary's starred intervals to prioritize existing evidence; retrieve missing steps only when needed. A star indicates intent, not repetition, completion or time savings. Do not add interval history to standing prompts.
Details
- Skill name
screenpipe-workflow-discovery- Repository
- screenpipe/screenpipe
- Path
crates/screenpipe-core/assets/skills/screenpipe-workflow-discovery/SKILL.md- Repo updated
- 17 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Screenpipe Workflow Discovery skill do?
Identify repeated work from recorded activity or starred examples and assess which steps could be automated.
How do I install the Screenpipe Workflow Discovery skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add screenpipe/screenpipe --skill screenpipe-workflow-discovery. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Screenpipe Workflow Discovery popular?
It lives in screenpipe/screenpipe, which has 22,429 GitHub stars and 2,305 forks, and is included in 1 curated skill list.
Related skills
Develop Screenpipe Windows
22kscreenpipe/screenpipe
Develop and test Screenpipe Windows-native changes on a disposable Azure VM created from the prepared Screenpipe Windows dev image. Use for Windows compiler, process, service, local API, desktop, capture, installer, or permission behavior. Do not use for React-only work proved by the browser mock.
Release
22kscreenpipe/screenpipe
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
Render HTML Report
22kscreenpipe/screenpipe
Produce a human-facing visual report — a chart, dashboard, scorecard, or styled summary — that renders as a live page in the screenpipe viewer instead of plain text. Use when the task asks for a visual/graphical output rather than a plain note; do NOT use for plain text or raw data (prefer a markdown note for those).
Screenpipe Workflow Maintenance
22kscreenpipe/screenpipe
Investigate and review evidence-backed workflows with Screenpipe tools and shared drafts.
Screenpipe Meeting Prep
22kscreenpipe/screenpipe
Prepare for a specific upcoming meeting using verified identity and prior context.
Release Plannotator
13kbacknotprop/plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.