using-knowledge-patch
SKILL.md
Rule
Even a 1% chance your task touches a patched technology → invoke that patch skill BEFORE writing code. Not optional.
Access via Skill tool: Skill: rust-knowledge-patch, Skill: bun-knowledge-patch, etc.
Red Flags — STOP if you think:
| Thought | Reality |
|---|---|
| "I know this API" | Training may be months behind |
| "Too simple to check" | Simple APIs get breaking changes |
| "I'm confident" | Confidence from training ≠ current accuracy |
| "Let me code first" | Wrong code = wasted time |
Priority
- Knowledge patch (most current) > 2. CLAUDE.md / AGENTS.md > 3. Training data (may be outdated)
Weekly Installs
1
Repository
nevaberry/nevab…-pluginsGitHub Stars
7
First Seen
8 days ago
Security Audits
Installed on
amp1
cline1
opencode1
cursor1
kimi-cli1
codex1