메뉴
Monitor Bluesky notifications (replies, mentions, quotes) on a schedule. Ready-to-use poller following the pollers.json contract with follow-gate trust tiers. Install from ClawHub or copy into your agent's skills/ folder.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | bluesky-poller |
| description | Monitor Bluesky notifications (replies, mentions, quotes) on a schedule. Ready-to-use poller following the pollers.json contract with follow-gate trust tiers. Install from ClawHub or copy into your agent's skills/ folder. |
Monitors your Bluesky account for new replies, mentions, and quotes. Emits events to the agent only when there's something actionable.
Install from ClawHub:
npx clawhub install bluesky-poller
Or copy this skill directory into your agent's skills/ folder.
After installation, call reload_pollers to register the poller with the scheduler.
The poller reads credentials from the agent's environment (.env file or system env):
| Variable | Required | Description |
|---|---|---|
BLUESKY_HANDLE | yes | Your Bluesky handle (e.g., agent.bsky.social) |
BLUESKY_APP_PASSWORD | yes | App password from Bluesky Settings > App Passwords |
Important: Use a dedicated agent account, not a personal account. The poller doesn't mark notifications as read, but using a separate account keeps things clean.
The skill ships with a default pollers.json that polls every 5 minutes:
{
"pollers": [
{
"name": "bluesky-mentions",
"command": "python poller.py",
"cron": "*/5 * * * *"
}
]
}
Adjust the cron schedule as needed. For lower-traffic accounts, */15 * * * * (every 15 minutes) is fine.
After installation, call reload_pollers to register the poller with the scheduler.
The poller emits events for:
Each event includes the author, text, and URIs needed to respond.
Likes and follows are ignored — they don't require agent action.
Events from accounts you follow are emitted as normal prompts. Events from accounts you don't follow are prefixed with [PERMISSION NEEDED] — the agent should ask the operator before engaging.
The follow list is cached for 1 hour to avoid API rate limits.
Requires the atproto Python package:
pip install atproto
Or with uv:
uv add atproto
How to choose between markdown, HTML messages, and UI plugins in the local web chat — and how to render each well. Use whenever you are about to call `send_message` to a web-chat channel, especially when the content has structure (rows, columns, statuses, a state machine, multiple linked things) or when the right answer is "let me show you", not "let me tell you". Do not use for Discord channels — HTML is rejected there.
Create and manage runtime command hooks declared in skills/*/hooks.json. Use when the user asks to intercept tool calls, augment prompts, audit or mutate tool arguments/results, add startup/shutdown scripts, or debug hook behavior.
Index of recurring problem shapes — environmental awareness (world-scanning, OS event hooks, browser automation), communication (messaging, multi-agent handoff, async waits), coordination between parallel things (avoiding collisions, oscillation, double-work), and self-correction (circuit-breaker, try-harder). Use when designing a non-trivial workflow, when the same shape just happened twice, or when the answer to "what should I do here?" isn't obvious. Don't read on every turn.
Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.
Diagnose agent behavior using event logs, journal history, and scheduler state. Use when you need to understand why something went wrong, review your own patterns, audit scheduled jobs, or debug communication issues. Do not use for one-off messaging or memory management (use the memory skill instead).
Guide for the first days with a new human. Use when: the `init` memory block exists (pointing you here), you have no persona/communication blocks yet, or a human explicitly asks about setup. This skill is about having good conversations — not filling out forms.