Is krimto-hierarchical-scope safe to install?

SaferSkills independently audited krimto-hierarchical-scope (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-hierarchical-scope/SKILL.md · 1 file

skills/krimto-hierarchical-scope/SKILL.md1.1 KB · Markdown

name: krimto-hierarchical-scope

description: Use when deciding what scope to store a fact at, or when reasoning about whether a fact

applies to the current user. Krimto uses a user -> team -> org hierarchy with precedence rules.

Triggers when scope selection is required.

Krimto's hierarchical scope model

Three scopes, most specific wins:

user/<identity> — personal preferences, individual decisions
team/<slug> — team conventions, project decisions
org/<slug> — company-wide policies, universal facts

Precedence (applied at recall time)

user-scope fact + team-scope fact on the same topic → user wins for that user
team-scope fact + org-scope fact → team wins for that team's members

Choosing a scope at write time

"I prefer X" → user/<identity>
"Our team agreed X" → team/<slug>
"All employees X" → org/<slug> (org admins only)

Common mistakes

Writing personal preferences at org scope (pollutes everyone)
Writing team decisions at user scope (no one else sees them)
Forgetting precedence when answering — always check user before team before org

krimto-hierarchical-scope— agent skill

Is krimto-hierarchical-scope safe to install?

Krimto's hierarchical scope model

Precedence (applied at recall time)

Choosing a scope at write time

Common mistakes

Audit the pieces. Scan the whole. Decide.