community

name	community
description	This skill should be used when managing community presence across platforms (Discord, GitHub, X/Twitter, Bluesky, LinkedIn, Hacker News). It provides sub-commands for generating digests, checking health metrics, and listing enabled platforms.

Community Management

Manage community presence across Discord, GitHub, X/Twitter, Bluesky, LinkedIn, and Hacker News. Detects enabled platforms from environment variables (or always-on for GitHub and HN) and delegates data collection to platform-specific scripts.

Arguments

$ARGUMENTS is parsed for a sub-command and optional flags:

community [sub-command] [--headless] [--platform PLATFORM]
community engage [--max-results N] [--headless]

If $ARGUMENTS is empty or unrecognized, present the sub-command menu below.

If --headless is present, skip all interactive prompts and approval gates.

Platform Detection

Platform detection is centralized in community-router.sh. Run at the start of every sub-command:

bash ${CLAUDE_PLUGIN_ROOT:-plugins/soleur}/skills/community/scripts/community-router.sh platforms

This prints each platform's name, enabled/disabled status, and script filename. The router's PLATFORMS array is the single source of truth for platform names, required env vars, and auth checks. To add a new platform, add one entry to the array and create the script.

Scripts

Platform scripts are located at plugins/soleur/skills/community/scripts/:

• community-router.sh -- Platform dispatch router (single source of truth for platform detection)
• discord-community.sh -- Discord Bot API wrapper (messages, members, guild-info, channels)
• discord-setup.sh -- Discord credential setup and validation
• github-community.sh -- GitHub API wrapper (activity, contributors, discussions, repo-stats)
• x-community.sh -- X/Twitter API v2 wrapper (fetch-metrics, fetch-mentions, fetch-timeline, fetch-user-timeline, post-tweet)
• x-setup.sh -- X/Twitter credential setup and validation
• bsky-community.sh -- Bluesky AT Protocol wrapper (create-session, post, get-metrics, get-notifications)
• bsky-setup.sh -- Bluesky credential setup and validation
• linkedin-community.sh -- LinkedIn API wrapper (post-content, fetch-metrics stub, fetch-activity stub)
• linkedin-setup.sh -- LinkedIn credential setup, token introspection, and OAuth token generation
• hn-community.sh -- Hacker News Algolia API wrapper (mentions, trending, thread)

Sub-Commands

digest

Generate a multi-platform community digest. Spawns the community-manager agent with digest instructions.

1. Run platform detection
2. Spawn agent: community-manager with prompt: "Generate a community digest covering the last 7 days. Enabled platforms: [list]. Collect data from each enabled platform and produce a unified digest."
3. The agent writes the digest to knowledge-base/support/community/YYYY-MM-DD-digest.md

If --headless is set, skip the Discord posting approval gate (the agent handles this).

health

Display community health metrics across all enabled platforms. Spawns the community-manager agent with health instructions.

1. Run platform detection
2. Spawn agent: community-manager with prompt: "Display community health metrics. Enabled platforms: [list]. Show metrics from each enabled platform."
3. Metrics are displayed inline (no file output)

platforms

List all platforms with their configuration status. Does NOT spawn an agent -- runs directly.

1. Run bash ${CLAUDE_PLUGIN_ROOT:-plugins/soleur}/skills/community/scripts/community-router.sh platforms
2. For disabled platforms, show setup instructions:
   • Discord: "Run plugins/soleur/skills/community/scripts/discord-setup.sh to configure"
   • X/Twitter: "Run plugins/soleur/skills/community/scripts/x-setup.sh validate-credentials to verify, or x-setup.sh write-env to save credentials"
   • Bluesky: "Run plugins/soleur/skills/community/scripts/bsky-setup.sh write-env to save credentials, or bsky-setup.sh verify to test"
   • LinkedIn: "Run plugins/soleur/skills/community/scripts/linkedin-setup.sh generate-token to set up credentials, or linkedin-setup.sh verify to test"

engage

Reply to recent mentions on X/Twitter or Bluesky using brand-voice drafts with human approval. Spawns the community-manager agent with engagement instructions.

Platform selection: The --platform flag specifies which platform to engage on. If --platform is not provided, use AskUserQuestion to prompt the user to choose from enabled platforms that support engagement (X/Twitter, Bluesky).

The selected platform must be enabled. If not configured, report the missing credentials and stop.

Flow (X/Twitter):

