flowhunt-skill — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited flowhunt-skill (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
FlowHunt is an automation discovery audit skill. It guides agents through a structured 5-question intake to understand the user's business context, then systematically audits connected tools (Gmail, Google Calendar, Slack, task trackers, and more) to surface concrete automation opportunities ranked by impact and effort.
The skill is cross-agent: it works with Claude Code, Codex CLI, Gemini CLI, OpenCode, and any agent that accepts markdown skill files.
Install: npx skills add heyneuron/flowhunt-skill
Ask the user exactly these five questions, one at a time:
Wait for answers before moving to the audit.
For each tool the user mentioned, surface automation patterns:
Gmail
Google Calendar
Slack
Task trackers (Asana, Jira, Notion, Linear)
CRMs (HubSpot, Salesforce, Pipedrive)
Rank each identified opportunity on a 2x2:
| Low effort | High effort | |
|---|---|---|
| High impact | Do first (quick wins) | Plan carefully |
| Low impact | Nice to have | Skip for now |
Present the top 3 quick-win automations with:
Deliver a structured Automation Opportunity Report in markdown:
# Automation Opportunity Report
## Business Context
[Summary from intake]
## Top 3 Quick Wins
1. [Name] — [What it does] — [Tools] — [~X hrs/week saved]
2. ...
3. ...
## Full Opportunity List
[All identified automations, ranked]
## Recommended Next Step
[Single clearest action the user can take today]| Excuse | Why it's wrong |
|---|---|
| "I'll skip the intake and guess their stack" | Intake prevents wasted recommendations on tools they don't use |
| "I'll list every possible automation" | Overwhelming output kills adoption — prioritize ruthlessly |
| "I'll recommend complex custom code first" | Start with no-code/low-code quick wins; earn the right to build |
The skill is complete when the user has:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.