agentleFS
Sign inStart free
CipherNovaaCipherNovaa/agent-skills/skills/myos/migrate/SKILL.md

migrate

Skill0 starsChanged 12 days agoMITView on GitHub

Bring an old-format note (no frontmatter `type:`) onto the myOS properties standard without rewriting the body. Use to fix a pre-properties note, or the note the janitor routes here.

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident, sdd 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.
  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • liatrio-labsSkill

    sdd

    Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.

    Also in 4 projects that use this

  • BerryKuipersSkill

    scaffold

    Detect project stack, apply architecture patterns, wire quality gates, and scaffold features. Use when bootstrapping a project, adding a vertical slice, wiring CI/CD, adding Docker compose, or setting up quality gates.

    Also in 4 projects that use this

  • MicrosoftSkill

    init

    Also in 8 projects that use this

  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 3 projects that use this

  • genomewalkerSkill

    checkpoint

    Save a checkpoint of task status, decisions, active files, and next steps

    Also in 5 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 50 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:

    When unsure it should guess: add --strict — unmapped folders are then left + listed for escalation instead of floored to type: note.

    line 43
  2. Very specific:

    After --all --apply, $MYOS_ENGINES/myos_janitor_scan.py --brief no longer lists the "no frontmatter type:" line.

    line 58

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

migrate

The dual of the template engine: apply-template instantiates a new note; migrate brings an already-written note that predates the properties standard (no YAML type:) up to it. It only ever adds/splices a frontmatter block — the user's words are preserved byte-for-byte. Idempotent: a note that already has type: is left untouched. This is the fix path the janitor routes old-format notes to.

When to Use

  • The janitor flags "notes with no frontmatter type:" → run this to clear them.
  • file-note calls it to guarantee a filed note lands on the standard (see that skill's step 3).
  • Any single pre-properties note you want typed.

How type is decided (folder-first, conservative)

The note's home layer decides its type: — the layer is the most reliable signal:

Folder (spine key)type:
projectsproject
journal + YYYY-MM-DD filenamedaily
academics / systems / myosconcept
source_materialresource
inventoryinventory (+ category: from the subfolder)
anything unmappednote (floor) — or with --strict, skipped + flagged

Procedure

  1. One note: python $MYOS_ENGINES/myos_migrate_note.py "<path>" → previews the header it would add (dry-run). Confirm the inferred type: looks right, then re-run with --apply to write.
  2. The whole backlog: python $MYOS_ENGINES/myos_migrate_note.py --all → dry-run table over every old-format note (exactly the janitor's set). Then --all --apply to migrate them all.
  3. When unsure it should guess: add --strict — unmapped folders are then left + listed for escalation instead of floored to type: note.
  4. Report: migrated N, already-current M (+ any flagged/errors).

Pitfalls

  • Body is never rewritten — the tool prepends/splices frontmatter only. If you ever need to change wording, that's a different job (don't do it here).
  • Idempotent — safe to re-run; a note with type: is skipped. Don't hand-add a second block.
  • Existing inline #tags in the body keep working (body untouched); the block seeds tags: [].
  • Floored type: note on a note that clearly wants a real type → that's the escalation case.

Verification

  • myos_migrate_note.py "<note>" twice → 2nd run says already-current.
  • The migrated note opens with a --- block carrying a correct type:, and its body is unchanged (git diff shows only added frontmatter lines, zero deletions).
  • After --all --apply, $MYOS_ENGINES/myos_janitor_scan.py --brief no longer lists the "no frontmatter type:" line.

Cadence

On demand, or whenever the janitor surfaces old-format notes.

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