How do I install the Workflow Audit skill?

Run npx skillmds@latest add bitwarden/workflow-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workflow Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflow Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflow Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workflow Audit?

bitwarden (@bitwarden) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflow Audit by bitwarden — Agent Skill

Name: Workflow Audit
Rating: 4.2 (5 reviews)
Author: bitwarden

Workflow Audit

Run the Bitwarden workflow linter (bwwl) against one or more repos and report findings. Strictly read-only — does not modify any files. Categorizes findings as mechanical or judgment using the bitwarden-workflow-linter-rules skill. Supports single repo, multiple repos, or single file/directory scope. <example> User: Run the workflow linter on the server repo Action: Trigger workflow-audit for that repo </example> <example> User: Lint the workflows across server, clients, and android Action: Trigger workflow-audit in multi-repo mode </example>

bitwarden e0cd7b3 2.6 KB Updated Sep 10, 2026

File contents

Rules

This skill is strictly read-only. Do not modify, create, or delete any files.
Flag uncertainty. If a finding is ambiguous, note it in the report rather than guessing.

Step 1: Verify Prerequisites

Check if bwwl is available:

bwwl --version

If the command is not found, stop and inform the user that bwwl must be installed before continuing. Do not attempt to install it.

Step 2: Determine Scope

Parse the user's request to determine what to lint:

Single file or directory (e.g., .github/workflows/build.yml or .github/workflows/): Operate on the current repo only.
Multiple repos (e.g., "server, clients, android"): Operate on each repo sequentially. Ask the user for the base directory where their repos are cloned. For each repo, look for its local clone at <base-dir>/<repo>. If a clone is not found, inform the user and skip that repo.
No specific target: Lint all files in .github/workflows/ of the current directory.

Step 3: Run the Linter

For each repo in scope, run:

bwwl lint -f .github/workflows/

Capture both stdout and stderr. If operating on multiple repos, announce which repo is being linted.

Step 4: Parse and Categorize Findings

From the linter output, produce a structured list of findings. Group by file and rule. Consult the bitwarden-workflow-linter-rules skill to categorize each finding:

Mechanical (can be auto-fixed):

name_capitalized, permissions_exist, pinned_job_runner, step_pinned, underscore_outputs, job_environment_prefix, check_pr_target
Simple run_actionlint findings (single-line shell fixes)

Judgment (requires user input):

name_exists, step_approved, complex run_actionlint findings

Step 5: Report

Output a summary table per repo:

File	Finding	Rule	Category
...	...	...	...

Include totals: mechanical findings, judgment findings, and repos with no issues.

Inform the user that they can use the workflow-fix skill to apply fixes based on these findings.

---name: workflow-auditdescription: Run the Bitwarden workflow linter (bwwl) against one or more repos and report findings. Strictly read-only — does not modify any files. Categorizes findings as mechanical or judgment using the bitwarden-workflow-linter-rules skill. Supports single repo, multiple repos, or single file/directory scope. <example> User: Run the workflow linter on the server repo Action: Trigger workflow-audit for that repo </example> <example> User: Lint the workflows across server, clients, and android Action: Trigger workflow-audit in multi-repo mode </example>---## Rules- **This skill is strictly read-only.** Do not modify, create, or delete any files.- **Flag uncertainty.** If a finding is ambiguous, note it in the report rather than guessing.## Step 1: Verify PrerequisitesCheck if `bwwl` is available:```bashbwwl --version```If the command is not found, stop and inform the user that `bwwl` must be installed before continuing. Do not attempt to install it.## Step 2: Determine ScopeParse the user's request to determine what to lint:- **Single file or directory** (e.g., `.github/workflows/build.yml` or `.github/workflows/`): Operate on the current repo only.- **Multiple repos** (e.g., "server, clients, android"): Operate on each repo sequentially. Ask the user for the base directory where their repos are cloned. For each repo, look for its local clone at `<base-dir>/<repo>`. If a clone is not found, inform the user and skip that repo.- **No specific target**: Lint all files in `.github/workflows/` of the current directory.## Step 3: Run the LinterFor each repo in scope, run:```bashbwwl lint -f .github/workflows/```Capture both stdout and stderr. If operating on multiple repos, announce which repo is being linted.## Step 4: Parse and Categorize FindingsFrom the linter output, produce a structured list of findings. Group by file and rule. Consult the `bitwarden-workflow-linter-rules` skill to categorize each finding:**Mechanical** (can be auto-fixed):- `name_capitalized`, `permissions_exist`, `pinned_job_runner`, `step_pinned`, `underscore_outputs`, `job_environment_prefix`, `check_pr_target`- Simple `run_actionlint` findings (single-line shell fixes)**Judgment** (requires user input):- `name_exists`, `step_approved`, complex `run_actionlint` findings## Step 5: ReportOutput a summary table per repo:| File | Finding | Rule | Category || ---- | ------- | ---- | -------- || ... | ... | ... | ... |Include totals: mechanical findings, judgment findings, and repos with no issues.Inform the user that they can use the `workflow-fix` skill to apply fixes based on these findings.

Frequently asked questions