New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sync Agent Symlinks

by LIDR-academy in LIDR-academy/AI4Devs-LTI-extended

Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames).

MITAuto-check passed

Install Sync Agent Symlinks

skills CLI
$ npx skills add LIDR-academy/AI4Devs-LTI-extended --skill sync-agent-symlinks -a claude-code

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

GitHub CLI
$ gh skill install LIDR-academy/AI4Devs-LTI-extended sync-agent-symlinks --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/LIDR-academy/AI4Devs-LTI-extended.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ai-specs/skills/sync-agent-symlinks .claude/skills/sync-agent-symlinks && 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/

Facts

Skill name
sync-agent-symlinks
GitHub stars
278
Token cost
~1k tokens
SKILL.md length
417 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames).

  • Works in 5 steps: Build inventories → Compute sync plan → Apply sync safely → …
  • Skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks
  • SKILL.md covers Scope and Safety Rules, Workflow, Add/Remove Scenarios and Command Patterns (Reference), plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sync Agent Symlinks is an agent skill from LIDR-academy/AI4Devs-LTI-extended. Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames). Use when skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks.

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

The repository describes itself as: Repository with several experiments from live sessions. The licence is MIT.

When your agent uses it

  • Skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks

Example prompts

  • “/sync-agent-symlinks”

Workflow steps

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

  1. Build inventories
  2. Compute sync plan
  3. Apply sync safely
  4. Verify integrity
  5. Report results

What it can do on your machine

Read from SKILL.md and the folder at commit 9ff9a80. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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 Agent Symlinks loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 417 words of instructions outside code blocks.

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

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 LIDR-academy/AI4Devs-LTI-extended at commit 9ff9a80, republished under its MIT licence (© LIDR-academy). 417 words, ~1,015 tokens.

Download SKILL.mdSave it as .claude/skills/sync-agent-symlinks/SKILL.md (or your agent's skills folder).
name
sync-agent-symlinks
description
Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames). Use when skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks.
author
LIDR.co
version
1.0.0

Keep agent-facing skill structures synchronized with ai-specs/skills as the canonical source.

Use this skill after any change in ai-specs/skills (new skill, removed skill, renamed skill, moved skill), especially when you need to avoid stale or broken symlinks.

Scope and Safety Rules

  • Canonical source is ai-specs/skills.
  • Mirror targets are:
    • .claude/skills
    • .cursor/skills
  • Manage only entries that are symlinks to ../../ai-specs/skills/<skill-name>.
  • Do not delete non-symlink directories in mirror targets unless the user explicitly asks.
  • Never overwrite a real directory automatically; report it as a conflict.

Workflow

Step 1 - Build inventories

