agentleFS
Sign inStart free
roedyrustamroedyrustam/doku-gemini-mcp/skills/mock-test/SKILL.md

mock-test

Skill2 starsChanged 9 days agoMITView on GitHub

Send test API request to DOKU Sandbox environment, validating HMAC-SHA256 signature calculations and HTTP response status / Kirim permintaan pengujian ke Sandbox DOKU, memvalidasi kalkulasi signature HMAC-SHA256 dan status respon.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If HTTP 401: Explain signature mismatch causes (trailing newline, timestamp milliseconds, unsorted JSON).

    line 43
  2. Distinctive:

    If HTTP 200/201: Report successful integration test.

    line 44
  3. Very specific:

    MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: …

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Mock Test / Pengujian Integrasi DOKU

English | Bahasa Indonesia

<a name="english"></a>

English

Description

Executes an end-to-end test request against DOKU Sandbox API (https://api-sandbox.doku.com). Validates SHA-256 Digest generation, HMAC-SHA256 header signature calculation, UTC ISO8601 timestamp formatting, and inspects response payloads.

Trigger Conditions

Activate this skill when the user says:

  • "test DOKU integration"
  • "run DOKU sandbox test"
  • "verify DOKU signature calculation"

Step-by-Step Execution Protocol

  1. Prepare Test Payload:
    • Sample Checkout Payment Request to /checkout/v1/payment.
    • Amount: 10000 (IDR Integer).
    • Invoice: INV-TEST-YYYYMMDDHHMMSS.
  2. Compute Signature Components:
    • For POST requests: Digest = Base64(SHA256(Raw JSON Body)).
    • Component = Client-Id:<ID>\nRequest-Id:<UUID>\nRequest-Timestamp:<TIMESTAMP>\nRequest-Target:/checkout/v1/payment\nDigest:<DIGEST>
    • For GET requests: Omit \nDigest:<DIGEST>.
    • Signature = HMACSHA256= + Base64(HMAC-SHA256(Component, SECRET_KEY)).
  3. Send Request to Sandbox:
    • Endpoint: https://api-sandbox.doku.com/checkout/v1/payment
    • Log HTTP Status and DOKU Response Message.
    • If HTTP 401: Explain signature mismatch causes (trailing newline, timestamp milliseconds, unsorted JSON).
    • If HTTP 200/201: Report successful integration test.
  4. Simulate Payment Event:
    • Open DOKU Payment Simulator: https://sandbox.doku.com/gtw-config-v2/simulator
    • Enter Payment Code / Virtual Account / Invoice Number to trigger success webhook notifications to your local listener.

<a name="bahasa-indonesia"></a>

Bahasa Indonesia

Deskripsi

Mengeksekusi pengujian end-to-end ke DOKU Sandbox API (https://api-sandbox.doku.com). Memvalidasi pembuatan Digest SHA-256, kalkulasi signature HMAC-SHA256 header, format timestamp UTC ISO8601, serta menganalisis respon dari server DOKU.

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "test DOKU integration"
  • "jalankan tes sandbox DOKU"
  • "verifikasi kalkulasi signature DOKU"

🚨 SNAP Integration Mandate (CRITICAL)

MANDATORY: The AI Agent MUST automatically apply the SNAP API v1.0 standard (Standard Nasional Open API Pembayaran) for all DOKU integrations, instead of the legacy Jokul API v2, unless the user explicitly requests otherwise. All generated signatures, headers, and endpoints MUST follow the SNAP BI standard.

🧪 DOKU Sandbox Simulator

MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: https://sandbox.doku.com/gtw-config-v2/simulator.

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.

Check your setup, free