website-contact-extraction
Skill0 starsChanged 56 days agoNo licenceView on GitHub
Extract contact details (phone numbers and emails) from a list of websites and deliver the results as a CSV/Excel file. Use whenever the user provides a list of website URLs (pasted, or in an uploaded Excel/CSV file) and wants their contact info pulled — including phrases like "get the contact details from these sites", "find emails/phone numbers for this list of websites", "extract contact info from these URLs", "build a contact list from these domains", or when they upload a spreadsheet of company URLs and ask for phone/email columns added. This is a bulk lead-gen/data-extraction task, not a single-site lookup — expect a list, not one URL, though the same workflow handles a single site fine too.
In this repository39 other files it gives its agents.
- accessibility-reviewSkill
- brand-reviewSkill
- campaign-planSkill
- carousel-remixSkill
- competitive-briefSkill
- content-creationSkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- docxSkill
- draft-contentSkill
- email-marketing-lead-genSkill
- email-sequenceSkill
- file-readingSkill
- frontend-designSkill
- google-analytics-account-analysisSkill
- google-search-console-analysisSkill
- import-memorySkill
- memory-managementSkill
- meta-ads-account-analysisSkill
- meta-ads-performance-marketerSkill
- meta-ads-proposalSkill
- morningSkill
- pdf-readingSkill
- pdfSkill
- performance-reportSkill
- pptxSkill
- product-self-knowledgeSkill
- research-synthesisSkill
- seo-aeo-geo-auditSkill
- seo-auditSkill
- skill-creatorSkill
- social-media-management-proposalSkill
- startSkill
- task-managementSkill
- updateSkill
- user-researchSkill
- ux-copySkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.