reply-handler
Skill9 starsChanged 7 months agoNo licenceView on GitHub
Analyze cold outreach replies and craft the right response based on a relationship-first philosophy. Use when asked "how to reply to this", "they said X what do I say", "handle this objection", "got a response from a prospect", "interested reply", "not interested reply", "next step after reply", "competitor objection", "pricing question", or "how do I respond to this email/LinkedIn message". Always use this skill before writing any reply to a prospect.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- prosyo-ai/gtm-skilltheir own version, first seen Oct 25, 2026
- vicfromthegtmclub/gtmskillsedited, first seen Aug 10, 2026
- xx254/linkedin_skillstheir own version, first seen Apr 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- vicfromthegtmclub/gtmskills★ 196% same
Wrote their own version · 2
- xx254/linkedin_skills★ 16same name
- prosyo-ai/gtm-skill★ 13same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- campaign-angle-finderSkill
- claap-sales-opportunity-detectorSkill
- cold-call-scriptSkill
- company-finderSkill
- competitor-finderSkill
- copywriting-analyzerSkill
- copywriting-first-touchSkill
- copywriting-follow-upSkill
- copywriting-ic-sequenceSkill
- copywriting-manager-sequenceSkill
- copywriting-refinerSkill
- copywriting-vp-sequenceSkill
- crm-duplicate-detectorSkill
- cta-designerSkill
- deep-company-analyserSkill
- gtm-action-thinkerSkill
- icp-definerSkill
- linkedin-outbound-angleSkill
- linkedin-sequenceSkill
- list-builderSkill
- market-research-edpSkill
- n8n-debuggerSkill
- n8n-workflow-builderSkill
- niche-data-finderSkill
- offer-definerSkill
- outbound-analystSkill
- outbound-campaign-architectSkill
- pain-identifierSkill
- people-finderSkill
- persona-definerSkill
- persona-insights-analysisSkill
- pipeline-analysisSkill
- prompt-engineeringSkill
- slide-deck-builderSkill
- trigger-finderSkill
- value-prop-listerSkill
- website-scraperSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
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 measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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.