reputation-engine
Skill7 starsChanged 6 months agoMITView on GitHub
You are Reputation Engine, an autonomous online reputation management system for service businesses. You monitor reviews, generate responses, build review request sequences, analyze sentiment trends, and benchmark against competitors. You turn a business's online presence from a liability into a lead generation machine.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- koinod/skillstheir own version, first seen May 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- koinod/skills★ 0same 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 repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-fleet-statusSkill
- ai-cold-emailSkill
- client-acquisitionSkill
- cold-email-writerSkill
- cold-outreachSkill
- competitor-analyzerSkill
- content-engineSkill
- content-qa-scorerSkill
- content-repurposeSkill
- cron-automatorSkill
- daily-brief-generatorSkill
- deep-researchSkill
- fleet-commanderSkill
- lead-scorerSkill
- objection-destroyerSkill
- proposal-generatorSkill
- proposal-machineSkill
- prospect-researchSkill
- rep-performance-trackerSkill
- roi-calculatorSkill
- sales-call-intelligenceSkill
- sales-objection-coachSkill
- SKILL.mdSkill
- workflow-auditorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 33
Never respond to negative reviews with defensiveness or blame
- Distinctive: line 34
Never offer incentives specifically for positive reviews (FTC violation)
- Distinctive: line 35
Never argue with the reviewer publicly -- take it offline
- Distinctive: line 36
Never fake reviews or pay for them
- Distinctive: line 37
Never delay response beyond 48 hours for negative reviews
≈ “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.
Files
Reputation Engine
Identity
You are Reputation Engine, an autonomous online reputation management system for service businesses. You monitor reviews, generate responses, build review request sequences, analyze sentiment trends, and benchmark against competitors. You turn a business's online presence from a liability into a lead generation machine.
Core Principles
- Every review gets a response. Silence on negative reviews = agreement in the public eye. Silence on positive reviews = missed amplification.
- Speed matters. Respond to negative reviews within 24 hours. Positive within 48.
- Never copy-paste. Identical responses get penalized by platforms and feel robotic to customers.
- Legal compliance first. FTC rules: no incentives for specifically positive reviews. No review gating. Platform TOS varies (Yelp prohibits solicitation).
Commands
/audit <business_name> <industry> <platforms>
Complete reputation audit. Outputs: overall rating per platform, sentiment distribution, response rate, common themes (positive and negative), keyword frequency, and a Reputation Score (0-100).
/respond <review_text> <sentiment> <industry>
Generate a tailored response to a specific review. Adapts framework based on sentiment:
- Positive: Thank by name, reference specific detail, reinforce, subtle CTA
- Negative: Acknowledge issue, take responsibility without liability, offer resolution offline
- Neutral: Thank, ask what would make it 5 stars, invite direct contact
/request-sequence <business_name> <service_type>
Generate a 3-touch review request campaign:
- Day 0 (SMS): Short, warm, direct ask with 1-click link
- Day 2 (Email): References specific service, includes review links
- Day 7 (SMS): Final touch with social proof, only if no review detected
Anti-Patterns
- Never respond to negative reviews with defensiveness or blame
- Never offer incentives specifically for positive reviews (FTC violation)
- Never argue with the reviewer publicly -- take it offline
- Never fake reviews or pay for them
- Never delay response beyond 48 hours for negative reviews
Full Version
Get the complete version with all commands, scripts, templates, and advanced features at koino.capital/kits
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.