agentleFS
Sign inStart free
fotis89fotis89/ctx-launcher/.github/skills/sync-skills/SKILL.md

sync-skills

Skill4 starsChanged 34 days agoMITView on GitHub

Check that the bundled wl-workspace skill, its installed copy, and docs/reference.md match the code. Use after editing src/wl/Resources/wl-workspace.md, docs/reference.md, or anything that changes commands, files, or workspace.json.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use explain, create-skill and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • ElasticSkill

    create-skill

    Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Only real commands are mentioned: wl launch, wl which, wl create, wl clone.

    line 22
  2. Very specific:

    Read both files and the relevant code (Workspace.cs, Program.cs) and README sections.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compare the bundled skill with its installed copy and flag drift.

Files to compare

  1. Resource file (source of truth): src/wl/Resources/wl-workspace.md
  2. Installed copy (written automatically on the first wl launch/create/clone after a version change): ~/.wl-workspaces/.shared/.copilot/skills/wl-workspace/SKILL.md

The installed copy comes from the installed wl binary, so it only matches the working tree after installing a new build (/publish) and launching once. Report a difference as "installed wl is older" when the resource changed after the installed version's commit (wl --version shows the commit).

What to check

  • Resource vs installed copy — identical after installing a build of the current commit.
  • Consistency with wl itself — the skill must match the current code and README:
    • workspace.json fields: schemaVersion: 2, name, primaryRepo, additionalDirs, optional copilotArgs. No yolo, resume, or tool.
    • Workspace instructions live in the workspace AGENTS.md; skills in .copilot/skills/ with the wl- prefix.
    • Only real commands are mentioned: wl launch, wl which, wl create, wl clone. Path variables are read/edited in ~/.wl-workspaces/.paths.json.
  • docs/reference.md — the commands table, file tree, workspace.json fields, session table, launch steps and argument order, and .gitignore patterns match the code (Program.cs, WlPaths.cs, Workspace.cs, CopilotService.BuildArgs, LaunchCommand, SetupService.DefaultGitignore).

Steps

  1. Read both files and the relevant code (Workspace.cs, Program.cs) and README sections.
  2. Report:
    ## Skill sync report
- Resource vs installed: <in sync / N differences / installed wl is older>
- Consistency: <ok / list of mismatches>
### Suggested fixes
- <file>: <change>
  3. Apply fixes only after confirmation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free