technicalpickles/connect
plugins/second-brain/skills/connect/SKILL.md
Find related notes via semantic search and weave links. Stage 4 of the processing pipeline.
$ install --global
skillsauthnpx skillsauth add technicalpickles/pickled-claude-plugins connectInstall 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.8s1 file scanned
SKILL.md
- name:
- connect
- description:
- Find related notes via semantic search and weave links. Stage 4 of the processing pipeline.
- - Bash(which:
- qmd)
- - Bash(qmd:
- status)
Connect Stage
Find related notes via semantic search (qmd) and weave forward/backward links.
See references/pipeline.md for stage definitions and status flow.
See references/connecting.md for the connection discovery algorithm.
Input
A routed note with status: routed.
Process
-
Check qmd availability:
which qmdIf not available, log "Skipped connections: qmd not available", set
status: connected, and return. -
Extract query terms from the note's title and body
-
Run semantic search:
qmd query "{terms}" -c {collection} -n 15 --json -
Filter and rank per
references/connecting.md:- Remove self
- Remove already-linked notes
- Remove daily notes
- Remove low-relevance results (below 30%)
-
If candidates found, present to human (when called by orchestrator):
- Show candidates with scores and snippets
- Let user multi-select which to connect
-
For selected connections:
- Add
## Relatedsection to the note with wiki-links - Offer backlink weaving for notes that have See Also/Related/TK sections
- Add
-
Update status to
connected
Output
- Note with
## Relatedsection added (if connections found) status: connected
Constraints
- Graceful skip if qmd unavailable (always log that it was skipped)
- The note being processed won't be in qmd's index yet. Search FROM its content, not for it.
- Don't add connections the user didn't approve
- Backlink weaving is optional (offer, don't force)
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