1. Run platform detection -- verify X/Twitter is enabled
2. Read the since-id state file (.soleur/x-engage-since-id, resolved via git rev-parse --show-toplevel). If the file exists and contains a valid numeric ID, pass it as --since-id to the fetch command. If missing or non-numeric, skip (fetches last N mentions).
3. Spawn agent: community-manager with prompt: "Engage with recent X/Twitter mentions. Use Capability 4: Mention Engagement. Max results: [N]. Since ID: [ID or none]."
4. The agent fetches mentions via community-router.sh x fetch-mentions
5. For each mention, the agent drafts a reply following brand guide voice (knowledge-base/marketing/brand-guide.md sections ## Voice and ## Channel Notes > ### X/Twitter). If the brand guide is missing, the agent warns but proceeds with a professional, declarative tone.
6. Each draft is presented via AskUserQuestion with options:
   • Accept -- post this reply via community-router.sh x post-tweet --reply-to <mention_id>
   • Edit -- modify the reply text (validate 280-character limit; re-prompt if over)
   • Skip -- move to the next mention
   • Skip all remaining -- end the session (available after the first mention)
7. After all mentions are processed, the agent updates the since-id state file with the newest_id from the fetch response and displays a session summary (processed, posted, skipped counts).

Since-id state file:

• Path: .soleur/x-engage-since-id (relative to repo root)
• Format: plain text, single line containing the tweet ID
• Created on first run with mkdir -p .soleur && chmod 600 before writing
• Updated only after all mentions are processed (not per-reply)

Free tier degradation: If fetch-mentions returns 403 (client-not-enrolled), the community-manager agent switches to manual mode — prompting for tweet URLs instead of fetching mentions automatically. The rest of the pipeline (brand-voice draft, approval, post-tweet) runs unchanged. See Capability 4 Step 1b. When the paid tier activates, this fallback is never triggered.

Flow (Bluesky):

1. Run platform detection -- verify Bluesky is enabled (BSKY_HANDLE + BSKY_APP_PASSWORD)
2. Read the cursor state file (.soleur/bsky-engage-cursor, resolved via git rev-parse --show-toplevel). If the file exists and contains a non-empty value, pass it as --cursor to the fetch command.
3. Spawn agent: community-manager with prompt: "Engage with recent Bluesky mentions. Use Capability 4: Bluesky Mention Engagement. Limit: [N]. Cursor: [cursor or none]."
4. The agent fetches mentions via community-router.sh bsky get-notifications
5. For each mention, the agent drafts a reply following brand guide voice (knowledge-base/marketing/brand-guide.md sections ## Voice and ## Channel Notes > ### Bluesky). 300-character limit.
6. Same approval flow as X/Twitter (Accept, Edit, Skip, Skip all remaining) but with 300-character validation.
7. Accepted replies posted via community-router.sh bsky post "<text>" --reply-to-uri <uri> --reply-to-cid <cid>
8. After processing, the agent updates the cursor state file (.soleur/bsky-engage-cursor) and displays a session summary.

Bluesky cursor state file:

• Path: .soleur/bsky-engage-cursor (relative to repo root)
• Format: plain text, single line containing the cursor string
• Created on first run with mkdir -p .soleur && chmod 600 before writing
• Updated only after all mentions are processed (not per-reply)

If --headless is set, skip all mentions with a summary message ("Skipped N mentions in headless mode -- engage requires interactive approval"). No replies are posted in headless mode.

Sub-Command Menu

If no sub-command is provided, present options using the AskUserQuestion tool:

Question: "Which community operation would you like to run?"

Options:

1. digest -- Generate a multi-platform community digest
2. health -- Display community health metrics
3. platforms -- List platform configuration status
4. engage -- Reply to recent X/Twitter or Bluesky mentions

Important Guidelines

• Platform detection runs at the start of every sub-command -- use community-router.sh platforms instead of checking env vars directly
• All platform API calls go through community-router.sh <platform> <command> -- do not call platform scripts or APIs directly
• The community-manager agent handles data collection, analysis, and output formatting
• This skill is the entry point; the agent does the work
• Ownership boundary: community = monitoring + engagement. Broadcasting/distribution is handled by the social-distribute skill.
• Posting requires explicit opt-in via environment variables (defense-in-depth guard). Monitoring workflows omit these variables intentionally:
  • LinkedIn: LINKEDIN_ALLOW_POST=true
  • X/Twitter: X_ALLOW_POST=true
  • Bluesky: BSKY_ALLOW_POST=true
• Scheduled-cron context: when the monitor runs via the Inngest cron (apps/web-platform/server/inngest/functions/cron-community-monitor.ts), a platform is enabled only if its required vars are in BOTH Doppler (prd_scheduled) AND the buildSpawnEnv() spawn-env allowlist that forwards env to the spawned claude --print. A platform shown disabled in the digest despite its creds being in Doppler means the allowlist omits them — widen buildSpawnEnv(), not the secret store. See knowledge-base/project/learnings/integration-issues/2026-06-03-platform-disabled-despite-creds-check-spawn-env-allowlist.md.

Platform Surface Check

After a new platform is set up and verified via its setup script (confirmed by the platforms sub-command showing [enabled]), check whether the platform has been added to all public-facing surfaces. Read each file and verify:

File	What to look for
plugins/soleur/docs/_data/site.json	URL entry for the platform
plugins/soleur/docs/pages/community.njk	Card in the Connect section
knowledge-base/marketing/brand-guide.md	Platform handle mention

If any surface is missing, output a warning:

[WARNING] Platform <platform-name> is missing from: <list-of-files>.
These files need updating before the integration is complete.
Consider filing: gh issue create --title 'feat(docs): add <platform-name> to website and brand guide' --milestone 'Post-MVP / Later'

This check does not block provisioning -- it is advisory only. The ops-provisioner agent has a broader version of this check for non-community tools.