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.
From soleurnpx claudepluginhub jikig-ai/soleur --plugin soleurThis skill uses the workspace's default tool permissions.
scripts/bsky-community.shscripts/bsky-setup.shscripts/community-router.shscripts/discord-community.shscripts/discord-setup.shscripts/github-community.shscripts/hn-community.shscripts/linkedin-community.shscripts/linkedin-setup.shscripts/x-community.shscripts/x-setup.shManage 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 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 is centralized in community-router.sh. Run at the start of every sub-command:
bash 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.
Platform scripts are located at plugins/soleur/skills/community/scripts/:
digestGenerate a multi-platform community digest. Spawns the community-manager agent with digest instructions.
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."knowledge-base/support/community/YYYY-MM-DD-digest.mdIf --headless is set, skip the Discord posting approval gate (the agent handles this).
healthDisplay community health metrics across all enabled platforms. Spawns the community-manager agent with health instructions.
community-manager with prompt: "Display community health metrics. Enabled platforms: [list]. Show metrics from each enabled platform."platformsList all platforms with their configuration status. Does NOT spawn an agent -- runs directly.
bash plugins/soleur/skills/community/scripts/community-router.sh platformsplugins/soleur/skills/community/scripts/discord-setup.sh to configure"plugins/soleur/skills/community/scripts/x-setup.sh validate-credentials to verify, or x-setup.sh write-env to save credentials"plugins/soleur/skills/community/scripts/bsky-setup.sh write-env to save credentials, or bsky-setup.sh verify to test"plugins/soleur/skills/community/scripts/linkedin-setup.sh generate-token to set up credentials, or linkedin-setup.sh verify to test"engageReply 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):
.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).community-manager with prompt: "Engage with recent X/Twitter mentions. Use Capability 4: Mention Engagement. Max results: [N]. Since ID: [ID or none]."community-router.sh x fetch-mentionsknowledge-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.community-router.sh x post-tweet --reply-to <mention_id>newest_id from the fetch response and displays a session summary (processed, posted, skipped counts).Since-id state file:
.soleur/x-engage-since-id (relative to repo root)mkdir -p .soleur && chmod 600 before writingFree 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):
BSKY_HANDLE + BSKY_APP_PASSWORD).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.community-manager with prompt: "Engage with recent Bluesky mentions. Use Capability 4: Bluesky Mention Engagement. Limit: [N]. Cursor: [cursor or none]."community-router.sh bsky get-notificationsknowledge-base/marketing/brand-guide.md sections ## Voice and ## Channel Notes > ### Bluesky). 300-character limit.community-router.sh bsky post "<text>" --reply-to-uri <uri> --reply-to-cid <cid>.soleur/bsky-engage-cursor) and displays a session summary.Bluesky cursor state file:
.soleur/bsky-engage-cursor (relative to repo root)mkdir -p .soleur && chmod 600 before writingIf --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.
If no sub-command is provided, present options using the AskUserQuestion tool:
Question: "Which community operation would you like to run?"
Options:
community-router.sh platforms instead of checking env vars directlycommunity-router.sh <platform> <command> -- do not call platform scripts or APIs directlycommunity-manager agent handles data collection, analysis, and output formattingsocial-distribute skill.LINKEDIN_ALLOW_POST=trueX_ALLOW_POST=trueBSKY_ALLOW_POST=trueAfter 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.