agentleFS
Sign inStart free
namedtoasternamedtoaster/The-Last-Mile/skills/sync/SKILL.md

sync

Skill39 starsChanged 22 days agoMITView on GitHub

Bring this project's copy of The Last Mile skills up to date, then commit and push it, so the next session on any device has the latest skills. Works from the phone, nothing to run by hand. Use when the user says "sync", "update the skills", "get the latest Last Mile", or a Last Mile change they just made is missing here.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use develop, scope and 10 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.
  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If the session will not run a script it just downloaded, use a local clone of the source, the way the README's "By hand" step 3 says.

    line 16
  2. Very specific:

    If claude plugin list shows The Last Mile plugin enabled too, every skill loads twice.

    line 18
  3. Very specific:

    Sync: Run node .claude/last-mile/sync.mjs.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 47 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

Sync

Copy the latest Last Mile skills into this project, commit and push. Do every step yourself; the user is often on a phone and runs nothing by hand.

  1. Check it is set up. The project needs .claude/last-mile/sync.mjs and .claude/last-mile/config.json. If either is missing, set them up the way sync/README.md in The Last Mile (namedtoaster/the-last-mile) says: fetch sync/sync.mjs from it and write the config with "source": "namedtoaster/the-last-mile", "ref": "main", "keepLocal": []. If the session will not run a script it just downloaded, use a local clone of the source, the way the README's "By hand" step 3 says. If claude plugin list shows The Last Mile plugin enabled too, every skill loads twice. Say so and offer to turn it off for this project: claude plugin disable the-last-mile@the-last-mile -s local.
  2. Sync. Run node .claude/last-mile/sync.mjs. It clones the source from GitHub, which cloud sessions can always reach.
  3. Commit only what the sync changed: .claude/skills and .claude/last-mile/synced.json. Never sweep in other work in progress. If nothing changed, say it is already current and stop.
  4. Push the way the project's rules file says (its Push to setting). With no setting, push to the branch the session works on.
  5. Report in two or three lines: which skills changed, the source commit, and that new or changed skills load in the next session (start a new one to use them now).

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