agentleFS
tiulpintiulpin/instill/.github/skills/agentic-workflows/SKILL.md

agentic-workflows

Skill0 starsChanged 8 days agoMITView on GitHub

Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.

76 other projects use a version of this, 71 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use agentic-workflow-designer, speckit-taskstoissues and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GitHubSkill

    agentic-workflow-designer

    Conversational skill that interviews users to design new agentic workflows

    Also in 5 projects that use this

  • Microsoft AzureSkill

    speckit-taskstoissues

    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    speckit-analyze

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

    Also in 3 projects that use this

  • +7 more from Azure

The file

We split this skill into the rules it gives an agent

11 rules. 2 are common, 0 are distinctive, and 9 are very specific to this project.

  • 2

    Common

    Most of the 72 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when a user asks to design, create, update, debug, or upgrade GitHub Agentic Workflows in this repository.

    line 8
  2. Very specific:

    Read only the files you need: Use a local guidance checkout only when its repository/ref matches the requested guidance.

    line 28
  3. Very specific:

    Use a local guidance checkout only when its repository/ref matches the requested guidance.

    line 29
  4. Common:

    After loading the matching workflow prompt or skill, follow it directly:

    line 125
  5. Very specific:

    Create new workflows: .github/aw/create-agentic-workflow.md

    line 127
  6. Very specific:

    Update existing workflows: .github/aw/update-agentic-workflow.md

    line 129
  7. Very specific:

    Create shared components or MCP wrappers: .github/aw/create-shared-agentic-workflow.md

    line 134
  8. Very specific:

    Create report-generating workflows: .github/aw/report.md

    line 135
  9. Very specific:

    Add skills or agent plugins requested by the user (skills: / plugins: frontmatter, never on-the-fly installs): .github/aw/skills.md

    line 145
  10. Very specific:

    When the task involves OTEL, OTLP, traces, observability backends, or telemetry-driven analysis, also read and follow …

    line 147
  11. Very specific:

    When creating, updating, diagnosing or upgrading a workflow that uses tools.work-queue, also load .github/aw/work-queue.md after the …

    line 149

“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agentic Workflows Router

Use this skill when a user asks to design, create, update, debug, or upgrade GitHub Agentic Workflows in this repository.

This skill is a dispatcher: identify the task type, load the matching workflow prompt/skill file, and follow it directly. Keep responses concise and ask a clarifying question if the correct prompt is unclear.

For debugging sessions needing CLI setup or run-URL scoping, first load https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/debug-bootstrap.md; it bootstraps the same shared strategy used by the debugging routes below.

Debugging, incident, health, and failure-related optimization requests use the bootstrap's intent routing before generic update, upgrade, or optimization routes, even when the CLI is installed. Preserve the supplied guidance repository/ref for all debugging links and public raw fallbacks; URLs showing main below are defaults only when no guidance revision is supplied. Reuse already-loaded guides. The intent index is .github/aw/debug-scenarios.md; load only the selected specialized route, not every debugging reference.

Repository overlay (optional):

  • Load the target repository's .github/aw/instructions.md, if present, after the matched prompt/skill. Use @.github/aw/instructions.md only in a matching checkout; do not substitute a guidance-repository overlay.
  • Precedence: repository overlay instructions override upstream defaults when they conflict.

