flowhunt

FlowHunt automates workflow audits by analyzing user behavior and providing actionable insights for productivity improvements.

Install this skill

85/100

Security score

The flowhunt skill was audited on May 23, 2026 and we found 3 security issues across 1 threat category. Review the findings below before installing.

medium line 3

Access to home directory dotfiles

SourceSKILL.md

1	---
2	name: flowhunt
3	description: Automation discovery audit. When the user says "flowhunt setup" walk them through a 5-question workflow intake (role, pain points, failed attempts, sacred areas, goal) and then wire Gmail/Calendar/Slack/task-tracker/optional messaging connectors and optionally install ActivityWatch. When the user says "flowhunt audit" collect data from all connected sources (and ActivityWatch if running), apply the FlowHunt analysis prompt with the user's stated context as the highest-priority input, and write a markdown report to ~/.flowhunt/audits/YYYY-MM-DD/audit.md. Audit works immediately after setup — ActivityWatch enriches it but is not required. Use this skill whenever the user mentions flowhunt, automation audit, productivity audit, or asks what they should automate in their workflow.
4	---
5

medium line 22

Access to home directory dotfiles

SourceSKILL.md

20	Trigger phrases: "flowhunt audit", "run audit", "audit my workflow", "what should I automate", "analyze my work patterns", "check flowhunt", any request to produce or refresh the audit report.
21
22	Action: read `audit.md` in this directory and follow its procedure end-to-end. It collects data from all connected sources (ActivityWatch data is used if AW is running, but the audit works without it), dumps raw data to `~/.flowhunt/audits/YYYY-MM-DD/raw/`, applies `prompts/audit-system-prompt.md`, writes `~/.flowhunt/audits/YYYY-MM-DD/audit.md`, asks the user "what would YOU automate?", and closes with a feedback link.
23
24	## Before you start either mode

medium line 29

Access to home directory dotfiles

SourceSKILL.md

27	2. Note your sandbox constraints for that agent (see `reference/environment.md`). Most important: inside `codex`, GUI app launch, port binding, nohup, and `open -a` are all refused — plan around it, do not fight it.
28	3. Confirm `curl`, `jq`, and `bash` are available. Baseline assumptions.
29	4. Make sure `~/.flowhunt/audits/` exists (`mkdir -p ~/.flowhunt/audits`). This is the persistent output location.
30
31	## Philosophy

Scanned on May 23, 2026

GitHub Stars 4

Rate this skill

Categorymarketing

UpdatedMay 31, 2026