technicalpickles/actually-lsp-ignore
plugins/actually-lsp/skills/actually-lsp-ignore/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add technicalpickles/pickled-claude-plugins actually-lsp-ignoreInstall 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: May 28, 2026, 4:28 AM35.6s1 file scanned
SKILL.md
- name:
- actually-lsp-ignore
- description:
- 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.
/actually-lsp-ignore
Parse args:
rust|typescript|rubyas an arg ignores that ecosystem directly.- No args: read
.claude/actually-lsp.jsonin the current project root, present the detected ecosystems, and ask the user which to ignore.
Action
Update the project state file at .claude/actually-lsp.json: set .ecosystems.<ecosystem>.dismissed to true. If the file doesn't exist, create it with version 1 schema:
{
"version": 1,
"ecosystems": {
"<ecosystem>": {
"state": "dismissed",
"dismissed": true,
"last_check_at": null,
"last_marker_mtime": null,
"last_plugin_list_hash": null,
"last_error": null
}
}
}
If the file exists, preserve all other fields and only flip dismissed.
The internal state value stays dismissed (that's the state-machine name from CONTEXT.md); only the user-facing skill name is ignore.
Confirmation output
Output a one-line confirmation per ignored ecosystem:
Ignoring <ecosystem> for this project. To re-enable, manually edit .claude/actually-lsp.json and set dismissed back to false. (A re-enable command is a future extension.)
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-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
technicalpickles/taskwarrior
tools
VerifiedTrustedCommunity
Use when querying or modifying tasks via the taskwarrior CLI - dense recipes for listing, single-field lookups, multi-task batched lookups, full-text search, and the soft description-length convention. Activates on `task list`, `task add`, `task info`, `task done`, "what's on the backlog", "find a task", or any taskwarrior interaction.
10SKILL.mdUpdated May 9, 2026