onepassword-cli-coder

This skill guides integrating 1Password CLI (op) for secret management in development workflows. Use when loading secrets for infrastructure, deployments, or local development.

Zur Installation springen

Repository: majesticlabs-dev/majestic-marketplace
Letzte Quellaktivität: 16. Februar 2026 um 14:50
Erkannte Sprache von SKILL.md: Englisch
Sterne: 47
Forks: 11

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill onepassword-cli-coder

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer

2 Dateien

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications. Includes framework-specific guidance for Tailwind, React, Vue, and Rails/Hotwire ecosystems.

2026-05-13

skill-structure

Skill file structure, naming conventions, directory layout, frontmatter requirements, and invocation control. Use when creating skill files or slash commands to ensure correct format and validation.

2026-05-13

devils-advocate

Forces adversarial reasoning before committing to decisions. Triggers on architectural choices, approach selection, and planning phases to prevent premature commitment bias.

2026-05-08

Alle aus diesem Repository ansehen

AWS_ACCESS_KEY_ID=op://Infrastructure/AWS/access_key_id
AWS_SECRET_ACCESS_KEY=op://Infrastructure/AWS/secret_access_key
DIGITALOCEAN_TOKEN=op://Infrastructure/DigitalOcean/api_token
DATABASE_URL=op://Production/PostgreSQL/connection_string
STRIPE_SECRET_KEY=op://Production/Stripe/secret_key

# 1Password - NEVER commit
.op.env
*.op.env

op run --env-file=.op.env -- terraform plan
op run --env-file=.op.env -- rails server

OP ?= op
OP_ENV_FILE ?= .op.env

# Prefix for all commands needing secrets
CMD = $(OP) run --env-file=$(OP_ENV_FILE) --

deploy:
	$(CMD) kamal deploy

console:
	$(CMD) rails console

migrate:
	$(CMD) rails db:migrate

op run --env-file=.op.env -- docker compose up

# config/deploy.yml
env:
  secret:
    - RAILS_MASTER_KEY
    - DATABASE_URL
    - REDIS_URL

# .kamal/secrets
RAILS_MASTER_KEY=$(op read "op://Production/Rails/master_key")
DATABASE_URL=$(op read "op://Production/PostgreSQL/url")
REDIS_URL=$(op read "op://Production/Redis/url")

# .github/workflows/deploy.yml
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: 1password/load-secrets-action@v2
        with:
          export-env: true
        env:
          OP_SERVICE_ACCOUNT_TOKEN: ${{ secrets.OP_SERVICE_ACCOUNT_TOKEN }}
          AWS_ACCESS_KEY_ID: op://CI/AWS/access_key_id
          AWS_SECRET_ACCESS_KEY: op://CI/AWS/secret_access_key

      - run: terraform apply -auto-approve

op read "op://Vault/Item/field"
op read "op://Vault/Item/field" --format json
op read "op://Vault/TLS/private_key" > /tmp/key.pem && chmod 600 /tmp/key.pem

DATABASE_URL=$(op read "op://Production/DB/url") rails db:migrate
op run --env-file=.op.env -- ./deploy.sh
op run --account my-team --env-file=.op.env -- terraform apply

op vault list
op item list --vault Infrastructure
op item get "AWS" --vault Infrastructure
op item create --category login --vault Infrastructure \
  --title "New Service" --field username=admin --field password=secret123

op signin
op vault list

cat > .op.env << 'EOF'
AWS_ACCESS_KEY_ID=op://Infrastructure/AWS/access_key_id
AWS_SECRET_ACCESS_KEY=op://Infrastructure/AWS/secret_access_key
DATABASE_URL=op://Production/Database/url
REDIS_URL=op://Production/Redis/url
EOF

op run --env-file=.op.env -- env | grep -E '^(AWS|DATABASE|REDIS)'

op item create --vault myproject --category login \
  --title "production-rails" --field master_key="PLACEHOLDER_UPDATE_BEFORE_DEPLOY"

cat > .kamal/secrets << 'EOF'
RAILS_MASTER_KEY=$(op read "op://myproject/production-rails/master_key")
EOF

# Later: update with real value
op item edit "production-rails" --vault myproject \
  master_key="actual_secret_value_here"

Vault: myproject
Items:
  - production-rails
  - production-dockerhub
  - production-hetzner-s3
  - staging-rails
  - staging-dockerhub
  - development-rails

op signin                  # Re-authenticate expired session
op whoami                  # Check current session
op vault list              # Verify vault access
op item list --vault Infrastructure | grep -i aws   # Search for items
op item get "AWS" --vault Infrastructure --format json | jq '.fields[].label'  # Check field names

op vault list --account acme.1password.com
export OP_ACCOUNT=acme.1password.com
op run --account acme.1password.com --env-file=.op.env -- ./deploy.sh

ENV ?= development
OP_ENV_FILE = .op.env.$(ENV)

deploy:
	op run --env-file=$(OP_ENV_FILE) -- kamal deploy
# Usage: make deploy ENV=production

Pattern	Example	Bad Alternative
`{env}-{service}`	`production-rails`	`Production Rails`
`{env}-{provider}`	`production-dockerhub`	`API Key`
`{env}-{provider}-{resource}`	`production-hetzner-s3`	Mixed env items

Pattern	Example	Bad Alternative
`{env}-{service}`	`production-rails`	`Production Rails`
`{env}-{provider}`	`production-dockerhub`	`API Key`
`{env}-{provider}-{resource}`	`production-hetzner-s3`	Mixed env items

Vault	Purpose	Access
`Infrastructure`	Cloud provider credentials	DevOps team
`Production`	Production app secrets	Deploy systems
`Staging`	Staging environment	Dev team
`Development`	Local dev secrets	Individual devs

onepassword-cli-coder

Installationsoptionen

Quelldateien prüfen

Core Patterns

Secret Reference Format

Item Naming Conventions

Field Naming

Core Patterns

Secret Reference Format

Item Naming Conventions

Field Naming

Environment File (.op.env)

Running Commands with Secrets

Integration Patterns

Makefile Integration

Docker Compose

Kamal Deployment

CI/CD (GitHub Actions)

CLI Commands

Reading Secrets

Injecting into Commands

Managing Items

Project Setup

Initial Configuration

Placeholder Workflow

Vault Organization

Security Rules

Troubleshooting

Multiple Accounts

Multi-Environment Pattern

References

name	onepassword-cli-coder
description	This skill guides integrating 1Password CLI (op) for secret management in development workflows. Use when loading secrets for infrastructure, deployments, or local development.
allowed-tools	Read Write Edit Bash Grep Glob

onepassword-cli-coder

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Mehr aus diesem Repository

Core Patterns

Secret Reference Format

Item Naming Conventions

Field Naming

Core Patterns

Secret Reference Format

Item Naming Conventions

Field Naming

Environment File (.op.env)

Running Commands with Secrets

Integration Patterns

Makefile Integration

Docker Compose

Kamal Deployment

CI/CD (GitHub Actions)

CLI Commands

Reading Secrets

Injecting into Commands

Managing Items

Project Setup

Initial Configuration

Placeholder Workflow

Vault Organization

Security Rules

Troubleshooting

Multiple Accounts

Multi-Environment Pattern

References