os-keychain

Integrate applications with OS-native keychain services for secure credential storage.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill os-keychain-probably-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-keychain
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/os-keychain
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill os-keychain-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OS keychain integration prevents secrets from being exposed through hardcoding, environment variables, or insecure files by routing credential storage to the platform’s secure vault.

Core Features & Use Cases

  • Secure secret storage guidance: Enforces using macOS Keychain, Windows Credential Manager, or Linux Secret Service for sensitive tokens and passwords instead of plaintext approaches, covering common mistakes like CWE-522 and CWE-798.
  • Cross-platform credential handling patterns: Provides code-generation rules and platform-specific behaviors (service identifiers, key naming validation, least-privilege, and error handling) for Rust, Python, and Node.js/TypeScript.
  • Fail-secure and safe operational flows: Requires validation, avoids leaking secrets in logs/errors, and mandates fail-closed behavior when keychain access is unavailable.

Quick Start

Use the os-keychain skill when you need to securely store an API token in the user’s platform credential store rather than in code, config files, or environment variables.

Frequently Asked Questions about os-keychain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store API tokens securely in Rust, Python, or Node.js using the OS keychain?

To store API tokens securely in the OS keychain, route credential persistence to platform-native services like macOS Keychain, Windows Credential Manager, or Linux Secret Service using Rust, Python, or Node.js/TypeScript code patterns that enforce encryption at rest.

What is the best way to handle cross-platform credential storage without hardcoding secrets?

Cross-platform credential storage is best handled by integrating OS-native keychain services, which prevents insecure hardcoding and plaintext environment variables by routing sensitive tokens to the platform's secure vault with strict key name validation.

Does OS keychain integration support Python and Node.js on Windows, macOS, and Linux?

OS keychain integration supports Python and Node.js/TypeScript across Windows, macOS, and Linux by providing platform-specific behaviors and code-generation rules for accessing Windows Credential Manager, macOS Keychain, and Linux Secret Service.

What happens to credential storage when the OS keychain is unavailable?

When the OS keychain is unavailable, credential storage must fail-secure by halting operations and avoiding insecure fallbacks, ensuring no secrets are leaked in logs or errors and preventing unprotected plaintext storage.

Why should I use the OS keychain instead of environment variables for secret management?

You should use the OS keychain instead of environment variables for secret management because environment variables expose secrets to plaintext access, whereas keychain services provide protected persistence, validation, isolation, and encryption at rest.

How does key naming validation work for secure credential storage in cross-platform applications?

Key naming validation for secure credential storage requires reverse-domain service identifiers and strict key name rules in cross-platform applications, ensuring proper isolation and least-privilege access when interacting with OS-native keychain services.