agentleFS
Sign inStart free
roedyrustamroedyrustam/doku-gemini-mcp/skills/setup-credentials/SKILL.md

setup-credentials

Skill2 starsChanged 8 days agoMITView on GitHub

Safely collect, configure, and store DOKU CLIENT_ID, SECRET_KEY, and environment mode in environment files / Konfigurasi dan simpan kredensial DOKU CLIENT_ID, SECRET_KEY, dan mode lingkungan secara aman.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update .env.example with sanitized placeholders.

    line 41
  2. Very specific:

    Ensure .env is listed in .gitignore to prevent secret key leaks into git repositories.

    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 66

≈ “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

Setup Credentials / Pengaturan Kredensial DOKU

English | Bahasa Indonesia

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

English

Description

Guides the developer in configuring DOKU Payment Gateway credentials for Sandbox or Production. Ensures DOKU_CLIENT_ID and DOKU_SECRET_KEY are safely injected via environment variables and never committed to source control.

Trigger Conditions

Activate this skill when the user says:

  • "set up DOKU credentials"
  • "configure DOKU keys"
  • "add DOKU API keys"

Step-by-Step Execution Protocol

  1. Prompt for Required Credentials:
    • DOKU_CLIENT_ID (Merchant Client ID from DOKU Back Office Sandbox: https://sandbox.doku.com/bo/login or Production: https://dashboard.doku.com).
    • DOKU_SECRET_KEY (Merchant Secret Key).
    • DOKU_IS_PRODUCTION (false for Sandbox https://api-sandbox.doku.com, true for Production https://api.doku.com).
  2. Update Environment Files (.env & .env.example):
    • Append to .env:
      DOKU_CLIENT_ID=YOUR_CLIENT_ID
DOKU_SECRET_KEY=YOUR_SECRET_KEY
DOKU_IS_PRODUCTION=false
    • Update .env.example with sanitized placeholders.
  3. Verify .gitignore:
    • Ensure .env is listed in .gitignore to prevent secret key leaks into git repositories.

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

Bahasa Indonesia

Deskripsi

Membimbing pengembang dalam mengonfigurasi kredensial DOKU Payment Gateway untuk Sandbox atau Production. Memastikan DOKU_CLIENT_ID dan DOKU_SECRET_KEY diinjeksikan secara aman via variabel lingkungan dan tidak pernah ter-commit ke repositori git.

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "set up DOKU credentials"
  • "konfigurasi kunci DOKU"
  • "tambahkan API key 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