Read only the files you need: Use a local guidance checkout only when its repository/ref matches the requested guidance; otherwise use the resolved guidance repository/ref (default github/gh-aw). If GitHub API, gh api, or GitHub MCP downloads return HTTP 403 (including a token SAML-authorized for a different organization), do not retry with the same token. Fetch the public file without authentication from https://raw.githubusercontent.com/github/gh-aw/main/<path> instead, preserving its repository-relative path (including .github/). For example: curl --fail --silent --show-error --location 'https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/create-agentic-workflow.md'. Use the same fallback for referenced instructions and SKILL.md files; never send an Authorization header or token to the raw URL. If the public download fails, report that error rather than proceeding without the required instructions. This fallback is for public github/gh-aw content only, not private or enterprise repositories.

  • .github/aw/action-container-substitutions.md
  • .github/aw/agent-runtime-instructions.md
  • .github/aw/agentic-chat.md
  • .github/aw/agentic-workflows-mcp.md
  • .github/aw/analyzing-runs.md
  • .github/aw/asciicharts.md
  • .github/aw/campaign.md
  • .github/aw/charts-trending.md
  • .github/aw/charts.md
  • .github/aw/cli-commands.md
  • .github/aw/compat.md
  • .github/aw/configure-agentic-engine.md
  • .github/aw/context.md
  • .github/aw/create-agentic-workflow-trigger-details.md
  • .github/aw/create-agentic-workflow.md
  • .github/aw/create-shared-agentic-workflow.md
  • .github/aw/debug-agentic-workflow.md
  • .github/aw/debug-bootstrap.md
  • .github/aw/debug-compilation.md
  • .github/aw/debug-live-testing.md
  • .github/aw/debug-model-engine-misconfiguration.md
  • .github/aw/debug-playbook.md
  • .github/aw/debug-scenarios.md
  • .github/aw/debug-security-review.md
  • .github/aw/debug-workflow-evidence.md
  • .github/aw/debug-workflow-health.md
  • .github/aw/dependabot.md
  • .github/aw/deployment-status.md
  • .github/aw/designer-mappings.md
  • .github/aw/designer.md
  • .github/aw/doctor.md
  • .github/aw/documentation-workflows.md
  • .github/aw/drive-memory.md
  • .github/aw/enclaves.md
  • .github/aw/evals.md
  • .github/aw/experiments.md
  • .github/aw/formal-methods.md
  • .github/aw/github-agentic-workflows.md
  • .github/aw/github-mcp-server-pagination.md
  • .github/aw/github-mcp-server-tools.md
  • .github/aw/github-mcp-server.md
  • .github/aw/harbor.md
  • .github/aw/instructions.md
  • .github/aw/intent.md
  • .github/aw/jobs.md
  • .github/aw/ledger.md
  • .github/aw/linter-workflows.md
  • .github/aw/llms.md
  • .github/aw/loop.md
  • .github/aw/lsp.md
  • .github/aw/maintainer.md
  • .github/aw/mcp-clis.md
  • .github/aw/memory-stateful-patterns.md
  • .github/aw/memory.md
  • .github/aw/messages.md
  • .github/aw/multi-agent-research.md
  • .github/aw/network.md
  • .github/aw/optimize-agentic-workflow.md
  • .github/aw/otel.md
  • .github/aw/patterns.md
  • .github/aw/playwright.md
  • .github/aw/pr-reviewer.md
  • .github/aw/release-workflow.md
  • .github/aw/report.md
  • .github/aw/reuse.md
  • .github/aw/safe-outputs-automation.md
  • .github/aw/safe-outputs-content.md
  • .github/aw/safe-outputs-management.md
  • .github/aw/safe-outputs-runtime.md
  • .github/aw/safe-outputs.md
  • .github/aw/serena-tool.md
  • .github/aw/shared-safe-jobs.md
  • .github/aw/skills.md
  • .github/aw/subagents.md
  • .github/aw/syntax-agentic.md
  • .github/aw/syntax-checkout.md
  • .github/aw/syntax-core.md
  • .github/aw/syntax-engine.md
  • .github/aw/syntax-tools-imports.md
  • .github/aw/syntax.md
  • .github/aw/test-coverage.md
  • .github/aw/test-expression.md
  • .github/aw/token-optimization-caching-budgets.md
  • .github/aw/token-optimization-observability.md
  • .github/aw/token-optimization.md
  • .github/aw/triggers.md
  • .github/aw/update-agentic-workflow.md
  • .github/aw/upgrade-agentic-workflows.md
  • .github/aw/visual-regression.md
  • .github/aw/work-queue.md
  • .github/aw/workflow-constraints.md
  • .github/aw/workflow-editing.md
  • .github/aw/workflow-patterns.md

After loading the matching workflow prompt or skill, follow it directly:

  • Design workflows from scratch via interview: .github/aw/designer.md
  • Create new workflows: .github/aw/create-agentic-workflow.md
  • Configure or add declarative engines: .github/aw/configure-agentic-engine.md
  • Update existing workflows: .github/aw/update-agentic-workflow.md
  • Diagnose, patch, audit, or actively debug workflows: .github/aw/debug-agentic-workflow.md (local-first strategy, evidence triage and live gates)
  • Analyze existing runs, logs, or recurring failures: .github/aw/analyzing-runs.md. General repository-wide debugging or optimization requests start here with failure clustering before selecting a workflow.
  • AWF model/endpoint 400s, silent cross-family sub-agent failures, model: auto failures, install-step 404s after a version pin, or questions about version fields: go directly to .github/aw/debug-agentic-workflow.md#model-and-engine-misconfiguration before suggesting model changes.
  • Upgrade workflows and fix deprecations: .github/aw/upgrade-agentic-workflows.md
  • Create shared components or MCP wrappers: .github/aw/create-shared-agentic-workflow.md
  • Create report-generating workflows: .github/aw/report.md
  • Fix Dependabot manifest PRs: .github/aw/dependabot.md
  • Analyze coverage workflows: .github/aw/test-coverage.md
  • Render compact markdown charts: .github/aw/asciicharts.md
  • Map CLI commands to MCP usage: .github/aw/cli-commands.md
  • Choose workflow architecture and patterns: .github/aw/patterns.md
  • Design, deploy, inspect or recover a Git-backed work queue: .github/aw/work-queue.md
  • Optimize token usage and cost: .github/aw/token-optimization.md
  • Advanced cost controls without native settings (custom AIC allowances by server size or shared organization budget policies): read docs/src/content/docs/reference/cost-management.md#configure-advanced-cost-controls-with-admission (published guidance). Explain the external authority requirement and cooperative limits; do not invent frontmatter fields or promise hard caps, reservations, or mid-run cancellation.
  • Design long-running multi-agent research workflows: .github/aw/multi-agent-research.md
  • Add skills or agent plugins requested by the user (skills: / plugins: frontmatter, never on-the-fly installs): .github/aw/skills.md

When the task involves OTEL, OTLP, traces, observability backends, or telemetry-driven analysis, also read and follow skills/otel-queries/SKILL.md after loading the matching workflow prompt or skill.

When creating, updating, diagnosing or upgrading a workflow that uses tools.work-queue, also load .github/aw/work-queue.md after the primary prompt. Load deployment docs, operator reference or specification only when that task needs them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.