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.
Run reputation programs: reviews, sentiment, brand safety. An agent skill from indranilbanerjee/digital-marketing-pro.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .claude/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/reputation-management .agents/skills/reputation-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .agents/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/reputation-management .cursor/skills/reputation-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .cursor/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/indranilbanerjee/digital-marketing-pro.git --path skills/reputation-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/reputation-management .gemini/skills/reputation-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .gemini/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/reputation-management .github/skills/reputation-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .github/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill reputation-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro reputation-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/reputation-management .opencode/skills/reputation-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "reputation-management" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/reputation-management into .opencode/skills/reputation-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reputation-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
reputation-managementRun 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. 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.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9e949f3. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from indranilbanerjee/digital-marketing-pro at commit 9e949f3, republished under its MIT licence (© indranilbanerjee). 2,458 words, ~5,044 tokens.
.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.Script location. If your host does not set
${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin'sscripts/folder, next toskills/.
Activate this skill when the user's request involves any of the following:
Before producing any marketing output from this module:
~/.claude-marketing/brands/{slug}/profile.jsonskills/context-engine/compliance-rules.mdskills/context-engine/industry-profiles.md for the brand's industryskills/context-engine/platform-specs.md for character limits and format requirementspython "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before planning new work~/.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.
Before executing, gather the following from the user (ask if not provided):
Tier 1 -- Minor Crisis (isolated complaint, single negative article, localized social media issue)
Tier 2 -- Moderate Crisis (trending complaint, multiple media outlets, influencer amplification, regional issue)
Tier 3 -- Severe Crisis (data breach, product safety issue, executive misconduct, viral outrage, regulatory action)
Layer 1 -- Ad Placement Safety
Layer 2 -- Association Safety
Layer 3 -- Content Safety
Layer 4 -- Data Safety
30-Day Plan (Immediate Stabilization)
60-Day Plan (Rebuilding)
90-Day Plan (Reinforcement)
review-strategy.md -- Review generation tactics, platform-specific solicitation rules, response templates, and review management workflowscrisis-communication.md -- 3-tier crisis framework details, stakeholder messaging templates, 72-hour timeline playbook, and post-crisis retrospective guidebrand-safety.md -- 4-layer brand safety framework, platform-specific settings, vendor evaluation criteria, and brand safety audit checklistssentiment-monitoring.md -- Monitoring tool recommendations, alert configuration guides, reporting templates, and competitive benchmarking methodsrecovery-playbooks.md -- 30/60/90-day recovery plans, SEO-for-reputation tactics, advocacy program designs, and reputation audit frameworksreview-management-platforms.md -- Review platform landscape, tool comparison, platform-specific policies, and FTC compliance guidance for review managementIf 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.
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.
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.
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.
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 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).
© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files in skills/reputation-management of indranilbanerjee/digital-marketing-pro.
Open the folder on GitHubat commit 9e949f3
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Reputation Management this skillindranilbanerjee/digital-marketing-pro | 862 | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Strict Programming Practicescode-yeongyu/oh-my-openagent | 70k | — | ~9.5k | Automated safety check: Pass | Custom licence | |
| Python Type Safetywshobson/agents | 40k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Safety Guardaffaan-m/ECC | 277k | 2 repos | ~554 | Automated safety check: Notes | MIT | |
| Safety Guardaffaan-m/ECC | 276k | — | ~323 | Automated safety check: Notes | MIT | |
| Safety Guardaffaan-m/ECC | 276k | — | ~255 | Automated safety check: Notes | MIT |
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.
wshobson/agents
Python type safety with type hints, generics, protocols, and strict type checking.
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…
affaan-m/ECC
本番システムでの作業時や、エージェントを自律的に実行する際に破壊的な操作を防ぐためにこのスキルを使用してください. An agent skill from affaan-m/ECC.
affaan-m/ECC
使用此技能可防止在生产系统上工作或自主运行代理时进行破坏性操作。
alirezarezvani/claude-skills
When the user wants to design, launch, or optimize a referral or affiliate program.
indranilbanerjee/digital-marketing-pro
Import a deliverable template as a reusable placeholder template per brand.
indranilbanerjee/digital-marketing-pro
Plan an A/B test by script: sample size per variant, days to run, stopping rules.
indranilbanerjee/digital-marketing-pro
Run a one-time AEO audit of six AI answer engines, scored per surface.
indranilbanerjee/digital-marketing-pro
Audit agent readiness by script: AI-crawler rules, product schema, no-JS HTML, feeds.
indranilbanerjee/digital-marketing-pro
Find backlink gap domains linking to competitors, not you, scored by script.
indranilbanerjee/digital-marketing-pro
Embed C2PA provenance in AI-generated images, video or PDF by script.
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.
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.
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.
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.
Going by SKILL.md and its folder, Reputation Management needs the command-line tools its instructions call (python). Our summary lists: Python 3.
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.
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.
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.
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.
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.
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.