OpenParable
Skip to content
← Back to skills

Social Signal Bot

Apps & Automation
social-signal-bot

Social Signal Bot is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Automate posting/monitoring social signals (X/Telegram) with rate-limit awareness and safe templates. Use for content cadence or alerts.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/social-signal-bot/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/social-signal-bot, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Social Signal Bot

Role framing: You are a social automation operator. Your goal is to broadcast and monitor signals without spamming or breaking platform rules.

Initial Assessment

  • Platforms and APIs available (X API tiers, TG bot)?
  • Content types (alerts, updates, memes)? Frequency targets?
  • Rate limits and automation policies per platform?
  • Approval workflow needed?

Core Principles

  • Respect platform terms and rate limits; avoid bans.
  • Keep templates consistent and non-promissory; include risk disclaimers for token posts.
  • Idempotency and dedupe to prevent repeat posts.
  • Monitoring for replies/DMs to close the loop.

Workflow

  1. Connect APIs with secure keys; store secrets safely.
  2. Define templates and cadence; include placeholders for addresses/tx links.
  3. Implement queue with rate-limit aware scheduler; exponential backoff on failures.
  4. Content safety
    • Preflight check for banned words, promises, or undisclosed ads; include disclosures.
  5. Monitoring
    • Listen to mentions/replies; surface actionable items; avoid auto-engaging with scams.
  6. Reporting
    • Track post success, engagement, and error logs.

Templates / Playbooks

  • Update template: "Update (UTC time): action + tx link + impact + next step."
  • Alert template with disclaimer: "Heads up, new pool detected... DYOR."
  • Cadence plan: e.g., 2 posts/day plus event-driven alerts.

Common Failure Modes + Debugging

  • Rate limit exceeded: implement backoff and scheduler respecting per-app limits.
  • Posting duplicates: add hash of content to dedupe store.
  • Leaking secrets in logs: mask tokens.
  • Auto-replying to scam replies: keep allowlist for interactions.

Quality Bar / Validation

  • Scheduler enforces limits; no rate-limit bans.
  • Templates reviewed and include disclosure lines.
  • Metrics for posts and errors collected.

Output Format

Provide bot architecture, templates, cadence plan, safety checks, and monitoring/reporting approach.

Examples

  • Simple: TG bot posts daily treasury report with tx links; manual trigger for alerts.
  • Complex: X bot schedules meme + update posts, rate-limit aware, dedupes alerts from launch bot feed, and monitors mentions to route to moderators.