memory-team SKILL.md skillA
memory-team from eric-cielo/moflo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eric-cielo/moflo/memory-team@git:20261017.b8b790aPins git:20261017.b8b790a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eric-cielo/moflo
- Path
.claude/skills/memory-team/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.b8b790a, committed Oct 17, 2026
- First version recorded
- Jul 1, 2026
- Size
- 8,674 bytes
- Repository stars
- 19
- License
- MIT
Guided setup for sharing moflo's durable learnings through a git-tracked artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", "auto-export learnings on every PR", or "learnings.jsonl keeps conflicting". Installs a pre-commit hook so the artifact rides along in every commit. An existing…
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
# /memory-team — Share Learnings via a Git-Tracked Artifact Wires up **`memory.team_artifact`**: a diffable directory (`.moflo/shared/learnings/`, one JSON file per entry) that lives **in the repo**, reviewed like any other change. One file per entry means two PRs that each add a learning never conflict — on GitHub or locally. Teammates `git pull` it and their next session auto-imports the merged learnings; each entry is stamped with its git author. This skill also installs a **pre-commit hook** so the artifact is re-exported and staged on every commit — the learnings ride along in each PR with zero effort. > **One mechanism, two audiences.** A *team* and *one person across machines* are the same problem — push > the durable slice through git. This skill covers both; the only difference is whether anyone else is on > the other end. (Prefer a private, non-git file for your own machines? See "Advanced" at the bottom — > `flo memory sync` moves a binary artifact that keeps embeddings verbatim.) **Arguments:** `$ARGUMENTS` — pass `--solo` to skip team-oriented wording (still identical setup). ## When to use - "share learnings / memory with my team" …
Read the whole file at its exact version.
How to install
mdr add eric-cielo/moflo/memory-team@sha256:8d2c7b4c9b105c1fThe line at the top of this page pins the label git:20261017.b8b790a, 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.
[](https://markdownregistry.com/a/art_flrwfc4qepo7pkxt)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 1, 2026 and Oct 17, 2026, about one every 109 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.b8b790a latest | 2026-10-17 | b8b790a | 8,674 B | A | view · diff |
| git:20260701.0d15602 | 2026-07-01 | 0d15602 | 7,035 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8674 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
eric-cielo/moflo · 19 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_flrwfc4qepo7pkxt GET https://markdownregistry.com/api/v1/resolve?ref=eric-cielo/moflo/memory-team GET https://markdownregistry.com/api/v1/blob/8d2c7b4c9b105c1f990b84d83ae6e49419fa35073ed29f124a3d80711e988e5f
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.