promote
GitHub Promotion Workflow
This skill targets the open issues of same-space projects (local coding agent ↔ IM / mobile / remote console) — that's where users have already self-identified as needing this category of tool. We share pikiclaw as another option that may help; we do not position against the host project.
1. Context Check (Anti-Duplication)
Before doing anything, ALWAYS read the registry of already replied issues to ensure we do not spam or reply to the same issue twice.
- Registry Path:
.pikiclaw/skills/promote/replied_issues.txt - Action: Read this file and keep the URLs in context.
2. Primary Path — Same-Space Project Issues
This is the main targeting strategy. Walk the issue trackers of the peer projects below — their users already feel the pain pikiclaw addresses. Bucket A repos are pikiclaw's same channels (Telegram / Feishu / WeChat); Bucket B repos are different channels (Discord / Slack / DingTalk) — replies in Bucket B are only valid for channel-agnostic topics (MCP bridge, session management, dashboard, multi-agent, watchdog) where pikiclaw's general capabilities apply regardless of frontend.