Agent skill

Reputation Management

by indranilbanerjee in indranilbanerjee/digital-marketing-pro

Run reputation programs: reviews, sentiment, brand safety. An agent skill from indranilbanerjee/digital-marketing-pro.

MITAuto-check passed

Install Reputation Management

skills CLI
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/reputation-management .claude/skills/reputation-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reputation-management
GitHub stars
862
Used in
1 other repo
Token cost
~5k tokens
SKILL.md length
2,458 words
Files
7
Skills in repo
162
Repo updated
First seen
Licence
MIT

At a glance

Run reputation programs: reviews, sentiment, brand safety. An agent skill from indranilbanerjee/digital-marketing-pro.

  • Works in 9 steps: Check session context — The active brand… → If you need the full profile, read:… → Apply brand voice — Formality, energy,… → …
  • SKILL.md covers When to Use This Skill, Brand Context (Auto-Applied), Required Context and Capabilities, plus 5 more sections
  • Calls python

What it does

Reputation Management is an agent skill from indranilbanerjee/digital-marketing-pro. Run reputation programs: reviews, sentiment, brand safety. Crisis → crisis-response; one review → review-response. "get more Google reviews"

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `brand-safety.md`, `crisis-communication.md` and `recovery-playbooks.md`).

The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.

Example prompts

  • “get more Google reviews”
  • “/reputation-management”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels…
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before…
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best…
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for…

What it can do on your machine

Read from SKILL.md and the folder at commit 9e949f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reputation Management loads about 5k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 2,458 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 9e949f3, republished under its MIT licence (© indranilbanerjee). 2,458 words, ~5,044 tokens.

Download SKILL.mdSave it as .claude/skills/reputation-management/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
reputation-management
description
Run reputation programs: reviews, sentiment, brand safety. Crisis → crisis-response; one review → review-response. "get more Google reviews"

Reputation Management

