Guide accessibility reviews for UI, documents, and workflows. Use for WCAG-oriented audits, keyboard review, semantics, contrast, and remediation planning.
The English summary is being prepared. Showing the original description.
Use when validating logical secret-ID maps, config, and reference syntax for a KeePassXC integration; output is redacted and the fake backend is test-only.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill to validate non-secret logical-ID metadata and reference syntax. It does not resolve, display, create, rotate, update, delete, or otherwise access real KeePassXC entries.
Primary validation commands:
python3 scripts/localsetup_secrets.py map-validate --map examples/map.yaml
python3 scripts/localsetup_secrets.py reference '{{secret:mail.box03.example.admin:password}}'
Capability check:
python3 scripts/verify_keepassxc.py --format json
The CLI emits JSON envelopes by default:
{
"ok": true,
"command": "map-validate",
"data": {},
"warnings": [],
"errors": [],
"sources": [],
"sensitive": false,
"redactions": []
}
Use --format human only for interactive display. Diagnostics are redacted. Protected values require --show-sensitive.
The default keepassxc backend preserves existing configuration and may check the CLI version. When keepassxc-cli is unavailable it reports missing_backend; otherwise it refuses every vault operation with interactive_backend_required. fake exists only for deterministic tests and examples; it is not a secret store.
Canonical IDs are lowercase and may contain letters, digits, dots, underscores, and hyphens:
mail.box03.example.admin
postgres.box03.app1
api.box03.stripe.live
Aliases, including email-like aliases, may be declared in map files. Ambiguous aliases fail clearly.
Supported forms:
Secret ID: mail.box03.example.admin
{{secret:mail.box03.example.admin:password}}
secret://localsetup/repo/default/mail.box03.example.admin#field=password
Resolution order:
Config and map files may contain metadata, entry paths, usernames, URLs, and aliases. They must not contain passwords, tokens, key material, or passphrases.
Examples live in examples/. Contract schemas live in schemas/.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide accessibility reviews for UI, documents, and workflows. Use for WCAG-oriented audits, keyboard review, semantics, contrast, and remediation planning.
The English summary is being prepared. Showing the original description.
Use when choosing a LocalSetup Agent-* lane for exploration, research, bounded implementation, or review. Consult the static capability matrix; do not probe account or network availability.
The English summary is being prepared. Showing the original description.
Guide agent email inbox workflows with prompt-injection defenses. Use for inbound email processing, webhooks, routing, and safety review.
The English summary is being prepared. Showing the original description.
Navigate and understand codebases using agentlens hierarchical documentation. Use when exploring new projects, finding modules, locating symbols in large files, finding TODOs/warnings, or understanding code structure.
The English summary is being prepared. Showing the original description.
Use for Agent Q signed encrypted file-drop or mail ship and ingest, private registry v2 setup, queue status, and transport maintenance.
The English summary is being prepared. Showing the original description.
Inventory wrapper for the alirezarezvani Claude skills bundle. Use when triaging its broad skill catalog and large script surface before any targeted import.
The English summary is being prepared. Showing the original description.