菜单
Show full details for one Repost-with-agent pair, including config, recent posts, recent audit events, and learnings. Use when the user asks "show me <pair-id>", "what's the state of <pair-id>", or "audit <pair-id>".
用 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-show |
| description | Show full details for one Repost-with-agent pair, including config, recent posts, recent audit events, and learnings. Use when the user asks "show me <pair-id>", "what's the state of <pair-id>", or "audit <pair-id>". |
| when_to_trigger | User asks to inspect, audit, or show a specific pair. |
Show full details for a specific pair: configuration, recent post history, recent audit events, and free-form learnings.
~/.repost-with-agent/pairs.json.id. If not found, list available ids and stop.jq via Bash for clean output:
jq '.pairs[] | select(.id == "<id>")' ~/.repost-with-agent/pairs.json).schedulerJobs exists, show jobs whose scope is all-enabled or whose pairIds includes this pair id. Label these as advisory scheduler metadata, not proof the host job is installed.~/.repost-with-agent/pairs/<id>/posted.jsonl
via tail -10 (Bash). For each entry, format as:
<ts> <sourceItemId> → <destinationUrl>.~/.repost-with-agent/pairs/<id>/audit.jsonl
via tail -20 (Bash). Include only event + ts + a short reason.~/.repost-with-agent/pairs/<id>/learnings.md (if exists, may be
empty).
## … entries verbatim under a "Recent learnings"
heading (newest at the bottom — the file is append-only so the last 5
## headings ARE the most recent). Use a small awk / tail pipe to
extract them; one practical approach is to grep -n '^## ' learnings.md | tail -5 to find the line numbers of the last 5 headings,
then sed -n '<first>,$p' from the earliest of those.(no learnings recorded yet) instead.--full-learnings or similar),
dump the entire file verbatim under "All learnings" instead of the
last-5 tail.=== Pair: <id> ===
Name: <name>
Enabled: <true|false>
Mode: <mode>
Run mode: <runMode>
Source: <platform> · <url>
Destination: <platform> · <accountHint>
Schedule: <schedule>
Scheduler: <matching schedulerJobs summary, if any>
Created: <createdAt>
Updated: <updatedAt>
=== Recent posts (last 10) ===
2026-04-30T22:53Z urn:li:activity:7000 → https://x.com/.../status/...
...
=== Recent audit (last 20) ===
2026-04-30T22:53:11Z pair.publish.success Posted to x.com.
2026-04-30T22:53:09Z pair.publish.url_expanded https://lnkd.in/abc → https://example.com/article
...
=== Recent learnings (last 5) ===
## 2026-05-12 14:22 — LinkedIn recent-activity pagination cap dropped to ~60
<body>
## 2026-05-09 09:14 — X composer textarea stopped auto-focusing
<body>
...
If --full-learnings was passed, replace the last-5 tail with the full
file contents under === All learnings ===.
skills/repost-learnings/SKILL.md — format + lifecycle of the
learnings.md file this skill surfaces.Read-only inspection. No Telegram on this skill.