learn-rule — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited learn-rule (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Capture a lesson from the current session into permanent memory.
Use when the user says "remember this", "add to rules", "don't do that again", or after a mistake is identified.
[LEARN] Category: One-line rule
Mistake: What went wrong
Correction: How it was fixedAppend Wiki: <slug> to bind the rule to a single pro-workflow wiki. The rule loads only when that wiki is in scope, avoiding cross-project pollution:
[LEARN] Editing: Cite a sources.md row before adding any wiki claim.
Wiki: agent-memoryThe capture hook auto-detects Wiki: <slug> and links the learning to that wiki via learnings_wiki.
| Category | Examples |
|---|---|
| Navigation | File paths, finding code, wrong file edited |
| Editing | Code changes, patterns, wrong approach |
| Testing | Test approaches, coverage gaps, flaky tests |
| Git | Commits, branches, merge issues |
| Quality | Lint, types, style violations |
| Context | When to clarify, missing requirements |
| Architecture | Design decisions, wrong abstractions |
| Performance | Optimization, O(n^2) loops, memory |
Recent mistake: Edited wrong utils.ts file
[LEARN] Navigation: Confirm full path when multiple files share a name.
Add to LEARNED section? (y/n)[LEARN] rule with category~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.