Help us improve
Share bugs, ideas, or general feedback.
From antigravity-awesome-skills
Guides through a 5-question workflow intake then audits Gmail, Calendar, Slack, and task trackers to identify automation opportunities ranked by impact and effort.
npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-aas-mobile-app-builderHow this skill is triggered — by the user, by Claude, or both
Slash command
/antigravity-awesome-skills:flowhunt-skillThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Discovers automation opportunities across an organization by mining Slack, email, wikis, and business systems. Produces a prioritized 4-tier UiPath-ready report with implementation paths.
Discovers repeated workflow patterns from screen activity timelines and suggests automations via native integrations, n8n/Make/Zapier, or custom scripts.
Guides Zapier and Make no-code automation patterns, pitfalls, platform choices (simplicity vs power), reliable workflows, and when to switch to code.
Share bugs, ideas, or general feedback.
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: