Agent skill

Sync Check

by ItamarZand88 in ItamarZand88/CLI-Anything-WEB

Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync.

MITAuto-check passedDevelopment

Install Sync Check

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sync-check .claude/skills/sync-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .claude/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sync-check .agents/skills/sync-check && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .agents/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sync-check .cursor/skills/sync-check && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .cursor/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ItamarZand88/CLI-Anything-WEB.git --path .claude/skills/sync-check

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sync-check .gemini/skills/sync-check && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .gemini/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sync-check .github/skills/sync-check && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .github/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ItamarZand88/CLI-Anything-WEB sync-check --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEB.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sync-check .opencode/skills/sync-check && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sync-check" agent skill from https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/.claude/skills/sync-check into .opencode/skills/sync-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-check", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sync-check
GitHub stars: 231
Token cost: ~1.7k tokens
SKILL.md length: 387 words
Files: 1
Skills in repo: 42
Repo updated: Oct 1, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync.

Works in 6 steps: Identify What Changed → Classify the Change → Run Verification Commands → …
Says sync check
SKILL.md covers How to Use, The Dependency Web, Sync Check Procedure and Quick Reference: File Locations
Calls git

What it does

Sync Check is an agent skill from ItamarZand88/CLI-Anything-WEB. Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs", "propagate changes", "did I forget to update", "what else needs updating", or "before I commit".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Operations and SOPs, Technical documentation and Debugging. The repository describes itself as: Claude Code plugin that generates production-grade Python CLIs for any web app. 20 CLIs and counting. The licence is MIT.

When your agent uses it

Says sync check
Propagate changes
Did I forget to update
What else needs updating

Example prompts

“sync check”
“update docs”
“propagate changes”
“/sync-check”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Identify What Changed
Classify the Change
Run Verification Commands
Check Each Downstream File
Plugin Lesson Check (Bug Fixes Only)
Verify with --json

What it can do on your machine

Read from SKILL.md and the folder at commit 931e201. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sync Check loads about 1.7k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 387 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~105
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ItamarZand88/CLI-Anything-WEB at commit 931e201, republished under its MIT licence (© ItamarZand88). 387 words, ~1,690 tokens.

