setup-memory SKILL.md skillA

setup-memory from antostr/team-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add antostr/team-workflow/setup-memory@git:20261108.f56f165

Pins git:20261108.f56f165 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
antostr/team-workflow
Path
skills/setup-memory/SKILL.md
Versions recorded
2
Latest version
git:20261108.f56f165, committed Nov 8, 2026
First version recorded
Nov 8, 2026
Size
1,177 bytes
Repository stars
3
License
MIT

Set up the shared project memory (docs/memory) in this repository and fill it from the code.

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

Use the team skill to set up the project memory of this repository.

1. If `docs/memory/INDEX.md` already exists, say so, run memcheck and stop.
2. Run `python3 <team skill folder>/scripts/init_memory.py --root <repository root>`.
3. Fill the memory from the real code, facts only:
   - `STATE.md`: version and the file that holds it, CI, known limits.
   - `PLAYBOOKS.md`: run the detected commands to confirm them; add the release steps.
   - `MAP.md`: every module or package in one line, grouped by area.
   - One card per area in `areas/`, from `areas/_TEMPLATE.md`: key files, contracts, tests,
     known traps.
   - `ACCESS.md`: what each folder holds and what must never be touched.
   In a large repository, split the reading of the areas between `doc-keeper` agents and
   check what they write.
4. Run memcheck and fix what it reports.
5. Report what was created, which commands you confirmed and what the user should check.

Notes from the user: $ARGUMENTS

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_2d73bxoeyqxg4qno/6e1dd6b2d9a35b0b87a9f7258a5960405afd5d580147ad9f8df1942f791a30b0.json

Then /plugin install setup-memory@markdownregistry-2d73bxoeyqxg4qno in Claude Code. It installs git:20261108.f56f165, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add antostr/team-workflow/setup-memory@sha256:6e1dd6b2d9a35b0b

The line at the top of this page pins the label git:20261108.f56f165, 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_2d73bxoeyqxg4qno.svg)](https://markdownregistry.com/a/art_2d73bxoeyqxg4qno)

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 antostr/team-workflow/setup-memory 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 setup-memory from somewhere else? Ask it: where did my setup-memory 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 2 versions of this file, all committed on Nov 8, 2026.

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

versioncommittedcommitsizeaudit
git:20261108.f56f165 latest2026-11-08 f56f165 1,177 BA view · diff
git:20261108.36c5a0f2026-11-08 36c5a0f 1,195 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 (1177 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

antostr/team-workflow · 3 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_2d73bxoeyqxg4qno
GET https://markdownregistry.com/api/v1/resolve?ref=antostr/team-workflow/setup-memory
GET https://markdownregistry.com/api/v1/blob/6e1dd6b2d9a35b0b87a9f7258a5960405afd5d580147ad9f8df1942f791a30b0

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 antostr/team-workflow

AGENTS.md@docs AGENTS.md file
antostr/team-workflow · docs/AGENTS.md
git:20261115.eee52df · audit A · 3 stars
AGENTS.md@rules AGENTS.md file
antostr/team-workflow · rules/AGENTS.md
git:20261111.42d0bf5 · audit A · 3 stars
addons SKILL.md skill
antostr/team-workflow · skills/addons/SKILL.md · Add, remove, update or list add-on plugins (skills, plugins and MCP servers - caveman, ponytail, the frontend…
git:20261108.f56f165 · audit A · 3 stars
agents SKILL.md skill
antostr/team-workflow · skills/agents/SKILL.md · List and customize the team roles - type, model and effort per role and per app, packs (languages, quality, planning…
git:20261108.f56f165 · audit A · 3 stars
audit SKILL.md skill
antostr/team-workflow · skills/audit/SKILL.md · Security audit of the AI agent setup - Claude Code and agy settings, permissions, hooks, MCP servers, agents, skills…
git:20261108.f56f165 · audit A · 3 stars
call-team SKILL.md skill
antostr/team-workflow · skills/call-team/SKILL.md · Call a team of agents for a task you describe - pick several roles (product, frontend, backend, fullstack, data…
git:20261108.f56f165 · audit A · 3 stars
ci-init SKILL.md skill
antostr/team-workflow · skills/ci-init/SKILL.md · Add a GitHub Actions workflow that checks the project memory and audits the agent configuration on every pull request…
git:20261108.f56f165 · audit A · 3 stars
doctor SKILL.md skill
antostr/team-workflow · skills/doctor/SKILL.md · Health check of team in Claude Code and agy - versions, settings, native agents, add-ons, launcher, memory and audit -…
git:20261108.f56f165 · audit A · 3 stars
end-session SKILL.md skill
antostr/team-workflow · skills/end-session/SKILL.md · Close the session - update the project memory, record lessons and decisions, report what is left
git:20261108.f56f165 · audit A · 3 stars
fix-bug SKILL.md skill
antostr/team-workflow · skills/fix-bug/SKILL.md · Fix a bug the safe way - reproduce it as a failing test first, then fix, verify and report
git:20261108.f56f165 · audit A · 3 stars
learn-history SKILL.md skill
antostr/team-workflow · skills/learn-history/SKILL.md · Learn this repository's habits from its git history - hotspots, bug-prone files, files that change together, commit…
git:20261108.f56f165 · audit A · 3 stars
library SKILL.md skill
antostr/team-workflow · skills/library/SKILL.md · The library inside team - 296 skills, 94 commands and 22 coding rule sets - list packs, search entries for a task, show…
git:20261108.f56f165 · audit A · 3 stars

Every file in antostr/team-workflow

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