Skills Guide

Sync Status

VerifiedCaution

Show where a codebase's tokens and its connected Paper file disagree, then offer to normalize. Use to check sync status.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#design-tokens#drift-detection#read-only#sync#design-system

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Runs a read-only diagnostic script that compares the tokens a codebase defines against those in a connected Paper file, then reports the drift in both directions before offering to normalize.

Strengths

  • Structured JSON report separating onlyInCode, onlyInDesign, differ, and declined tokens
  • Writes nothing: it only computes drift, leaving the reconciliation decision to the user
  • Handles failure modes explicitly (missing config, no fileId, Paper daemon failure) with dedicated exit codes
  • Surfaces both reconciliation paths (normalize-to-code / normalize-to-design) without choosing on the user's behalf

Limitations

  • Requires a valid token-bridge.config.json and a Paper file already linked through the connect skill
  • Not exhaustive: shadows and motion tokens are reported as declined because Paper cannot represent them
  • Needs the Python script and the Paper daemon to be reachable in the runtime environment
When to use it

When someone asks for sync status, whether code and design agree, what has drifted, or which direction to reconcile in.

When not to use it

When the codebase has not been connected to a Paper file yet, or when you want changes applied directly instead of inspecting drift first.

Security analysis

Caution
Quality score85/100

The skill is described as a read-only drift check: it runs a local Python script, reads a config, and compares values without writing. No destructive commands, obfuscation, secret exfiltration, or safety-disabling instructions appear, and it explicitly refuses to auto-apply changes. Because it uses Bash plus a daemon connection and ships an unshown script, it warrants caution rather than a clean 'safe' rating.

Findings
  • •Invokes a bundled Python script via Bash (${CLAUDE_PLUGIN_ROOT}/lib/status.py) whose source is not shown, so the 'read-only' claim can't be independently verified
  • •Reads token-bridge.config.json from an arbitrary --repo path and talks to a 'Paper daemon', implying local IPC/possible network access
  • •The --repo path is user-supplied and forwarded to the script; no validation described, though as a Python arg the injection surface is minimal
How this analysis is made

Examples

Check sync status
Is my codebase in sync with the connected Paper design file? Show me what's drifted.
Explain the drift
Run the status check on /path/to/my-app and break down which tokens exist only in code versus only in design, and which ones differ in value.
Decide a direction
The status report shows some tokens differ between code and Paper — walk me through which normalize direction to pick and why.

name: status description: > Show where a codebase's tokens and its connected Paper file disagree, in both directions, without writing anything — then offer to normalize. Use when someone asks for the sync status, whether code and design are in sync, what's drifted, or which way to reconcile. Reads the connection from the codebase's token-bridge.config.json (via --repo). allowed-tools: Bash, Read

Sync status

The script computes the drift read-only; your job is to run it, present the drift plainly, and then offer the two normalize directions — never apply automatically.

Workflow

  1. Run the status script:

    python3 "${CLAUDE_PLUGIN_ROOT}/lib/status.py" run --repo /path/to/codebase

  2. Read the exit code and JSON report:

    • Exit 2 (refused): no config / no fileId under --repo (error is no_config / no_target_file / bad_config). Tell the user to run connect first, and surface note.
    • Exit 4 (error): the source read or the Paper daemon failed. Relay it.
    • Exit 0 (ok): report the drift from the fields below.

  3. Present the drift plainly (nothing was written):

    • inSync — when true, code and design already agree; say so and stop.
    • onlyInCode — tokens the code defines that the Paper file lacks.
    • onlyInDesign — tokens the Paper file has that the code lacks (within the configured prefix).
    • differ — tokens both carry with different values (a genuine conflict to resolve deliberately).
    • declined — source tokens Paper can't represent (shadows, motion), for context.

  4. Then offer the two directions (this is the "which way?" decision — do not pick for the user):

    • To make the design match the code (code wins): run normalize-to-code.
    • To make the code match the design (design wins): run normalize-to-design.

    If the user chooses one, invoke that skill with the same --repo. Point out that differ tokens are where the two directions actually disagree — the choice matters most there.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/sync-status-mrwakbmq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/sync-status-mrwakbmq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sync-status-mrwakbmq/download' --output '.skill-downloads/sync-status-mrwakbmq/SKILL.md.part' && mv '.skill-downloads/sync-status-mrwakbmq/SKILL.md.part' '.skill-downloads/sync-status-mrwakbmq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/sync-status-mrwakbmq/SKILL.md' && test -s '.skill-downloads/sync-status-mrwakbmq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/status' && cp -R '.skill-downloads/sync-status-mrwakbmq' '.claude/skills/status'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/sync-status-mrwakbmq'

openskills read 'sync-status-mrwakbmq'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/sync-status-mrwakbmq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot