zaafpulse-workflows SKILL.md skillA
zaafpulse-workflows from rifqifitriady/zaafpulse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rifqifitriady/zaafpulse/zaafpulse-workflows@git:20261019.2310dccPins git:20261019.2310dcc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rifqifitriady/zaafpulse
- Path
skills/zaafpulse-workflows/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.2310dcc, committed Oct 19, 2026
- First version recorded
- Oct 18, 2026
- Size
- 2,974 bytes
- Repository stars
- 3
- License
- MIT
Run ZAAFPulse's ready-made multi-agent workflows (incident triage to mitigation, postmortem, IT helpdesk, ticket triage, refunds, phishing triage, cited research, RFP and security questionnaires, contract redlines, code review, lead outreach, meeting actions, change risk, vulnerability plans, access requests, onboarding, month-end commentary, procurement, feedback to PRD, release notes, project status, PDP and OJK compliance, knowledge-base gaps, agent quality review). Steps that send or…
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
# ZAAFPulse: workflows
Requires `ZAAFPULSE_URL` and `ZAAFPULSE_KEY`, with a key that has the `agents` scope. For setup, read the `zaafpulse` skill.
## Find a workflow
```bash
curl -s $ZAAFPULSE_URL/v1/workflows -H "Authorization: Bearer $ZAAFPULSE_KEY" \
| jq -r '.data[] | "\(.id)\t\(.tier // "")\t\(.name)"'
```
Each workflow has:
- `steps` (agent and prompt, run in order)
- `tier`, the risk of the step after an approval gate:
- R0: read only
- R1: internal draft
- R2: sends or changes something
- R3: money, access or decisions about a person
- `sampleInput`, which shows what to send
- `kpi`
## Run
```bash
curl -s $ZAAFPULSE_URL/v1/workflows/incident-triage-rca/run -H "Authorization: Bearer $ZAAFPULSE_KEY" -H "Content-Type: application/json" \
-d '{"input":"SEV2: checkout p95 4.8s since 10:02; payment-api errors 6%; deploy v2.14 at 09:55"}'
```
Two outcomes are possible:
- `state: "completed"`: read `answer` (the last step's output) and `steps`.
- `state: "input-required"`: the run paused at an **approval gate**. `pending.question` shows the step and the proposal (it starts with APPROVAL_PACKET).
## Approval gates
…Read the whole file at its exact version.
How to install
mdr add rifqifitriady/zaafpulse/zaafpulse-workflows@sha256:f6f694fa64577a92The line at the top of this page pins the label git:20261019.2310dcc, 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_74fgjgz6mqpcgyja)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 18, 2026 and Oct 19, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.2310dcc latest | 2026-10-19 | 2310dcc | 2,974 B | A | view · diff |
| git:20261018.d626678 | 2026-10-18 | d626678 | 2,475 B | A | view |
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 (2974 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
rifqifitriady/zaafpulse · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_74fgjgz6mqpcgyja GET https://markdownregistry.com/api/v1/resolve?ref=rifqifitriady/zaafpulse/zaafpulse-workflows GET https://markdownregistry.com/api/v1/blob/f6f694fa64577a9248592982f9c799f2884abad812a31c4ae4b0d2dd5c2ae42d
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.