Is krimto-write-fact safe to install?

SaferSkills independently audited krimto-write-fact (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/krimto-write-fact/SKILL.md · 1 file

skills/krimto-write-fact/SKILL.md1.6 KB · Markdown

name: krimto-write-fact

description: Use when the user asks you to remember something for later, save team knowledge, record

a decision, or note a durable fact about the project, person, or team. Triggers on "remember that",

"save this", "add to memory", "note for the team". Do not use for conversational context.

Writing facts to Krimto memory

When the user wants to save a durable fact:

Choose the scope (default to the user's personal scope unless the fact is clearly shared):

user/<identity> — personal preferences, individual decisions (e.g. user/[email protected])
team/<slug> — team conventions, shared system rules (e.g. team/payments)
org/<slug> — company-wide standards (e.g. org/acme); org admins only

Call krimto_recall first to avoid writing a duplicate.
Call the MCP tool krimto_write with:

scope: one of the forms above
title: a descriptive title, ≤ 80 characters
body: markdown content
tags (optional): lowercase kebab-case array
source (optional): URL or stable identifier
supersedes (optional): array of fact ids this replaces

The server assigns the author, timestamps, and fact id, writes the markdown file, and commits to git. Return the resulting path so the user can find it.

Common mistakes

Don't write the same fact at multiple scopes. Pick the broadest scope where it is true.
Don't write to org/ without confirming the user is an org admin.
Don't invent the scope. If unclear, ask, or default to the user's personal scope.
Don't extract facts silently — only write when the user asks or you learn a durable, non-obvious fact.

krimto-write-fact— agent skill

Is krimto-write-fact safe to install?

Writing facts to Krimto memory

Common mistakes

Audit the pieces. Scan the whole. Decide.