DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to get alerted when upstream agent skills change with Agent Skill Sync

Diff the current skills against the last snapshot and record a new one each run.

Short answer: Install the CLI with pipx install agent-skill-sync; then run skillsync check once to record the first snapshot; run skillsync check again after upstream updates to see what changed since the last snapshot. All steps.

Who it is forA developer who pulls third-party or marketplace agent skills and wants to notice changes without rereading everything.

The problemUpstream skill updates land silently, so local copies drift without anyone noticing.

The outcomeA changed-since-last-check report, plus a one-line summary you can run from cron.

What you need first

  • Python 3.11 or newer
  • Local SKILL.md skill folders for Codex, Claude Code or other supported agents
  • pipx or pip to install the agent-skill-sync package

Steps

  1. Install the CLI with pipx install agent-skill-sync.
  2. Run skillsync check once to record the first snapshot.
  3. Run skillsync check again after upstream updates to see what changed since the last snapshot.
  4. Run skillsync check --quiet in a cron job to get a summary line only.

Prompt for your agent

Use the agent-skill-sync repo to report skill changes since the last run. Run `skillsync check --quiet` and write the output line to <log-file>. Expected output: one summary line with counts of changed skills. Verify by running `skillsync check` without --quiet and confirming the detail matches the summary.

Caveat. The first run only records a baseline, so change reports are meaningful from the second run onward.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for kina-cmd/agent-skill-sync and "Get alerted when upstream agent skills change"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer