Is Recall · MattsomStudio safe and trustworthy?

tashan scores Recall · MattsomStudio on public evidence — tashan score 42.0/100, it is currently active, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Recall · MattsomStudio?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Recall · MattsomStudio?

1 GitHub contributors, source: MattsomStudio/memsom.

‹ The Index

Recall · MattsomStudio

skill

Author’s activation text, quoted as published

Search the memsom memory store by meaning, not just by what's loaded in MEMORY.md. Trigger when the user asks things like "what did we figure out about X", "recall that conversation about Y", "search my memory for Z", "what do I have on W", "remember when we worked on…", or any request to find prior content that isn't in the always-loaded MEMORY.md index. Runs memsom's hybrid (BM25 + local vector) retrieval over the whole store and returns ranked hits with their provenance.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r recall ~/.claude/skills/

tashan score: 42.0
Adoption: 2 repos
Upkeep: 64.0
Freshness: 100.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 1
License: AGPL-3.0

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md does not say when to use it, show a worked example, cover setup, or state a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Recall · MattsomStudio scores 42 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/skill-mattsomstudio-recall.svg)](https://tashan.sh/capability/skill-mattsomstudio-recall.html)

source ↗ · skill:MattsomStudio/recall

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-22 · scorer s5 · how · something wrong here?