菜单
List all configured Repost-with-agent pairs with their mode, runMode, schedule, and last-run summary. Use when the user asks "what pairs are configured?", "list my repost pairs", or "show me the repost-with-agent state".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run Repost-with-agent for one pair, all enabled pairs, or an explicit subset — scrape source, dedupe (local + destination), expand URLs, publish when allowed, append history, and notify the user. Use when the user asks to "run pair <id>", "post the latest from <pair>", "tick the <pair-id> pair", "run all pairs", or invokes /repost-run. Also invoked by scheduled agents for listen-for-future pairs.
Process one selected source item across every enabled destination pair for that source, especially scheduled/backfill slots. Use when the user or scheduler asks to backfill/catch up a source platform such as LinkedIn to all configured destinations, or when a partial fanout needs resume.
User-configured allow/skip rules for Repost-with-agent candidates. Apply before dedupe/publish so Ethan can block categories such as X video/livestream promos without polluting publish ledgers.
Walk back through historical source posts and repost the missing ones (newest-first). Use when the user asks to "backfill <pair>", "catch up the destination", "repost the last N posts", or invokes /repost-backfill. Multi-post operation with rate-limiting between publishes.
Install current-harness scheduler entries for Repost-with-agent. Default listen mode is one fresh agent/subagent running /repost-run all across enabled listen-for-future pairs; source backfills use source-item fanout; custom per-pair, subset, dry/preview, and arbitrary cadence jobs are supported when the user asks.
Create or save a new Repost-with-agent source → destination pair. Use when the user wants to set up cross-posting between websites the agent can safely operate through a logged-in browser (with documented examples for LinkedIn, X, Bluesky, Threads, and Facebook), or asks to "configure a repost pair", "set up reposting", "wire up cross-posting", or "add a new pair to repost-with-agent / repost_with_agent".
| name | repost-pair-list |
| description | List all configured Repost-with-agent pairs with their mode, runMode, schedule, and last-run summary. Use when the user asks "what pairs are configured?", "list my repost pairs", or "show me the repost-with-agent state". |
| when_to_trigger | User asks to list, show all, or summarize the configured repost pairs. |
Read ~/.repost-with-agent/pairs.json and summarize each configured pair.
~/.repost-with-agent/pairs.json. If the file does not exist, tell the user "No pairs configured yet. Run /pair create to set one up." and stop.ls -t ~/.repost-with-agent/pairs.json.bak.* via Bash), and stop.pairs.pairs:
id, name, enabled, mode, runMode, source.platform, source.url, destination.platform, destination.accountHint, schedule.posted.jsonl to count entries and grab the most-recent timestamp + destination URL: tail -1 ~/.repost-with-agent/pairs/<id>/posted.jsonl (Bash). If the file doesn't exist, "No posts yet."schedulerJobs exists, summarize active/inactive jobs after the pair list (id, enabled, scope, pairIds, publishMode, schedule, host jobName). This is advisory metadata; do not treat it as proof the host scheduler is installed.**linkedin-to-x** (enabled · live-approved · listen-for-future)
Source: linkedin · https://www.linkedin.com/in/ethansk
Destination: x · @REEEthan_YT
Schedule: cron · daily / every 24h (0 10 * * *) · Europe/London
History: 11 posts · last 2026-04-30T22:53:11Z → https://x.com/REEEthan_YT/status/...
**bluesky-to-threads** (disabled · preview-only · backfill)
Source: bluesky · https://bsky.app/profile/ethan.bsky.social
Destination: threads · @ethanskattan
Schedule: manual
History: 0 posts · no posts yet
enabled first in the parenthesized status line so the user can
see at a glance which pairs are armed.posted.jsonl entries and the most-recent destination URL.schedulerJobs exists, include a short Scheduler jobs: block so custom all-pairs/per-pair/subset/dry configurations are visible.This is a read-only inspection skill. Do not Telegram on this skill — list operations are a quiet local query.