🔌
Plugins
Loading...
Showing 30 of 14295 results
Credibility and consistency tracker -- ingest YouTube transcripts and news, detect contradictions
Capture tasks into Things 3 on macOS via the things:/// URL scheme. ALWAYS use this skill when the user mentions Things (the Cultured Code app), Things 3, Things Inbox, or asks to add/create/capture to-dos, tasks, reminders, or todos in Things. Also use when the user invokes the /mytodo slash command, dictates a stream-of-consciousness list they want turned into tasks, or asks to push items to Things by project or area. Covers: generalizing free text into atomic to-dos, batch-adding via things:///json, scheduling (today, anytime, someday, specific date), targeting projects or areas, tags, and checklist items. Not for other to-do apps — if the user mentions Reminders, Todoist, OmniFocus, or anything non-Things, do not use this skill.
Apply expert thinking profiles to code reviews, architecture evaluation, and security audits - think like DHH, Sandi Metz, or build your own expert profiles
Third-party risk and operational resilience skills for vendor diligence, criticality assessment, DORA registers, contract gaps, exit plans, resilience testing, and concentration risk.
VeChainThor node internals — architecture, consensus (PoA/PoS/BFT), built-in contracts, REST API, storage, P2P, block production, transaction lifecycle, rewards, staking, and contributing to the Go codebase
from johnlindquist/thoroughness-enforcer
Conduct systematic security threat model assessments by analyzing code against countermeasurement requirements and generating compliance documentation with optional JIRA integration
from rhuss/rhuss-claude-marketplace
from josemlopez/threat-modeling-toolkit
ThreatLocker - zero-trust application allowlisting, approval triage, audit log investigation, computer inventory
Full three-pillars framework: TDD pipeline, spike pipeline, council, session management, and docs skills
Git-backed messaging for AI agent coordination across sessions, worktrees, and machines.
Tidy-as-you-touch: when you edit a file, format it and surface linter findings — fixing what's safe — flag it for decomposition when it grows past a size budget, and hold a subtractive posture (reuse before create, delete what a change makes redundant) so an actively-worked project trends down in complexity over time, scoped to the file you touched. The standard goes quiet (one-line re-anchor) once it's recorded in the project's CLAUDE.md. Edit-time linting targets Go (goimports/gofumpt + golangci-lint), web (eslint incl. jsx-a11y, stylelint), Python (ruff) and shell (shellcheck) — findings-only, the project's own tool, fast file-scoped tools only (slow whole-project linters stay with the verification floor). It surfaces an approximate blast-radius of the touched file (Go via the toolchain's exact go list importer graph, cached per session, falling back to git grep; else git grep) so a change's affected surface gets test coverage. A Stop hook is the verification floor: after Claude finishes, if the working tree changed and the project has a discoverable test command, it runs the tests and blocks until they pass (bounded) — the safety net a non-technical owner can't produce. After a change verifies clean, the same Stop hook surfaces the deliberate whole-project prune when debt crosses a threshold (over-budget files past CLAUDE_TIDY_PRUNE_THRESHOLD, default 3) — a weight report recommending a subtractive pass (dead code, duplication, doc gaps), throttled to once per debt episode, with any cuts routed through the task-queue review loop; no manual command. Coverage ratchet: when a touched source file has no test, nudge to characterize it before changing; opt-in strict mode (CLAUDE_TIDY_COVERAGE_RATCHET=1) blocks the stop until changed source is characterized. Regression gate (always-on, narrow): the same Stop hook blocks when a changed file is BOTH a scar-tissue hotspot (one git history shows has been repeatedly FIXED — mirrors charter's outcome-memory detector, drift-guarded) AND still has no test — a fix to a proven debt-magnet can silently regress, so it must be pinned by a regression test before finishing. Safe to keep on by default because it only fires on files that have earned it and goes quiet the moment a test lands (closing the loop charter's scar-tissue detection opens); bounded like the test floor (can't loop), disable with CLAUDE_TIDY_REGRESSION_GATE=0, and stands down when the broad coverage ratchet is already forcing. Quality floor: before the tests, the same Stop hook enforces the project's OWN declared quality gates beyond its test command — typecheck, a11y/perf, and architecture/dependency rules, discovered as package.json scripts (npm/pnpm/yarn) — running detect-and-run (installs/invents nothing; heavy Lighthouse/CWV audits stay in CI) and blocking until they pass, bounded like the test floor; disable with CLAUDE_TIDY_QUALITY_FLOOR=0. Clean-architecture check (zero owner config): after a clean verify it also surfaces any import CYCLE that involves a file changed this turn — detect-and-run the project's own madge (no bespoke resolver; silent without it; Go/Rust cycles are compiler errors the floor already catches), non-blocking and content-deduped per session, disable with CLAUDE_TIDY_CYCLE_CHECK=0. Coupling-density trend: the same post-green surface nudges when import-edges-per-file (a size-normalized coupling proxy, so healthy growth doesn't false-alarm) climbs past a threshold vs the last check — turning 'watch total coupling' into a measured signal; per-repo baseline, non-blocking, disable with CLAUDE_TIDY_COUPLING_TREND=0.
Development tools and guides for tidymodels ecosystem packages including yardstick metrics, recipes steps, dials parameters, and parsnip models
Claude Code skills for using tidymodels packages in data analysis and modeling
from TierZeroAI/tierzero-claude-code
Shared data integrations for Tiger Intelligence - connects to GitHub, Slack, Jira, Linear, Notion, PagerDuty, Google Docs, and Calendar
For ICs: Discover if you're a tiger team member and make invisible work visible
For leaders: Identify tiger teams in your organization and audit your metrics for reality vs noise
For PMs and team leads: Map dependencies on key people and monitor tiger team health