Script location. If your host does not set ${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin's scripts/ folder, next to skills/.

When to Use This Skill

Activate this skill when the user's request involves any of the following:

  • Generating more customer reviews or managing existing reviews across platforms
  • Responding to negative reviews (Google, Yelp, G2, Capterra, Trustpilot, Amazon, BBB, industry-specific sites)
  • Preparing for or responding to a brand crisis (product recall, executive scandal, data breach, viral complaint, lawsuit)
  • Assessing and mitigating brand safety risks in advertising and partnerships
  • Monitoring brand sentiment across social media, review platforms, and press
  • Building a reputation recovery plan after a negative event
  • Handling negative press, unfavorable search results, or misinformation
  • Managing employee reviews on platforms like Glassdoor or Indeed
  • Designing proactive reputation-building strategies
  • Evaluating brand safety settings for ad placements and content adjacency
  • Navigating legal constraints on reputation responses (defamation, HIPAA, regulated industries)
  • Addressing fake review attacks or review manipulation by competitors

Brand Context (Auto-Applied)

Before producing any marketing output from this module:

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before planning new work
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices."
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for banned words, restricted claims, and mandatory disclaimers; channel-styles.md for channel-specific tone overrides (may differ from base voice); messaging.md for approved key messages, taglines, and positioning language; voice-and-tone.md for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.

Do not ask the user for information that already exists in their brand profile.

Required Context

Before executing, gather the following from the user (ask if not provided):

  • Current situation: Is this proactive reputation building, reactive crisis response, or ongoing reputation maintenance?
  • Severity level: For crisis situations, what is the scope and intensity? (Single negative review, trending negative conversation, press coverage, legal action)
  • Industry: Needed for compliance constraints (healthcare/HIPAA, finance/FINRA, legal/bar rules, government)
  • Platform landscape: Which review platforms and social channels are most relevant to the business
  • Current review profile: Average rating, review volume, review trend, and response rate
  • Brand voice: Tone and communication style guidelines
  • Stakeholders: Who needs to be involved in approvals (legal, PR, C-suite, customer service)
  • Existing monitoring: What tools or processes are in place for sentiment tracking
  • History: Any past crises or reputation issues and how they were handled
  • Resources: Team capacity for review management, crisis response, and ongoing monitoring

Capabilities

Review Generation
  • FTC-compliant solicitation: Ask for reviews without incentivizing positive reviews specifically. Incentives for leaving a review (not a positive review) require disclosure. Never gate reviews by satisfaction level (asking happy customers to review publicly while routing unhappy customers to private feedback is prohibited)
  • Platform-specific timing: Google reviews (post-purchase/service completion), G2/Capterra (after meaningful product usage, typically 30-60 days), Amazon (post-delivery with review request button), Yelp (never directly solicit -- Yelp penalizes solicited reviews)
  • Review request sequences: Email, SMS, in-app prompts, QR codes on receipts/packaging, post-interaction follow-ups
  • Review volume strategy: Consistent review velocity matters more than spikes. Build automated review request flows triggered by key customer milestones
  • Review platform prioritization: Focus efforts on platforms that influence purchase decisions for the specific industry (Google for local, G2 for SaaS, TripAdvisor for hospitality, Healthgrades for medical)
Negative Review Response Framework
  • Response timing: Respond within 24 hours for public reviews. Speed demonstrates attentiveness. Delayed responses appear dismissive
  • Response structure: Acknowledge the concern, apologize for the experience (not admitting fault), explain what happened if appropriate, offer a resolution, and move the conversation offline
  • Tone calibration: Professional and empathetic regardless of review tone. Never argue, get defensive, or blame the customer publicly. The response is for future readers, not just the reviewer
  • Legal review triggers: Know when a response requires legal review (threatened litigation, allegations of illegal activity, regulated industry topics, potential defamation claims)
  • Follow-up protocol: After resolving the issue offline, politely ask if the customer would consider updating their review. Never demand or pressure
  • Review disputes: Platform-specific processes for flagging fake, defamatory, or policy-violating reviews for removal
Crisis Communication (3-Tier Framework)

Tier 1 -- Minor Crisis (isolated complaint, single negative article, localized social media issue)

  • Severity indicators: Limited reach, no media pickup, contained to one platform or conversation
  • Response timeline: Respond within 24 hours with prepared acknowledgment
  • Actions: Direct customer response, monitor for spread, prepare holding statement if needed
  • Stakeholders: Customer service lead, social media manager

Tier 2 -- Moderate Crisis (trending complaint, multiple media outlets, influencer amplification, regional issue)

  • Severity indicators: Growing reach, media inquiries, multiple customer complaints on the same issue, hashtag trending
  • Response timeline: Public statement within 4 hours. Internal alignment within 2 hours
  • Actions: Activate crisis team, issue holding statement, prepare full response, monitor real-time, brief executives
  • Stakeholders: VP/Director of Marketing, PR team, legal counsel, customer service leadership
  • Stakeholder messaging matrix: Different messages for customers (empathy + action), employees (facts + guidance), media (official statement), investors (impact assessment + response plan), partners (reassurance + timeline)
  • Brand voice shift protocol: Move from standard marketing voice to crisis voice -- more human, more direct, less polished, zero humor, zero promotion

Tier 3 -- Severe Crisis (data breach, product safety issue, executive misconduct, viral outrage, regulatory action)

  • Severity indicators: National/international media coverage, regulatory involvement, potential legal liability, significant customer impact
  • Response timeline: Initial acknowledgment within 1 hour. Full response within 4 hours. Ongoing updates every 24-48 hours
  • Actions: CEO-level response, legal coordination, regulatory notification (if required), customer notification, operational remediation, third-party investigation (if needed)
  • 72-hour timeline: Hour 0-1 (acknowledge, assemble team), Hour 1-4 (fact-finding, holding statement), Hour 4-24 (detailed response, customer outreach, media statement), Hour 24-48 (operational updates, stakeholder briefings), Hour 48-72 (recovery plan announcement, ongoing communication cadence)
  • Stakeholders: CEO/C-suite, general counsel, board of directors (if public company), PR agency, regulatory contacts
Brand Safety (4-Layer Framework)

Layer 1 -- Ad Placement Safety

  • Ensuring ads do not appear alongside harmful, offensive, or brand-inappropriate content
  • Platform-specific brand safety settings (Google content exclusions, Meta inventory filters, YouTube placement exclusions)
  • Third-party verification tools (IAS, DoubleVerify) for programmatic environments
  • Keyword exclusion lists and site exclusion lists

Layer 2 -- Association Safety

  • Vetting partners, influencers, and sponsors for brand alignment and risk
  • Due diligence on co-marketing partners, event sponsors, and media placements
  • Ongoing monitoring of brand-associated entities for emerging controversies

Layer 3 -- Content Safety

  • Ensuring brand-produced content does not inadvertently create brand safety issues
  • Content review process for cultural sensitivity, inclusivity, and potential misinterpretation
  • Social media post approval workflows and crisis-proofing content calendars

Layer 4 -- Data Safety

  • Protecting customer data in marketing operations
  • Compliance with GDPR, CCPA, and other privacy regulations in marketing contexts
  • Vendor data handling assessments for marketing technology partners
Sentiment Monitoring Framework
  • Monitoring scope: Social media mentions, review platforms, news/press, forums, employee review sites, search results
  • Sentiment scoring: Positive, neutral, negative classification with intensity weighting
  • Alert thresholds: Define spike thresholds that trigger escalation (e.g., 3x normal negative mention volume in 24 hours)
  • Competitive benchmarking: Compare sentiment trends against key competitors
  • Topic clustering: Group sentiment by theme (product quality, customer service, pricing, leadership) to identify systemic issues
  • Trend analysis: Weekly/monthly sentiment trend reports to identify gradual shifts before they become crises
Reputation Recovery Playbooks

30-Day Plan (Immediate Stabilization)

  • Audit current reputation state across all platforms
  • Respond to all outstanding negative reviews
  • Launch review generation campaign to dilute negative content with fresh positive reviews
  • Publish thought leadership or positive press content to improve search results
  • Implement monitoring infrastructure if not already in place

60-Day Plan (Rebuilding)

  • Execute content strategy targeting negative search results (SEO for reputation)
  • Launch customer success stories and case study campaigns
  • Engage in community outreach and corporate responsibility initiatives
  • Build media relationships for positive press placements
  • Implement systematic review management process

90-Day Plan (Reinforcement)

  • Measure sentiment shift and review profile improvement
  • Establish ongoing reputation monitoring and maintenance cadence
  • Create crisis communication playbook to prevent future reputation damage
  • Build brand advocacy program with satisfied customers and employees
  • Conduct reputation audit to benchmark progress and set ongoing targets

Process

Show full SKILL.md (1,045 more words)Show less
Negative Review Response (Most Common Use Case)
  1. Assess the review -- Read carefully. Determine if the complaint is legitimate, exaggerated, or fabricated. Check if the reviewer is an actual customer. Assess the platform and visibility of the review.
  2. Check for legal triggers -- Does the review mention legal action, allege illegal behavior, or involve a regulated topic? If yes, route through legal before responding.
  3. Draft the response -- Follow the framework: acknowledge, empathize, explain (briefly and without excuses), offer resolution, and invite offline conversation. Keep it under 150 words for public responses.
  4. Tone check -- Ensure the response is empathetic, professional, and non-defensive. Read it from the perspective of a potential customer seeing both the review and the response. The response should make the brand look better, not worse.
  5. Post and track -- Publish the response, log it in the review management system, and set a follow-up reminder to check if the customer responded or updated their review.
  6. Resolve offline -- If the customer engages, resolve the issue through direct communication. Document the resolution for internal process improvement.
  7. Pattern analysis -- Regularly analyze negative reviews for recurring themes. Feed patterns back to product, operations, and customer service teams for systemic fixes.
Crisis Response Activation
  1. Severity assessment -- Classify the crisis as Tier 1, 2, or 3 based on reach, media involvement, customer impact, and legal exposure.
  2. Assemble the team -- Activate the appropriate stakeholders based on tier level. Establish a communication channel for real-time coordination.
  3. Fact-finding -- Gather all available information. What happened, when, who is affected, what is the scope, and what do we know vs what is speculation.
  4. Holding statement -- Issue a brief acknowledgment that the brand is aware of the situation and is investigating. This buys time without leaving a silence vacuum.
  5. Detailed response -- Craft the full response addressing what happened, what the brand is doing about it, and what affected parties should do. Tailor messaging per stakeholder group.
  6. Distribution -- Publish the response through appropriate channels (website statement, social media, email to affected customers, press release if media is involved).
  7. Monitor and update -- Track conversation in real time. Update stakeholders and the public at regular intervals. Correct misinformation promptly.
  8. Post-crisis review -- After the crisis subsides, conduct a retrospective. What caused it, how was the response, what should change in the crisis playbook, and what operational changes prevent recurrence.

Reference Files

  • review-strategy.md -- Review generation tactics, platform-specific solicitation rules, response templates, and review management workflows
  • crisis-communication.md -- 3-tier crisis framework details, stakeholder messaging templates, 72-hour timeline playbook, and post-crisis retrospective guide
  • brand-safety.md -- 4-layer brand safety framework, platform-specific settings, vendor evaluation criteria, and brand safety audit checklists
  • sentiment-monitoring.md -- Monitoring tool recommendations, alert configuration guides, reporting templates, and competitive benchmarking methods
  • recovery-playbooks.md -- 30/60/90-day recovery plans, SEO-for-reputation tactics, advocacy program designs, and reputation audit frameworks
  • review-management-platforms.md -- Review platform landscape, tool comparison, platform-specific policies, and FTC compliance guidance for review management

Output Formats

  • Review response: Ready-to-publish response text tailored to the specific review, platform, and brand voice
  • Crisis communication plan: Severity assessment, stakeholder matrix, messaging by audience, timeline, and channel distribution plan
  • Brand safety audit: Layer-by-layer assessment, risk scores, gap analysis, and prioritized remediation actions
  • Sentiment report: Current sentiment baseline, trend analysis, competitive comparison, and topic-level breakdown
  • Reputation recovery plan: 30/60/90-day action plan with specific tactics, responsible parties, success metrics, and timeline
  • Review management playbook: Standard operating procedures for review generation, monitoring, response, and escalation

Edge Cases

Crisis During Campaign Launch

If a crisis hits during a planned campaign launch, pause all scheduled marketing content immediately. Promotional content running alongside crisis response appears tone-deaf and amplifies backlash. Resume campaigns only after the crisis is resolved and public sentiment has stabilized. Factor in a buffer period -- restarting promotions too quickly can reignite criticism.

Regional Crisis Containment

When a crisis is localized to one market or region, attempt containment before it spreads. Respond in the local language and on local platforms. Adjust global content calendars to avoid tone-deaf cross-posting. Brief regional teams immediately even if their markets are not yet affected, so they can prepare.

Influencer-Caused vs Company-Caused Crisis

The response playbook differs based on crisis origin. For influencer-caused issues (influencer says something offensive while associated with the brand), distance the brand, invoke the morality clause, and focus messaging on brand values. For company-caused issues (product defect, employee misconduct, data breach), own the problem, take responsibility, and focus messaging on actions being taken.

In healthcare, finance, and legal services, every public statement may have compliance implications. Build mandatory legal review into the crisis response timeline. For HIPAA-covered entities, never acknowledge a specific patient relationship in a review response. For financial services, never make statements that could be construed as investment advice or guarantees. These legal gates add response time, so prepare pre-approved response templates for common scenarios.

Social Media Pile-On with Misinformation

When a brand faces viral criticism built on inaccurate information, resist the urge to respond emotionally or repeatedly. Issue one clear, factual correction through official channels. Do not engage in back-and-forth arguments with individual commenters. Arm supporters and employees with accurate talking points. Monitor for influencer or media amplification and respond directly to high-reach accounts spreading misinformation.

Fake Review Attacks

If a business is targeted by coordinated fake negative reviews (competitor sabotage, disgruntled ex-employee, online mob), document the pattern (timing, reviewer profiles, language similarities), report to the platform with evidence, and respond to each review professionally (the response is for genuine readers, not the fake reviewers). Consider legal action for demonstrable defamation. Accelerate genuine review generation to dilute the impact.

Employee Review Management (Glassdoor)

Employee review platforms influence recruiting and brand perception. Respond to negative Glassdoor reviews with the same professionalism as customer reviews. Never attempt to identify anonymous reviewers. Address systemic themes in employer branding content. Encourage satisfied employees to share their experiences authentically (never mandate or incentivize specific positive reviews).

  • Influencer & Creator Marketing -- Managing reputation risks from influencer partnerships and controversies
  • Paid Advertising -- Brand safety settings in ad platforms and pausing campaigns during crises
  • Content Engine -- Positive content creation for reputation recovery and thought leadership
  • Analytics & Insights -- Sentiment data analysis and reputation metric tracking
  • SEO -- Search result optimization for reputation management (suppressing negative results)
  • Emerging Channels -- Monitoring and managing reputation on newer platforms and community channels

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in skills/reputation-management of indranilbanerjee/digital-marketing-pro.

  • SKILL.md
  • brand-safety.md
  • crisis-communication.md
  • recovery-playbooks.md
  • review-management-platforms.md
  • review-strategy.md
  • sentiment-monitoring.md

Open the folder on GitHubat commit 9e949f3

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Reputation Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reputation Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reputation Management this skillindranilbanerjee/digital-marketing-pro8621 repos~5kAutomated safety check: PassMIT
Strict Programming Practicescode-yeongyu/oh-my-openagent70k—~9.5kAutomated safety check: PassCustom licence
Python Type Safetywshobson/agents40k—~1.4kAutomated safety check: PassMIT
Safety Guardaffaan-m/ECC277k2 repos~554Automated safety check: NotesMIT
Safety Guardaffaan-m/ECC276k—~323Automated safety check: NotesMIT
Safety Guardaffaan-m/ECC276k—~255Automated safety check: NotesMIT

Similar skills

  • Strict Programming Practices

    code-yeongyu/oh-my-openagent

    Applies strict, type-first coding rules for Python, Rust, TypeScript and Go, loading the matching language reference before the agent writes or edits any code.

    70k GitHub stars~9.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Python Type Safety

    wshobson/agents

    Python type safety with type hints, generics, protocols, and strict type checking.

    40k GitHub stars~1.4k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Safety Guard

    affaan-m/ECC

    Guard against destructive operations with three modes: Careful intercepts dangerous commands (rm -rf, git push --force, DROP TABLE) for confirmation, Freeze locks writes to one directory, and Guard…

    277k GitHub starsUsed in 2 repos~554 tokens
    DevelopmentAuto-check: notes
  • Safety Guard

    affaan-m/ECC

    本番システムでの作業時や、エージェントを自律的に実行する際に破壊的な操作を防ぐためにこのスキルを使用してください. An agent skill from affaan-m/ECC.

    276k GitHub stars~323 tokensUpdated yesterday
    Auto-check: notes
  • Safety Guard

    affaan-m/ECC

    使用此技能可防止在生产系统上工作或自主运行代理时进行破坏性操作。

    276k GitHub stars~255 tokensUpdated yesterday
    Auto-check: notes
  • Referral Program

    alirezarezvani/claude-skills

    When the user wants to design, launch, or optimize a referral or affiliate program.

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

More from indranilbanerjee/digital-marketing-pro

All 162 skills in this repo
  • Import Template

    indranilbanerjee/digital-marketing-pro

    Import a deliverable template as a reusable placeholder template per brand.

    862 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Plan an A/B test by script: sample size per variant, days to run, stopping rules.

    862 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Aeo Audit

    indranilbanerjee/digital-marketing-pro

    Run a one-time AEO audit of six AI answer engines, scored per surface.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Agent Readiness Audit

    indranilbanerjee/digital-marketing-pro

    Audit agent readiness by script: AI-crawler rules, product schema, no-JS HTML, feeds.

    862 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed
  • Backlink Gap

    indranilbanerjee/digital-marketing-pro

    Find backlink gap domains linking to competitors, not you, scored by script.

    862 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • C2pa Metadata

    indranilbanerjee/digital-marketing-pro

    Embed C2PA provenance in AI-generated images, video or PDF by script.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Reputation Management

What does Reputation Management do?

Run reputation programs: reviews, sentiment, brand safety. An agent skill from indranilbanerjee/digital-marketing-pro. Reputation Management is an agent skill from indranilbanerjee/digital-marketing-pro. Run reputation programs: reviews, sentiment, brand safety.

How do I install Reputation Management in Claude Code?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a claude-code`. Or copy the skill folder (skills/reputation-management in indranilbanerjee/digital-marketing-pro) into .claude/skills/reputation-management in your project. Claude Code loads it when a task matches its description.

How do I install Reputation Management in Codex?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a codex`. Or copy the skill folder (skills/reputation-management in indranilbanerjee/digital-marketing-pro) into .agents/skills/reputation-management in your project. Codex loads it when a task matches its description.

Can I use Reputation Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reputation-management, .gemini/skills/reputation-management, .github/skills/reputation-management and .opencode/skills/reputation-management in your project.

What does Reputation Management need to run?

Going by SKILL.md and its folder, Reputation Management needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Reputation Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Reputation Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reputation Management use?

Reputation Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reputation Management use?

About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reputation Management?

Skills that share tags, products or a category with Reputation Management: Strict Programming Practices (code-yeongyu/oh-my-openagent, 70k stars), Python Type Safety (wshobson/agents, 40k stars), Safety Guard (affaan-m/ECC, 277k stars) and Safety Guard (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reputation Management?

indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 862 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 9, 2026.

Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.