菜单
Look up secrets from KeePassXC via FDO Secret Service. USE WHEN the agent needs credentials, API keys, tokens, or passwords stored in KeePassXC.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | keepassxc |
| description | Look up secrets from KeePassXC via FDO Secret Service. USE WHEN the agent needs credentials, API keys, tokens, or passwords stored in KeePassXC. |
| allowed-tools | ["Bash"] |
| user-invocable | true |
| argument-hint | <search-term> |
| model | sonnet |
| context | fork |
| agent | general-purpose |
You retrieve secrets from an unlocked KeePassXC database via the FDO Secret Service API using secret-tool. Only entries in KeePassXC groups explicitly exposed for Secret Service access are available.
Gather Context: Run claude-KeePassXC-search with no arguments to verify KeePassXC is running and unlocked. If it returns an error, inform the user that KeePassXC must be running and unlocked with FDO Secrets enabled.
Determine Intent: Analyze the user's request or the agent's need:
$ARGUMENTS?Select Workflow:
Execute Workflow: Read the workflow document completely before proceeding, then follow the workflow's process completely.
Report Results: Confirm the credential was retrieved by name (never by value).
| Workflow | Trigger Words | When to Use |
|---|---|---|
| LookupSecret | "lookup", "get", "fetch", "password", "secret", "credential", "token", "key" | Agent needs to retrieve a specific secret or browse available entries |
Test NixOS configuration changes using the feedback ladder — from instant syntax checks to full system builds. USE WHEN the user wants to verify, test, or check NixOS changes before deploying.
Review and fix documentation surprises discovered by the surprise hook. USE WHEN the user wants to fix documentation issues, review surprises, or address items in .claude/surprises/.
Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries.
Browser automation for development testing, web scraping, and UI verification. USE WHEN you need to interact with web pages, verify UI changes, take screenshots, or extract data from websites.
Systematically explore and test a web application to find bugs, UX issues, and other problems. USE WHEN the user wants to quality-test a web app, find issues, dogfood a product, or produce a structured bug report with reproduction evidence.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) via Chrome DevTools Protocol. USE WHEN the user needs to interact with an Electron desktop app, automate a native app, connect to a running Electron app, or test an Electron application.