bootstrap-workflow-dispatch SKILL.md skillB
bootstrap-workflow-dispatch from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/bootstrap-workflow-dispatch@git:20261014.0f16275Pins git:20261014.0f16275 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/bootstrap-workflow-dispatch/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.0f16275, committed Oct 14, 2026
- First version recorded
- Aug 12, 2026
- Size
- 3,742 bytes
- Repository stars
- 22
- License
- MIT
Temporarily bootstrap a newly renamed or newly added `workflow_dispatch` workflow so GitHub can dispatch it before the workflow exists on the default branch. Use when `gh workflow run <file>.yml` returns `workflow ... not found on the default branch` for a feature branch, especially right after renaming or introducing a dispatch-only workflow.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
GitHub does not reliably expose a brand-new `workflow_dispatch` workflow to `gh workflow run` until that workflow has been seen by Actions metadata at least once. Before merge, the default branch still points at the old workflow set, so a feature branch can hit: ```text HTTP 404: workflow <file>.yml not found on the default branch ``` The workaround is a **one-shot branch-scoped push trigger** that causes exactly one non-dispatch run on the feature branch, registering the workflow so later `workflow_dispatch` calls succeed. ## Step 0 — confirm the failure mode Verify the workflow is blocked for the expected reason: ```bash gh workflow run <workflow-file>.yml --ref "$(git branch --show-current)" ``` If the error is `workflow ... not found on the default branch`, continue. If the failure is about bad inputs, missing permissions, or YAML syntax, fix that instead — this skill is only for the metadata-registration problem. ## Step 1 — add the one-shot push trigger Edit the workflow file and add a temporary `push` trigger next to `workflow_dispatch`, scoped to: - the **current feature branch name**, and - the workflow file's own path Pattern: ```yaml on: …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/bootstrap-workflow-dispatch@sha256:00d449eaa9f6dca6The line at the top of this page pins the label git:20261014.0f16275, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fhngmw3wo253wqr3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 12, 2026 and Oct 14, 2026, about one every 63 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.0f16275 latest | 2026-10-14 | 0f16275 | 3,742 B | B | view · diff |
| git:20260812.5a86cca | 2026-08-12 | 5a86cca | 3,742 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3742 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fhngmw3wo253wqr3 GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/bootstrap-workflow-dispatch GET https://markdownregistry.com/api/v1/blob/00d449eaa9f6dca6a42cfd0741e626f26a84d1f583543c2d4eba70522de725a2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.