sync-agent-layers SKILL.md skillA

sync-agent-layers from igniteui/ai-repo-structure is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add igniteui/ai-repo-structure/sync-agent-layers@git:20261117.4024d82

Pins git:20261117.4024d82 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
igniteui/ai-repo-structure
Path
.agents/skills/sync-agent-layers/SKILL.md
Versions recorded
1
Latest version
git:20261117.4024d82, committed Nov 17, 2026
Size
1,296 bytes
Repository stars
12
License
MIT

Carries a relevant change across the Claude Code, GitHub Copilot, and Codex layers of this repository without making them identical. Use when an agent, skill, rule, instruction, or hook changes in .claude/, .github/, .codex/, or .agents/.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Sync agent layers

This repo shows one maintainer setup in three tools. When one layer changes, decide which counterparts need the same change, and apply it in each tool's own format.

## Workflow

1. Read `references/counterparts.md` and find the counterparts of the changed file.
2. For each counterpart, decide whether the change is relevant:
   - shared intent, such as the role, focus areas, covered paths, or validation steps: sync it
   - tool-specific behavior, such as frontmatter fields, tool lists, hook output format, or trust rules: leave it, or adapt it only if that tool supports it
3. Apply relevant changes in each tool's own format. Never copy one tool's syntax into another.
4. If a file was added, renamed, or removed, update `references/counterparts.md` and the README tree.
5. Run `bash .claude/skills/validate-learning-repo/scripts/check-required-files.sh`.

## Output

- counterparts updated, with one line per file on what changed
- counterparts intentionally left different, and why

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kuo4ld4qgi4srk2q/72e7037041c0fb238cb0e8dc2f464b7b244234b9459eb2cf6287d5e9cfcbba1d.json

Then /plugin install sync-agent-layers@markdownregistry-kuo4ld4qgi4srk2q in Claude Code. It installs git:20261117.4024d82, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add igniteui/ai-repo-structure/sync-agent-layers@sha256:72e7037041c0fb23

The line at the top of this page pins the label git:20261117.4024d82, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_kuo4ld4qgi4srk2q.svg)](https://markdownregistry.com/a/art_kuo4ld4qgi4srk2q)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in igniteui/ai-repo-structure/sync-agent-layers since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of sync-agent-layers from somewhere else? Ask it: where did my sync-agent-layers come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 17, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261117.4024d82 latest2026-11-17 4024d82 1,296 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (1296 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

igniteui/ai-repo-structure · 12 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_kuo4ld4qgi4srk2q
GET https://markdownregistry.com/api/v1/resolve?ref=igniteui/ai-repo-structure/sync-agent-layers
GET https://markdownregistry.com/api/v1/blob/72e7037041c0fb238cb0e8dc2f464b7b244234b9459eb2cf6287d5e9cfcbba1d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from igniteui/ai-repo-structure

learning-repo-maintainer Claude Code subagent
igniteui/ai-repo-structure · .claude/agents/learning-repo-maintainer.md · Maintains this repository as a real teaching repo for AI-enabled project structure. Use proactively when changes affect…
git:20261117.4024d82 · audit A · 12 stars
validate-learning-repo SKILL.md skill
igniteui/ai-repo-structure · .claude/skills/validate-learning-repo/SKILL.md · Audits this repository's teaching content against the real file structure. Use when checking README examples…
git:20261117.4024d82 · audit A · 12 stars
copilot-instructions.md
igniteui/ai-repo-structure · .github/copilot-instructions.md
git:20261117.4024d82 · audit A · 12 stars
learning-content Copilot instructions
igniteui/ai-repo-structure · .github/instructions/learning-content.instructions.md
git:20261117.4024d82 · audit A · 12 stars
review-learning-repo-pr SKILL.md skill
igniteui/ai-repo-structure · .github/skills/review-learning-repo-pr/SKILL.md · Reviews pull requests that change the teaching structure of this repository. Use when PRs affect README.md, AGENTS.md…
git:20261117.4024d82 · audit A · 12 stars
AGENTS.md AGENTS.md file
igniteui/ai-repo-structure · AGENTS.md
git:20261117.9356497 · audit A · 12 stars
CLAUDE.md CLAUDE.md file
igniteui/ai-repo-structure · CLAUDE.md
git:20261117.4024d82 · audit A · 12 stars
adopt-this-repo SKILL.md skill
igniteui/ai-repo-structure · skills/adopt-this-repo/SKILL.md · Help a user or agent adopt this repository structure into another project by deciding what to copy, what to adapt, what…
git:20261117.4024d82 · audit A · 12 stars
use-this-repo SKILL.md skill
igniteui/ai-repo-structure · skills/use-this-repo/SKILL.md · Explain this repository's AI structure, what each layer and file is for, and how the Claude, GitHub/Copilot, and shared…
git:20261117.4024d82 · audit A · 12 stars

Every file in igniteui/ai-repo-structure

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.