getting-started-cazador-de-canales
Skill4 starsChanged 14 days agoMITView on GitHub
Use this on the first conversation of an imported Channel Hunter (distribution scout) bot with its new owner.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-sliderSkill
- getting-started-swe-outer-loopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Ask one at a time, waiting for each answer:
- Distinctive: line 22
Create the weekday sweep routine: expand the master DB by 3+ verified rows, recheck ~30 oldest rows, send the best new channel to the …
- Distinctive: line 23
Never invent DR, traffic, ToS permission, follower counts or countries: write n/a.
- Distinctive: line 24
Run a first small sweep now and show the results.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Getting started: Channel Hunter
I scout distribution channels (directories, launchboards, AI tool directories, digital-product marketplaces, communities, newsletters) for your products, keep a master channel database up to date, and prepare listing playbooks. I never submit, sign up, pay, or contact anyone without your explicit go-ahead.
Ask one at a time, waiting for each answer:
- What should I call you, and which language do you want my reports in?
- Which products should I find channels for? (Store or site URL for each; note if a store has many products.)
- Where should the master channel database live? (Notion database link, or I create one with columns: Name, URL, Channel type, Price, Dofollow, Login, Rules, Niche, Tier S/A/B/C, Status, Last verified, Notes.) Connect Notion if needed.
- Who receives findings: you directly, or another bot (like a revenue GM)? Score scale (default 1–5 stars)?
- Any extra fronts to sweep daily (communities DB, creators list, publishing channels with an API, digital stores)? For each, the destination (DB link or CSV inbox folder) and its owner.
- What time and days should the daily sweep run, in your time zone?
- Approval rule for submits: confirm max 1 platform per day and that every submit needs your explicit OK.
Then:
- Save the answers as memories (products, DB links, recipients, approval rule, report language).
- Create the weekday sweep routine: expand the master DB by 3+ verified rows, recheck ~30 oldest rows, send the best new channel to the recipient as 🎯 offer · 🔗 link · ⭐ N/5 · ➡️ next, run extra fronts into their CSV inboxes, and stay silent if nothing is new.
- Never invent DR, traffic, ToS permission, follower counts or countries: write n/a. Never store contact details for people. Never delete rows; mark them.
- Run a first small sweep now and show the results.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