Download SKILL.mdSave it as .claude/skills/sync-check/SKILL.md (or your agent's skills folder).

name: sync-check
description: Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs", "propagate changes", "did I forget to update", "what else needs updating", or "before I commit".

Sync Check

After any code change, verify all related files are synchronized. This catches the "fixed the bug but forgot to update the skill/SOP/plugin docs" problem.

How to Use

Run /sync-check after making changes. It will:

Detect what changed (from git diff or conversation context)
Check all downstream files that depend on the change
Report what's out of sync
Offer to fix each one

The Dependency Web

Every change touches multiple files. Here's the full map:

Code Change → Documentation Updates

CLI code changed (client.py, commands/*.py, auth.py)
  ├── .claude/skills/<app>-cli/SKILL.md     (commands, output fields, examples)
  ├── <app>/agent-harness/<APP>.md           (SOP: rpcid table, data models)
  ├── <app>/agent-harness/cli_web/<app>/README.md  (usage examples, deps)
  ├── <app>/agent-harness/setup.py           (dependencies)
  └── <app>_cli.py _print_repl_help()        (REPL help must list all commands)

Bug Fix → Plugin Lesson Updates

Bug found and fixed in any CLI
  ├── Was it a pattern that could repeat in future CLIs?
  │   YES → Add to the relevant plugin reference file:
  │   ├── auth-strategies.md "Known Pitfalls" table    (auth bugs)
  │   ├── google-batchexecute.md                       (RPC/batchexecute bugs)
  │   ├── ssr-patterns.md "HTML Scraping Pitfalls"     (scraping bugs)
  │   ├── protection-detection.md                      (anti-bot/WAF bugs)
  │   └── traffic-patterns.md                          (protocol detection bugs)
  │
  ├── Is it a universal lesson (applies to ALL CLIs)?
  │   YES → Add to HARNESS.md "Lessons Learned" cross-reference table
  │
  └── Does it change a critical convention?
      YES → Update CLAUDE.md "Critical Conventions" section

New Command Added → Full Update Chain

New command added to a CLI
  ├── .claude/skills/<app>-cli/SKILL.md     (add command + options + output fields)
  ├── <app>_cli.py _print_repl_help()        (add to REPL help)
  ├── <app>/agent-harness/<APP>.md           (add endpoint to API map)
  ├── README.md (repo root)                  (if it changes the CLI's capabilities)
  └── Run: cli-web-<app> <new-cmd> --json    (verify output matches skill docs)

Auth/Protection Change → Cross-Cutting Updates

Auth behavior changed
  ├── auth-strategies.md                     (patterns, pitfalls, code examples)
  ├── HARNESS.md lessons table               (cross-reference)
  ├── testing/SKILL.md                       (auth prereqs)
  ├── standards/SKILL.md                     (smoke test steps)
  └── CLAUDE.md                              (critical conventions)

Anti-bot/protection change (e.g., httpx → curl_cffi)
  ├── protection-detection.md                (strategy, detection)
  ├── <app>/agent-harness/<APP>.md           (site profile, HTTP client)
  ├── <app>/agent-harness/setup.py           (dependencies)
  ├── <app>/agent-harness/cli_web/<app>/README.md  (deps section)
  ├── CLAUDE.md generated CLIs table         (protocol column)
  └── README.md (repo root)                  (protocol column)

Sync Check Procedure

Step 1: Identify What Changed

bash

# Check git diff for changed files
git diff --name-only HEAD
# Or if already committed:
git diff --name-only HEAD~1

Step 2: Classify the Change

Ask yourself:

Which CLI? Extract from file path (booking, futbin, notebooklm, etc.)
What type of change?
- Bug fix → needs lesson propagation?
- New command → needs skill + REPL + SOP update?
- Auth change → cross-cutting update?
- Dependency change → setup.py + README?
- RPC/protocol change → SOP + batchexecute ref?

Step 3: Run Verification Commands

For the affected CLI:

bash

# Verify commands match skill docs
cli-web-<app> --help
cli-web-<app> <subgroup> --help

# Verify output fields match skill docs
cli-web-<app> <primary-command> --json | head -20

# Verify auth works (if auth CLI)
cli-web-<app> auth status --json

Step 4: Check Each Downstream File

For each file in the dependency chain above:

Read the file
Find the section that relates to your change
Verify it matches the current code behavior
Update if stale

Show full SKILL.md (186 more words)Show less

Step 5: Plugin Lesson Check (Bug Fixes Only)

If you fixed a bug, ask:

"Would this bug happen again if someone generated a new CLI tomorrow?"

If YES, add it to the appropriate plugin reference file:

Bug Category	Add To
Auth (cookies, login, tokens, refresh)	`auth-strategies.md` Known Pitfalls
RPC (wrong IDs, wrong params, parsing)	`google-batchexecute.md`
HTML scraping (selectors, noise, slugs)	`ssr-patterns.md` HTML Scraping Pitfalls
Anti-bot (blocked, 401, 403, challenges)	`protection-detection.md`
Output (raw data leak, wrong fields)	`testing/SKILL.md` CLI Output Sanity Checks
Downloads (URLs, cookies, formats)	`auth-strategies.md` Known Pitfalls
General (UTF-8, Windows, rate limits)	HARNESS.md Lessons table + relevant ref

Format for Known Pitfalls: | Symptom | Cause | Fix |

Step 6: Verify with --json

After all updates, run one command per affected CLI with --json to confirm the output still matches what the skill documents.

Quick Reference: File Locations

What	Where
CLI skills	`.claude/skills/<app>-cli/SKILL.md`
CLI SOPs	`<app>/agent-harness/<APP>.md`
CLI READMEs	`<app>/agent-harness/cli_web/<app>/README.md`
Plugin capture skill	`cli-anything-web-plugin/skills/capture/SKILL.md`
Plugin methodology skill	`cli-anything-web-plugin/skills/methodology/SKILL.md`
Plugin testing skill	`cli-anything-web-plugin/skills/testing/SKILL.md`
Plugin standards skill	`cli-anything-web-plugin/skills/standards/SKILL.md`
Auth strategies ref	`cli-anything-web-plugin/skills/methodology/references/auth-strategies.md`
Batchexecute ref	`cli-anything-web-plugin/skills/methodology/references/google-batchexecute.md`
SSR patterns ref	`cli-anything-web-plugin/skills/methodology/references/ssr-patterns.md`
Protection ref	`cli-anything-web-plugin/skills/capture/references/protection-detection.md`
HARNESS.md	`cli-anything-web-plugin/HARNESS.md`
CLAUDE.md	`CLAUDE.md` (repo root)
README.md	`README.md` (repo root)

Files

Just SKILL.md in .claude/skills/sync-check of ItamarZand88/CLI-Anything-WEB.

Open the folder on GitHubat commit 931e201

Compare with similar skills

Sync Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sync Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sync Check this skillItamarZand88/CLI-Anything-WEB	231	—	~1.7k	Automated safety check: Pass	MIT	8 days ago
Nemo Rl DocsNVIDIA/skills	3.5k	—	~357	Automated safety check: Pass	Apache-2.0	today
Code Review Graph Navigatorhandsontable/handsontable	22k	—	~939	Automated safety check: Pass	Custom licence	today
Analyze Projectlllllllama/RigorPilot-Skills	497	1 repos	~519	Automated safety check: Pass	MIT	15 days ago
Andrej Karpathy Skillduolahypercho/andrej-karpathy-skills	249	—	~793	Automated safety check: Pass	MIT	4 mo ago
Enforce Rules For Typescriptmoeru-ai/airi	50k	—	~3.4k	Automated safety check: Pass	MIT	today

Similar skills

Nemo Rl Docs
NVIDIA/skills
Official
Documentation conventions for NeMo-RL. An agent skill from NVIDIA/skills.
3.5k GitHub stars~357 tokensUpdated today
DevelopmentAuto-check passed
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
22k GitHub stars~939 tokensUpdated today
DevelopmentAuto-check passed
Analyze Project
lllllllama/RigorPilot-Skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
497 GitHub starsUsed in 1 repo~519 tokens
DevelopmentAuto-check passed
Andrej Karpathy Skill
duolahypercho/andrej-karpathy-skills
Apply Andrej Karpathy-inspired coding-agent guidelines in Codex.
249 GitHub stars~793 tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Enforce Rules For Typescript
moeru-ai/airi
Enforce AIRI's TypeScript and Vue source rules for imports, naming, comments, JSDoc, fallbacks, stateful and protocol code, and module design.
50k GitHub stars~3.4k tokensUpdated today
DevelopmentAuto-check passed
Verdaccio Change Implementation
verdaccio/verdaccio
A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.
18k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed

More from ItamarZand88/CLI-Anything-WEB

All 42 skills in this repo

Standards
ItamarZand88/CLI-Anything-WEB
Runs Phase 4 review/publish/verify for a cli-web- CLI: implementation review by 3 parallel agents, the tiered quality checklist (Tier 1 critical fail-fast, then comprehensive), pip install + smoke…
231 GitHub stars~4.2k tokensUpdated 8 days ago
Auto-check passed
Airbnb CLI
ItamarZand88/CLI-Anything-WEB
Searches Airbnb from the terminal via cli-web-airbnb — find stays by location, dates, and filters; get listing details, guest reviews, and availability calendars; autocomplete location names.
231 GitHub stars~801 tokensUpdated 8 days ago
Auto-check passed
Amazon CLI
ItamarZand88/CLI-Anything-WEB
Searches Amazon from the terminal via cli-web-amazon — product search, product details by ASIN, Best Sellers by category, and autocomplete suggestions.
231 GitHub stars~570 tokensUpdated 8 days ago
Auto-check passed
Booking CLI
ItamarZand88/CLI-Anything-WEB
Searches Booking.com from the terminal via cli-web-booking — find hotels, apartments, and hostels by destination, dates, and guests; get property details by slug; resolve destination names to IDs.
231 GitHub stars~776 tokensUpdated 8 days ago
Auto-check passed
Booking CLI
ItamarZand88/CLI-Anything-WEB
Use cli-web-booking to search Booking.com for hotels, apartments, hostels, and accommodations by destination, dates, and filters.
231 GitHub stars~970 tokensUpdated 8 days ago
Auto-check passed
Capitoltrades CLI
ItamarZand88/CLI-Anything-WEB
Queries US congressional stock trades (STOCK Act disclosures) on capitoltrades.com via the cli-web-capitoltrades command-line tool — trades with rich filters, politician profiles and leaderboards…
231 GitHub stars~971 tokensUpdated 8 days ago
Auto-check passed

Questions about Sync Check

What does Sync Check do?

Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Sync Check is an agent skill from ItamarZand88/CLI-Anything-WEB. Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync.

When should I use Sync Check?

Sync Check fits situations like: says sync check; propagate changes; did I forget to update; what else needs updating.

How do I install Sync Check in Claude Code?

Run `npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a claude-code`. Or copy the skill folder (.claude/skills/sync-check in ItamarZand88/CLI-Anything-WEB) into .claude/skills/sync-check in your project. Claude Code loads it when a task matches its description.

How do I install Sync Check in Codex?

Run `npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a codex`. Or copy the skill folder (.claude/skills/sync-check in ItamarZand88/CLI-Anything-WEB) into .agents/skills/sync-check in your project. Codex loads it when a task matches its description.

Can I use Sync Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ItamarZand88/CLI-Anything-WEB --skill sync-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-check, .gemini/skills/sync-check, .github/skills/sync-check and .opencode/skills/sync-check in your project.

What does Sync Check need to run?

Going by SKILL.md and its folder, Sync Check needs the command-line tools its instructions call (git).

Does Sync Check access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sync Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sync Check use?

Sync Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sync Check use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sync Check?

Skills that share tags, products or a category with Sync Check: Nemo Rl Docs (NVIDIA/skills, 3.5k stars), Code Review Graph Navigator (handsontable/handsontable, 22k stars), Analyze Project (lllllllama/RigorPilot-Skills, 497 stars) and Andrej Karpathy Skill (duolahypercho/andrej-karpathy-skills, 249 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sync Check?

ItamarZand88 (a GitHub user) maintains it in ItamarZand88/CLI-Anything-WEB, which has 231 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 1, 2026.

Source: ItamarZand88/CLI-Anything-WEB on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sync Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Sync Check

How to Use

The Dependency Web

Code Change → Documentation Updates

Bug Fix → Plugin Lesson Updates

New Command Added → Full Update Chain

Auth/Protection Change → Cross-Cutting Updates

Sync Check Procedure

Step 1: Identify What Changed

Step 2: Classify the Change

Step 3: Run Verification Commands

Step 4: Check Each Downstream File

Step 5: Plugin Lesson Check (Bug Fixes Only)

Step 6: Verify with --json

Quick Reference: File Locations

Files

Compare with similar skills

Similar skills

More from ItamarZand88/CLI-Anything-WEB

Related

Questions about Sync Check