Background
30 workflows use the agentic-workflows: tool, and 17 of these share an almost identical tool stack: agentic-workflows + cli-proxy: true + github: mode: gh-proxy. This pattern is copy-pasted without a shared abstraction, making configuration changes error-prone and inconsistent.
Problem
No shared component exists for the meta-analysis tool stack. Every workflow that analyzes other workflows repeats the same frontmatter, differing only in toolset selection and memory branch name.
Representative examples (17 workflows with all 3 tools):
agent-performance-analyzer.md
audit-workflows.md
aw-failure-investigator.md
daily-subagent-optimizer.md
prompt-clustering-analysis.md
workflow-normalizer.md
- ... and 11 more
Proposed Shared Component
Path: shared/meta-analysis-base.md
---
# Meta-Analysis Base - Standard tool stack for workflows that analyze other agentic workflows.
# Bundles: agentic-workflows tool + cli-proxy + GitHub MCP in gh-proxy mode.
#
# Usage:
# imports:
# - uses: shared/meta-analysis-base.md
# with:
# toolsets: [default, actions, repos] # optional, default: [default]
import-schema:
toolsets:
type: array
default: [default]
description: "GitHub MCP toolsets to enable (e.g. [default, actions, repos])"
tools:
cli-proxy: true
agentic-workflows:
github:
mode: gh-proxy
toolsets: ${{ github.aw.import-inputs.toolsets }}
---
**IMPORTANT**: When analyzing agentic workflows, use the `agentic-workflows` tool to read workflow files and the `mcpscripts-gh` tool for GitHub CLI commands.
Estimated Impact
- Workflows affected: 17–30 workflows
- Lines saved: ~5–8 lines per workflow = 85–240 lines eliminated
- Maintenance benefit: Changing
gh-proxy config or adding a new default toolset only requires one file edit
Migration Plan
- Create
shared/meta-analysis-base.md with the content above
- Audit the 17 workflows using the full stack — add
imports: - uses: shared/meta-analysis-base.md with: toolsets: [...] and remove the duplicated cli-proxy, agentic-workflows, and github: blocks
- For the 13 workflows using partial stacks, evaluate case-by-case
- Recompile all workflows with
make recompile
Example Usage After Migration
imports:
- uses: shared/meta-analysis-base.md
with:
toolsets: [default, actions, repos]
- shared/reporting.md
Priority: High — 30 workflows affected, low extraction complexity
Generated by Workflow Skill Extractor · ● 18.4M · ◷
Background
30 workflows use the
agentic-workflows:tool, and 17 of these share an almost identical tool stack:agentic-workflows+cli-proxy: true+github: mode: gh-proxy. This pattern is copy-pasted without a shared abstraction, making configuration changes error-prone and inconsistent.Problem
No shared component exists for the meta-analysis tool stack. Every workflow that analyzes other workflows repeats the same frontmatter, differing only in toolset selection and memory branch name.
Representative examples (17 workflows with all 3 tools):
agent-performance-analyzer.mdaudit-workflows.mdaw-failure-investigator.mddaily-subagent-optimizer.mdprompt-clustering-analysis.mdworkflow-normalizer.mdProposed Shared Component
Path:
shared/meta-analysis-base.mdEstimated Impact
gh-proxyconfig or adding a new default toolset only requires one file editMigration Plan
shared/meta-analysis-base.mdwith the content aboveimports: - uses: shared/meta-analysis-base.md with: toolsets: [...]and remove the duplicatedcli-proxy,agentic-workflows, andgithub:blocksmake recompileExample Usage After Migration
Priority: High — 30 workflows affected, low extraction complexity