Collect three inventories:

  1. Canonical skills from ai-specs/skills/*/SKILL.md
  2. Mirror entries in .claude/skills
  3. Mirror entries in .cursor/skills

From mirror entries, classify:

  • linked: valid symlink pointing to existing canonical skill
  • broken: symlink target missing
  • orphan: symlink points to canonical namespace but skill no longer exists
  • conflict: non-symlink entry with same name as canonical skill
  • external: entry not managed by canonical symlink policy (leave unchanged)
Step 2 - Compute sync plan

For each mirror target:

  • to_add: canonical skills missing in mirror target
  • to_fix: broken canonical symlinks that should be recreated
  • to_remove: orphan canonical symlinks with no canonical source
  • to_skip: conflicts and external entries (report only)
Step 3 - Apply sync safely

Apply changes in this order:

  1. Add missing symlinks:
    • <mirror>/<skill-name> -> ../../ai-specs/skills/<skill-name>
  2. Fix broken canonical symlinks:
    • Remove broken link and recreate the same canonical link
  3. Remove orphan canonical symlinks:
    • Remove symlink only if it points to canonical namespace and skill is gone

Never remove:

  • non-symlink directories
  • files not under canonical symlink policy
Show full SKILL.md (167 more words)Show less
Step 4 - Verify integrity

After changes:

  • Confirm every canonical skill exists in both mirrors as a valid symlink, or is explicitly listed as conflict.
  • Confirm no broken canonical symlinks remain.
  • Confirm external entries remain untouched.
Step 5 - Report results

Return a concise sync report:

  • Canonical skills count
  • Per mirror target:
    • added
    • fixed
    • removed
    • conflicts
    • skipped external entries
  • Remaining blockers (if any)

Add/Remove Scenarios

Scenario A - New skill added in ai-specs

Expected behavior:

  • Add missing symlink in .claude/skills
  • Add missing symlink in .cursor/skills
  • Verify both links resolve to canonical folder
Scenario B - Skill removed from ai-specs

Expected behavior:

  • Remove orphan canonical symlink from .claude/skills
  • Remove orphan canonical symlink from .cursor/skills
  • Keep non-canonical directories untouched and report them

Command Patterns (Reference)

Use equivalent commands for your environment:

bash
# list canonical skill directories (names with SKILL.md)
ls ai-specs/skills

# inspect mirror entries with link metadata
ls -la .claude/skills
ls -la .cursor/skills

# add canonical link
ln -s ../../ai-specs/skills/<skill-name> .claude/skills/<skill-name>
ln -s ../../ai-specs/skills/<skill-name> .cursor/skills/<skill-name>

# remove orphan canonical link
rm .claude/skills/<skill-name>
rm .cursor/skills/<skill-name>

Red Flags

Never:

  • treat ai-specs as non-canonical
  • auto-delete real directories in mirror targets
  • leave broken canonical symlinks after sync
  • silently skip conflicts without reporting

Always:

  • analyze before changing
  • apply minimal safe changes
  • preserve non-canonical entries
  • provide a final sync report with blockers

© LIDR-academy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ai-specs/skills/sync-agent-symlinks of LIDR-academy/AI4Devs-LTI-extended.

Open the folder on GitHubat commit 9ff9a80

Compare with similar skills

Sync Agent Symlinks 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 Agent Symlinks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sync Agent Symlinks this skillLIDR-academy/AI4Devs-LTI-extended278—~1kAutomated safety check: PassMIT
Spec Writergarrytan/gstack136k—~14kAutomated safety check: NotesMIT
Sync Specsnexu-io/nexu3.3k—~1.2kAutomated safety check: PassMIT
I18n Syncaffaan-m/ECC276k—~1.8kAutomated safety check: PassMIT
Specgarden-co/classic-jazz2.5k—~1.3kAutomated safety check: PassMIT
React Syncvercel/next.js143k—~486Automated safety check: PassMIT

Similar skills

  • Spec Writer

    garrytan/gstack

    Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.

    136k GitHub stars~14k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Sync Specs

    nexu-io/nexu

    A skill your agent uses when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

    3.3k GitHub stars~1.2k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • I18n Sync

    affaan-m/ECC

    Translate and synchronize application JSON locale files using source-key usage, project terminology, and focused validation.

    276k GitHub stars~1.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Spec

    garden-co/classic-jazz

    Implement features using Spec Driven Development (SDD) workflow.

    2.5k GitHub stars~1.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • React Sync

    vercel/next.js

    Official

    Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.

    143k GitHub stars~486 tokensUpdated today
    Auto-check passed

  • Spec Driven Workflow

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first…

    28k GitHub stars~3.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from LIDR-academy/AI4Devs-LTI-extended

All 9 skills in this repo

  • Owasp Security Audit

    LIDR-academy/AI4Devs-LTI-extended

    A skill your agent uses when performing a cybersecurity audit, security review, OWASP Top 10 compliance check, vulnerability assessment, or preparing for a penetration test on a…

    278 GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check: notes

  • Show Spec Working

    LIDR-academy/AI4Devs-LTI-extended

    A skill your agent uses when the user asks "show me X", "demo X", "walk me through X", "how X works" or requests a live feature demonstration from a spec, feature or ticket.

    278 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Run Parallel Tasks

    LIDR-academy/AI4Devs-LTI-extended

    Run N feature tasks in parallel, each in its own worktree, following the full specboot pipeline (enrich → new → ff → apply → verify).

    278 GitHub stars~1.5k tokensUpdated 4 mo ago
    Auto-check passed

  • Commit

    LIDR-academy/AI4Devs-LTI-extended

    Create focused commits and pull requests following repository standards.

    278 GitHub stars~1.5k tokensUpdated 4 mo ago
    Auto-check: notes

  • Explain

    LIDR-academy/AI4Devs-LTI-extended

    Teach underlying concepts with clear mental models to close skill gaps behind user questions.

    278 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Enrich Us

    LIDR-academy/AI4Devs-LTI-extended

    Analyze and enhance Jira user stories with complete, implementation-ready technical detail.

    278 GitHub stars~521 tokensUpdated 4 mo ago
    Auto-check passed

Questions about Sync Agent Symlinks

What does Sync Agent Symlinks do?

Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames). Sync Agent Symlinks is an agent skill from LIDR-academy/AI4Devs-LTI-extended. Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames).

When should I use Sync Agent Symlinks?

Sync Agent Symlinks fits situations like: skills are added/removed in ai-specs and .claude/skills and .cursor/skills must stay aligned through symlinks.

How do I install Sync Agent Symlinks in Claude Code?

Run `npx skills add LIDR-academy/AI4Devs-LTI-extended --skill sync-agent-symlinks -a claude-code`. Or copy the skill folder (ai-specs/skills/sync-agent-symlinks in LIDR-academy/AI4Devs-LTI-extended) into .claude/skills/sync-agent-symlinks in your project. Claude Code loads it when a task matches its description.

How do I install Sync Agent Symlinks in Codex?

Run `npx skills add LIDR-academy/AI4Devs-LTI-extended --skill sync-agent-symlinks -a codex`. Or copy the skill folder (ai-specs/skills/sync-agent-symlinks in LIDR-academy/AI4Devs-LTI-extended) into .agents/skills/sync-agent-symlinks in your project. Codex loads it when a task matches its description.

Can I use Sync Agent Symlinks 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 LIDR-academy/AI4Devs-LTI-extended --skill sync-agent-symlinks -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-agent-symlinks, .gemini/skills/sync-agent-symlinks, .github/skills/sync-agent-symlinks and .opencode/skills/sync-agent-symlinks in your project.

What does Sync Agent Symlinks need to run?

SKILL.md names no scripts, command-line tools or credentials: Sync Agent Symlinks is instructions for the agent only.

Does Sync Agent Symlinks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sync Agent Symlinks 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 Agent Symlinks use?

Sync Agent Symlinks 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 Agent Symlinks use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Agent Symlinks?

Skills that share tags, products or a category with Sync Agent Symlinks: Spec Writer (garrytan/gstack, 136k stars), Sync Specs (nexu-io/nexu, 3.3k stars), I18n Sync (affaan-m/ECC, 276k stars) and Spec (garden-co/classic-jazz, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sync Agent Symlinks?

LIDR-academy (a GitHub organization) maintains it in LIDR-academy/AI4Devs-LTI-extended, which has 278 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on June 9, 2026.

Source: LIDR-academy/AI4Devs-LTI-extended on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.