New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Managing Workflow Secrets

by bitwarden in bitwarden/ai-plugins

Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…

OfficialCustom licenceAuto-check passedDevOps & Cloud

Install Managing Workflow Secrets

skills CLI
$ npx skills add bitwarden/ai-plugins --skill managing-workflow-secrets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwarden/ai-plugins managing-workflow-secrets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bitwarden-devops-engineer/skills/managing-workflow-secrets .claude/skills/managing-workflow-secrets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managing-workflow-secrets
GitHub stars
154
Token cost
~4k tokens
SKILL.md length
1,817 words
Files
13 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
Custom licence

At a glance

Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…

  • Works in 5 steps: Internal actions float on @main;… → Any job that logs in declares id-token:… → Only three GitHub secrets exist for auth… → …
  • Questions like add a step to pull the DockerHub token from Key Vault before we push the image
  • SKILL.md covers Boundaries, Secret exposure is the…, The AKV + OIDC lifecycle and Golden rules (invariants), plus 4 more sections
  • Calls az and gh

What it does

Managing Workflow Secrets is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions composite actions (azure-login → get-keyvault-secrets → azure-logout), consume it safely, and get it beyond the job or into a reusable workflow when needed. Use when questions like "add a step to pull the DockerHub token from Key Vault before we push the image", "do I need id-token: write on this job that logs in to Azure", or…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `evals/README.md`, `evals/evals.json` and `evals/files/app-token-cross-job.yml`).

It sits in DevOps & Cloud, covering CI/CD, Linting and formatting and OAuth and OpenID Connect. It works with Azure Key Vault, Microsoft Azure and GitHub Actions. The repository describes itself as: AI plugin marketplace.

When your agent uses it

  • Questions like add a step to pull the DockerHub token from Key Vault before we push the image
  • Do I need id-token: write on this job that logs in to Azure
  • My deploy job cant see the secret the build job retrieved come up

Example prompts

  • “do I need id-token: write on this job that logs in to Azure”
  • “my deploy job can”
  • “/managing-workflow-secrets”

Requirements

  • Docker
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Edit

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Internal actions float on @main; third-party actions are SHA-pinned. Every
  2. Any job that logs in declares id-token: write. OIDC federated login fails without it. Keep
  3. Only three GitHub secrets exist for auth — the OIDC triad. AZURE_SUBSCRIPTION_ID,
  4. Always pair azure-login with azure-logout, and match their conditions. Omitting logout
  5. Treat secret exposure as the thing that matters most — see "Secret exposure is the overriding

What it can do on your machine

Read from SKILL.md and the folder at commit 53e22a3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • az
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use az and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Workflow Secrets loads about 4k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 200 tokens; SKILL.md has 1,817 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~200
When it runs · the whole SKILL.md, loaded when a task matches
~4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,817 words (~4,022 tokens).

“The three-action pattern is the standard across Bitwarden's CI, CD, and operational workflows — treat any other retrieval mechanism in a Bitwarden workflow as a finding.”

— opening of SKILL.md by bitwarden, Custom licence
name
managing-workflow-secrets
allowed-tools
Read, Glob, Grep, Edit

Read the full SKILL.md on GitHub

Files

SKILL.md and 12 other files (references) in plugins/bitwarden-devops-engineer/skills/managing-workflow-secrets of bitwarden/ai-plugins.

  • SKILL.md
  • evals/README.md
  • evals/evals.json
  • evals/files/app-token-cross-job.yml
  • evals/files/build-acr.yml
  • evals/files/build-and-push.yml
  • evals/files/caller-workflow.yml
  • evals/files/deploy-cant-see-secret.yml
  • evals/files/deploy-datadog.yml
  • evals/files/leaky-secret.yml
  • evals/files/multi-secret-deploy.yml
  • evals/results/SNAPSHOT.md
  • references/actions.md

Open the folder on GitHubat commit 53e22a3

Compare with similar skills

Managing Workflow Secrets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing Workflow Secrets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managing Workflow Secrets this skillbitwarden/ai-plugins154—~4kAutomated safety check: PassCustom licence
Azure Bicep Skilltimothywarner-org/claude-code224—~2.9kAutomated safety check: PassMIT
Nuget Trusted Publishingdotnet/skills5.6k2 repos~2.3kAutomated safety check: PassMIT
CD Pipeline GeneratorArabelaTso/Skills-4-SE253—~1.3kAutomated safety check: PassApache-2.0
GitHub Actions Hardeninggithub/awesome-copilot40k1 repos~2.4kAutomated safety check: PassMIT
Python Pypi Package Buildergithub/awesome-copilot40k1 repos~4.6kAutomated safety check: PassMIT

