home / skills / laurigates / claude-plugins / configure-reusable-workflows
This skill installs Claude-powered reusable GitHub Actions workflows for security, quality, and accessibility checks to quickly bootstrap project automation.
npx playbooks add skill laurigates/claude-plugins --skill configure-reusable-workflowsReview the files below or copy the command above to add this skill to your agents.
---
model: haiku
created: 2026-02-02
modified: 2026-02-11
reviewed: 2026-02-02
description: Install reusable GitHub Actions workflows for security, quality, and accessibility checks
allowed-tools: Glob, Grep, Read, Write, Edit, Bash(mkdir *), Bash(ls *), AskUserQuestion, TodoWrite
argument-hint: "[--all] [--security] [--quality] [--a11y] [--list]"
name: configure-reusable-workflows
---
# /configure:reusable-workflows
Install Claude-powered reusable GitHub Actions workflows from claude-plugins into a project.
## When to Use This Skill
| Use this skill when... | Use another approach when... |
|------------------------|------------------------------|
| Adding Claude-powered reusable workflows for security, quality, or accessibility | Setting up standard CI/CD workflows (use `/configure:workflows`) |
| Installing pre-built workflow callers from claude-plugins | Writing custom GitHub Actions workflows from scratch |
| Automating OWASP, secret scanning, or code smell detection via CI | Configuring local security scanning tools (use `/configure:security`) |
| Adding WCAG accessibility checks to pull request pipelines | Running one-off accessibility audits manually |
| Bootstrapping a full suite of Claude-powered CI checks across categories | Only need to check existing workflow compliance |
## Context
- Workflows dir: !`test -d .github/workflows && echo "EXISTS" || echo "MISSING"`
- Existing callers: !`find .github/workflows -maxdepth 1 -name 'claude-*' 2>/dev/null`
- Package files: !`find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \) -print -quit 2>/dev/null`
- TypeScript files: !`find . -maxdepth 2 \( -name '*.ts' -o -name '*.tsx' \) -print -quit 2>/dev/null`
- Component files: !`find . -maxdepth 3 \( -name '*.jsx' -o -name '*.vue' -o -name '*.svelte' \) -print -quit 2>/dev/null`
## Parameters
Parse from command arguments:
- `--all`: Install all workflows
- `--security`: Install security workflows only
- `--quality`: Install quality workflows only
- `--a11y`: Install accessibility workflows only
- `--list`: List available workflows without installing
## Available Workflows
### Security
| Workflow | Description | File |
|----------|-------------|------|
| secrets | Detect leaked secrets and credentials | `reusable-security-secrets.yml` |
| owasp | OWASP Top 10 vulnerability scanning | `reusable-security-owasp.yml` |
| deps | Dependency vulnerability audit | `reusable-security-deps.yml` |
### Quality
| Workflow | Description | File |
|----------|-------------|------|
| typescript | TypeScript strictness analysis | `reusable-quality-typescript.yml` |
| code-smell | Code smell detection | `reusable-quality-code-smell.yml` |
| async | Async/await pattern issues | `reusable-quality-async.yml` |
### Accessibility
| Workflow | Description | File |
|----------|-------------|------|
| wcag | WCAG 2.1 compliance checking | `reusable-a11y-wcag.yml` |
| aria | ARIA pattern validation | `reusable-a11y-aria.yml` |
## Execution
Execute this reusable workflow installation:
### Step 1: Detect current state
1. Check for `.github/workflows/` directory (create if missing)
2. List any existing Claude-powered workflow callers
3. Determine project type from files present
### Step 2: Select workflows
If no flags provided, ask the user which categories to install:
```
Available workflow categories:
[1] Security (secrets, owasp, deps)
[2] Quality (typescript, code-smell, async)
[3] Accessibility (wcag, aria)
[4] All workflows
Which categories? (comma-separated, e.g., 1,2):
```
If `--list` is set, print the Available Workflows tables above and stop.
### Step 3: Generate caller workflows
For each selected workflow, create a caller file in `.github/workflows/`.
**Naming convention**: `claude-<category>-<name>.yml`
Example: `claude-security-secrets.yml`
Use the caller workflow template:
```yaml
name: Claude <Category> - <Name>
on:
pull_request:
branches: [main]
workflow_dispatch:
permissions:
contents: read
pull-requests: write
id-token: write
jobs:
check:
uses: laurigates/claude-plugins/.github/workflows/reusable-<category>-<name>.yml@main
with:
# Default inputs - customize as needed
max-turns: 5
secrets: inherit
```
For complete caller workflow files per category, see [REFERENCE.md](REFERENCE.md).
### Step 4: Remind about secrets
After installation, print the required secret configuration:
```
Required secret: CLAUDE_CODE_OAUTH_TOKEN
To configure:
1. Go to repository Settings > Secrets and variables > Actions
2. Add secret: CLAUDE_CODE_OAUTH_TOKEN
3. Value: Your Claude Code OAuth token
Get token from: https://console.anthropic.com/
```
## Customization
After installation, users can customize:
| Input | Purpose | Example |
|-------|---------|---------|
| `file-patterns` | Files to scan | `'src/**/*.ts'` |
| `max-turns` | Claude analysis depth | `3` (quick) to `10` (thorough) |
| `fail-on-*` | Block merges on findings | `true` / `false` |
| `wcag-level` | Accessibility standard | `'A'`, `'AA'`, `'AAA'` |
## Post-Installation
1. **Configure secret**: Add `CLAUDE_CODE_OAUTH_TOKEN` to repository secrets
2. **Customize patterns**: Edit `file-patterns` to match project structure
3. **Adjust triggers**: Modify `paths` filters for relevant file types
4. **Test manually**: Use `workflow_dispatch` to test before PR triggers
## Agentic Optimizations
| Context | Command |
|---------|---------|
| List available workflows | `/configure:reusable-workflows --list` |
| Install all workflows at once | `/configure:reusable-workflows --all` |
| Security workflows only | `/configure:reusable-workflows --security` |
| Quality workflows only | `/configure:reusable-workflows --quality` |
| Accessibility workflows only | `/configure:reusable-workflows --a11y` |
| Check existing callers | `find .github/workflows -name 'claude-*' -type f` |
## Flags
| Flag | Description |
|------|-------------|
| `--all` | Install all workflows |
| `--security` | Install security workflows only |
| `--quality` | Install quality workflows only |
| `--a11y` | Install accessibility workflows only |
| `--list` | List available workflows without installing |
## See Also
- `/configure:workflows` - Standard CI/CD workflows (container, release-please)
- `/configure:security` - Security tooling configuration
- `ci-workflows` skill - Workflow patterns
This skill installs Claude-powered reusable GitHub Actions workflows into a repository to add automated security, code quality, and accessibility checks. It scaffolds caller workflow files that invoke centralized reusable workflows, detects project type, and reminds you of required secrets and customization points. Use flags to install specific categories or list available workflows without making changes.
The skill inspects the repository for a .github/workflows directory, existing Claude workflow callers, and key project files to infer language and structure. It then creates caller YAML files named claude-<category>-<name>.yml that reference the reusable workflow templates in the claude-plugins project. After generation it prints required secrets and recommended post-install steps.
What flags can I use to control installation?
--all, --security, --quality, --a11y to install specific groups; --list to show workflows only.
What secret is required after installation?
Add CLAUDE_CODE_OAUTH_TOKEN to repository Actions secrets. Obtain the token from your Claude Code/Anthropic console.
How are caller filenames structured?
Caller files use the pattern claude-<category>-<name>.yml, for example claude-security-secrets.yml.