agentsclimarketplace
Sign in

Atuin memory

Skill cosgroveb/claude-atuin-memory-skill/skills/atuin-memory

Check, store, and retrieve atuin memory for project roadmap, feature work, and optional cross-project priming context.From its SKILL.md

Install
npx -y skills add cosgroveb/claude-atuin-memory-skill --skill atuin-memory

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, as published. Nobody here has run it

Use this skill for atuin-backed project memory. Keep task state in project-metadata. Use technical-knowledge as read-mostly cross-project priming memory when reusable technical context would help.

  • Start with project-detection.md.

  • Use project-metadata.md for roadmap, feature plans, specs, todos, and session notes.

  • Use technical-knowledge.md for cross-project priming memory and retrieval cues.

  • Use operations.md for get/set/delete syntax and multiline storage.

  • Prefer a user-named feature slug.

  • Otherwise use the active roadmap item when it is clear.

  • Do not infer the feature slug from git branch by default.

  • If the feature is unclear, ask the user.

  • main and master are never valid feature slugs.

  • A named branch alone is not enough. If the branch name is the only candidate, ask whether it maps to the memory name.

  • If the derived project or feature slug looks like a temp dir, hidden scratch dir, or placeholder such as tmp.*, random dot-dir names, or no-branch, ask the user how the memory should be remembered before storing it.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.