Similar skills

  • Azure Bicep Skill

    timothywarner-org/claude-code

    A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.

    224 GitHub stars~2.9k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Nuget Trusted Publishing

    dotnet/skills

    Official

    Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens.

    5.6k GitHub starsUsed in 2 repos~2.3k tokens
    DevOps & CloudAuto-check passed

  • CD Pipeline Generator

    ArabelaTso/Skills-4-SE

    Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure).

    253 GitHub stars~1.3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • GitHub Actions Hardening

    github/awesome-copilot

    Official

    Security hardening reviewer for GitHub Actions workflow files (.github/workflows/.yml).

    40k GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    DevelopmentAuto-check passed

  • GitHub Actions Creator

    FNOSP/FlyNarwhal

    A skill your agent uses when the user wants to create, generate, or set up a GitHub Actions workflow.

    495 GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed

More from bitwarden/ai-plugins

All 33 skills in this repo

  • Reviewing Claude Config

    bitwarden/ai-plugins

    Official

    Reviews Claude configuration files for security, structure, and prompt engineering quality.

    154 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Reviewing Security Architecture

    bitwarden/ai-plugins

    Official

    This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…

    154 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Auditing External Claude Plugins

    bitwarden/ai-plugins

    Official

    Audits an external (third-party) Claude Code plugin pinned in this marketplace for security risk before it is vendored, and writes the report to a file for downstream posting.

    154 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Action Audit

    bitwarden/ai-plugins

    Official

    Audit GitHub Actions action usage across an org. An agent skill from bitwarden/ai-plugins.

    154 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Action Remediate

    bitwarden/ai-plugins

    Official

    Remediate GitHub Actions action findings identified by the action-audit skill.

    154 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Addressing Code Review Comments

    bitwarden/ai-plugins

    Official

    A skill your agent uses when the user is addressing pull request review comments locally and asks for help evaluating, implementing, or drafting responses to reviewer feedback - requires technical…

    154 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Managing Workflow Secrets

What does Managing Workflow Secrets do?

Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…. Managing Workflow Secrets is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions composite actions (azure-login → get-keyvault-secrets → azure-logout), consume it safely, and get it beyond the job or into a reusable workflow when needed.

When should I use Managing Workflow Secrets?

Managing Workflow Secrets fits situations like: questions like add a step to pull the DockerHub token from Key Vault before we push the image; do I need id-token: write on this job that logs in to Azure; my deploy job cant see the secret the build job retrieved come up.

How do I install Managing Workflow Secrets in Claude Code?

Run `npx skills add bitwarden/ai-plugins --skill managing-workflow-secrets -a claude-code`. Or copy the skill folder (plugins/bitwarden-devops-engineer/skills/managing-workflow-secrets in bitwarden/ai-plugins) into .claude/skills/managing-workflow-secrets in your project. Claude Code loads it when a task matches its description.

How do I install Managing Workflow Secrets in Codex?

Run `npx skills add bitwarden/ai-plugins --skill managing-workflow-secrets -a codex`. Or copy the skill folder (plugins/bitwarden-devops-engineer/skills/managing-workflow-secrets in bitwarden/ai-plugins) into .agents/skills/managing-workflow-secrets in your project. Codex loads it when a task matches its description.

Can I use Managing Workflow Secrets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwarden/ai-plugins --skill managing-workflow-secrets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-workflow-secrets, .gemini/skills/managing-workflow-secrets, .github/skills/managing-workflow-secrets and .opencode/skills/managing-workflow-secrets in your project.

What does Managing Workflow Secrets need to run?

Going by SKILL.md and its folder, Managing Workflow Secrets needs the command-line tools its instructions call (az and gh). Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Glob, Grep, Edit.

Does Managing Workflow Secrets access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Managing Workflow Secrets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managing Workflow Secrets use?

Managing Workflow Secrets has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Managing Workflow Secrets use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Managing Workflow Secrets?

Skills that share tags, products or a category with Managing Workflow Secrets: Azure Bicep Skill (timothywarner-org/claude-code, 224 stars), Nuget Trusted Publishing (dotnet/skills, 5.6k stars), CD Pipeline Generator (ArabelaTso/Skills-4-SE, 253 stars) and GitHub Actions Hardening (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Workflow Secrets?

bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ai-plugins, which has 154 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.

Source: bitwarden/ai-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.