op-aws-windows-wsl

Manage AWS/Azure/API credentials and SSH workflows across Windows and WSL using 1Password CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/unnowataru/codex-skills --skill op-aws-windows-wsl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: op-aws-windows-wsl
Source: https://github.com/unnowataru/codex-skills/tree/main/op-aws-windows-wsl
Command: npx skills add https://github.com/unnowataru/codex-skills --skill op-aws-windows-wsl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Securely manage AWS/Azure/API credentials and SSH workflows across Windows and WSL using 1Password.

Core Features & Use Cases

  • Cross-OS credential provisioning and bridging between Windows and WSL using 1Password CLI.
  • Ephemeral environment variables for AWS/Azure/Google AI Studio/GitHub workflows without exposing secrets.
  • SSH agent integration and WSL bridge utilities to run commands from Windows with secret references.

Quick Start

Create an AWS API Credential item and generate an environment file to bootstrap a session across Windows and WSL.

Frequently Asked Questions about op-aws-windows-wsl

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

FAQPage Schema
How do I securely manage AWS credentials across Windows and WSL?

This Skill bridges Windows and WSL to provision ephemeral environment variables for AWS credentials using 1Password CLI, ensuring secrets are not exposed during cross-OS sessions.

Can I use 1Password for SSH authentication in WSL from Windows?

Yes, by utilizing SSH agent integration and WSL bridge utilities, you can run Windows commands with 1Password secret references to authenticate SSH sessions within WSL.

How do I set up ephemeral environment variables for Azure workflows?

You generate an environment file from an API Credential item to bootstrap on-demand ephemeral environment variables for Azure workflows, preventing permanent secret exposure.

Does this approach require 1Password CLI to provision cloud credentials?

Yes, the credential bridging and environment-file generation rely explicitly on 1Password CLI integration to securely fetch and inject secrets across Windows and WSL.

What is the best way to share API secrets between Windows PowerShell and WSL?

The best way is using a WSL bridge with PowerShell scripts to generate environment files using date-field conventions for API Credential items, securely passing secrets across the OS boundary.

Are there limitations when bridging cloud credentials between operating systems?

A key limitation is the strict dependency on 1Password CLI integration and specific date-field conventions for API Credential items to correctly generate environment files across operating systems.