technicalpickles/distill-rules
plugins/second-brain/skills/distill-rules/SKILL.md
Review routing corrections and propose updates to vault CLAUDE.md routing rules.
$ install --global
skillsauthnpx skillsauth add technicalpickles/pickled-claude-plugins distill-rulesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:03 AM7.5s1 file scanned
SKILL.md
- name:
- distill-rules
- description:
- Review routing corrections and propose updates to vault CLAUDE.md routing rules.
- - Bash(npx @techpickles/sb:
- *)
Distill Rules
Review accumulated routing corrections in .routing-memory.md and propose updates to the vault's CLAUDE.md routing rules.
See references/routing-memory.md for correction format and learning loop.
Process
-
Read
.routing-memory.mdfrom vault root -
Read vault CLAUDE.md
-
Analyze corrections for patterns:
- Group corrections by destination
- Identify repeated corrections (same type of note going to same destination)
- Look for corrections that contradict existing CLAUDE.md rules
-
Propose updates:
- New edge case mappings for disambiguation sections
- New category table entries
- New learned patterns for
.routing-memory.md - Corrections to existing rules that have been consistently overridden
-
Present proposals to user:
Found {n} patterns in {m} corrections: 1. Add edge case: "{scenario}" -> {destination} Based on: {n} corrections over {date range} 2. Add to category table: "{tool}" under {area} Based on: {n} corrections 3. Update rule: "{old rule}" -> "{new rule}" Based on: consistently overridden {n} times Apply these updates? (A) Apply all (B) Review individually (C) Skip for now -
Apply selected updates:
- Edit vault CLAUDE.md with new rules
- Move applied corrections to an
## Archivedsection in.routing-memory.md - Promote stable patterns to
## Patterns Learned
Constraints
- Never auto-apply. Always present proposals for approval.
- Preserve existing CLAUDE.md structure and formatting
- Archive corrections, don't delete them (audit trail)
- Only propose rules backed by multiple corrections (minimum 2)
Related Skills
technicalpickles/plugins/writing-tools/skills/writing-for-scannability
tools
VerifiedTrustedCommunity
--- name: writing-for-scannability description: Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that
10SKILL.mdUpdated Jun 2, 2026
technicalpickles/actually-lsp-ignore
development
VerifiedTrustedCommunity
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp.json`. Persistent across sessions for this project only.
10SKILL.mdUpdated May 28, 2026
technicalpickles/actually-lsp-doctor
tools
VerifiedTrustedCommunity
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
10SKILL.mdUpdated May 28, 2026
technicalpickles/plugins/github-actions/skills/investigating-runs
tools
VerifiedTrustedCommunity
--- name: investigating-runs description: Use whenever the user mentions a GitHub Actions / GHA run, even casually — invoke this skill before reaching for raw `gh` commands, because the bundled `gha-snapshot` helper distills `gh run view --log-failed` (a firehose) into a readable block with per-job status, failed-step log tails, and annotations. Specific triggers (any one is enough): a `github.com/.../actions/runs/...` URL; the phrase "GitHub Actions" or "GHA"; the `gh run` CLI; a failing workfl
10SKILL.mdUpdated May 21, 2026