Parse and export cryptographic keys across PEM, JWK, OpenSSH, and SSH2 formats.
npx skills add https://github.com/tomitribe/claude-plugins --skill churchkey
Please help me install this Agent Skill. Skill: churchkey Source: https://github.com/tomitribe/claude-plugins/tree/main/plugins/churchkey/skills/churchkey Command: npx skills add https://github.com/tomitribe/claude-plugins --skill churchkey
Managing cryptographic keys across multiple formats (PEM, JWK, OpenSSH, SSH2) can be error-prone and slow. Churchkey provides a unified API to parse, validate, and export keys, reducing format friction and inconsistency.
Install churchkey and use Keys.decode to parse a PEM, then access getAlgorithm and getFormat to inspect the key.
High-intent search queries and answers about installing and using this skill.
You can convert a PEM private key to JWK by decoding the PEM file into a common Key object and then encoding it into JWK format. This streamlines web-based API integration by translating standard cryptographic key structures into JSON Web Keys.
The best way to parse an OpenSSH public key is using an auto-detecting key decoder that reads the OpenSSH format and outputs a standard Key object. You can then extract the algorithm and format details to properly configure server access controls.
Yes, you can extract a public key from an RSA private key. The API parses the private key material and isolates the public components, allowing you to export the public key independently in PEM, JWK, OpenSSH, or SSH2 formats.
Yes, the key parsing API supports DSA, EC, and RSA algorithms. It auto-detects the key format, decodes the cryptographic material, and encodes it across PEM, JWK, OpenSSH, and SSH2 formats regardless of the underlying algorithm.
When handling unknown cryptographic key formats, the API uses auto-detection to identify the structure automatically. It provides encode and decode utilities with built-in error handling to gracefully manage unsupported or malformed key inputs.
SSH2 key export failures during format conversion usually stem from unsupported algorithms or malformed key material. The API includes error handling during the encoding process to catch these issues, ensuring only valid RSA, DSA, or EC keys are exported.
TheBushidoCollectiveEnforce encryption, key management, and access controls for Fnox secrets.
secutils-devGenerate and manage cryptographic private keys for TLS and JWT.
AshleyHollisManage Azure resources via Azure CLI for ACR, AKS, Storage, and Key Vault.
adamhjkManage SolidJS reactive primitives for custom reactive workflows.
