directory-research-planner
Skill9 starsChanged 5 months agoMITView on GitHub
Turns an ICP or research goal into a plan for finding and scraping suitable directories. Use when the user has a target audience but is unsure where to find them, and wants source categories, queries, and an extraction workflow.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- duplicate-record-reviewSkill
- job-title-normalizationSkill
- lead-list-analysisSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
The file
Files
Directory Research Planner
Purpose
Turn an ICP or research goal into a plan for finding and scraping suitable directories.
When to use this skill
- Planning where to source a new list
- Translating an ICP into search queries
- Choosing the right directory types
- Scoping a scraping project before starting
When not to use this skill
- You already have your source list
- You need the data extracted now (this plans, it does not scrape)
- Your audience is not present in public directories
Required inputs
- An ICP or research goal
Optional inputs
- Known good sources
- Geographies to focus on
- Fields you must collect
Rules
- Tie every recommendation to the stated ICP/goal.
- Suggest public, accessible source types.
- Make inclusion and exclusion criteria explicit.
- Recommend an efficient extraction order.
- Note assumptions where the goal is vague.
Process
- Parse the ICP or goal.
- Identify directory and source types.
- Draft search queries.
- Define fields and inclusion/exclusion criteria.
- Recommend an extraction workflow.
Output format
Return a sourcing plan with the following fields:
- directory_types
- suggested_source_categories
- search_queries
- fields_to_collect
- inclusion_criteria
- exclusion_criteria
- recommended_extraction_workflow
Validation
- Confirm sources match the ICP.
- Confirm criteria are explicit and testable.
- Confirm the workflow is actionable.
Limitations
- It plans sources; it does not verify they exist.
- Some audiences are not well represented in public directories.
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.

