メニュー
Archived after consolidation into linux-system-debugging. Debug Linux login/password failures, PAM stacks, and account lockouts before changing auth config.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when building, backtesting, or deploying algorithmic trading systems with NautilusTrader (nautilus_trader) — writing Strategy/Actor classes and StrategyConfig, configuring BacktestNode/BacktestEngine, constructing instruments, order management, ParquetDataCatalog/wranglers, message bus and custom data streams, indicators, portfolio/analysis/report generation, or live TradingNode deployment. Curated for v1.230.0.
Inspect and extend Hermes Agent TUI capabilities, launch flags, hotkeys, composer input, and terminal behavior.
Use when modifying a multi-host Nix flake or dotfiles repo, especially host-specific inputs, overlays, lockfile scope, and evaluation checks.
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
Class-level Linux debugging workflow for authentication/PAM lockouts, desktop hardware/device stacks, and RAM/swap/CPU/process resource pressure.
Inspect installed Claude Code internals and official plugin recreations to locate prompts, output styles, built-in strings, and migration hooks.
| name | linux-authentication-debugging |
| description | Archived after consolidation into linux-system-debugging. Debug Linux login/password failures, PAM stacks, and account lockouts before changing auth config. |
| version | 1.0.0 |
| author | Hermes Agent |
| license | MIT |
| platforms | ["linux"] |
| metadata | {"hermes":{"archived_into":"linux-system-debugging","tags":["linux","pam","authentication","faillock","lockout","debugging"],"related_skills":["systematic-debugging","linux-system-debugging"]}} |
This skill package was consolidated into linux-system-debugging during the umbrella-building pass. The class-level instructions now live under the authentication/PAM/faillock section of that umbrella skill.
Preserved package references:
references/screen-locker-shared-faillock-case.mdreferences/i3-lockscreen-replacement-faillock.mdUse when a Linux user reports known-password rejection, lockout earlier than expected, or differing auth behavior across sudo, TTY login, SSH, display manager, or screen unlock. Gather non-sudo evidence (id, whoami, loginctl, account state, faillock --user) before changing PAM. Correlate journal lines for faillock, PAM services, i3lock, display managers, TTY logins, and SSH. Avoid blind sudo probes because failed sudo can consume another shared pam_faillock failure.
Core durable lesson: pam_faillock tracks failures by user across participating PAM services, so a later prompt can appear to lock early because another service already added failures.