workflow-client-bootstrap skillA
workflow-client-bootstrap is agent-read markdown (skill) from ulises-jeremias/agent-toolkit: WHAT — Interactive interview to capture client delivery context and store it inside the user's.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Workflow Client Bootstrap Use this skill to **create or update** a client-specific delivery context for any project. It runs a structured interview and stores the result inside the user’s **workspace** (`~/.ai-workspace`, `~/.ai-workspace`, or a workspace-like directory) as **packs + knowledge** (not new skills). **All generated files, PR text, and Jira/ClickUp comments must be in English.** ## When to use - Onboarding a new client project that needs its own delivery workflow (beyond `workflow-generic-project`) - Updating an existing workflow with new lifecycle states, repos, or guardrails - Documenting a client's ticket lifecycle so future agent sessions can use correct status transitions ## Do not use when - The project already has an up-to-date workflow skill and only a ticket or code change is needed - The work fits entirely within `workflow-generic-project` without client-specific gates ## Interview process Read `questions.yaml` (co-located with this skill) before starting. It defines multiple question groups. | Group | Topics | | --- | --- | | **Identity** | Client name, slug, ticket system, docs platform, repo host | …
Read the whole file at its exact version.
How to install
mdr add ulises-jeremias/agent-toolkit/workflow-client-bootstrap@git:20260831.856ee57mdr add ulises-jeremias/agent-toolkit/workflow-client-bootstrap@sha256:b6d6a3e237c937d7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_bjfzyhy23cobqpv3)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6097 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
Source
ulises-jeremias/agent-toolkit · 18 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bjfzyhy23cobqpv3 GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/workflow-client-bootstrap GET https://markdownregistry.com/api/v1/blob/b6d6a3e237c937d76bcc6f65dc9fa09c802f4098e23833209ab3bad33647fa08
Your agent 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.