agentsclimarketplace

Rutebayar agent contributor

Skill pendig/rutebayar-agent-contributor

AI Agent skill for operating and contributing to Rute Bayar

Install
npx -y skills add pendig/rutebayar-agent-contributor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Operate and extend Rute Bayar, the Go CLI and webhook daemon for Indonesian payment gateways. Use when setting up sandbox or production Rute Bayar flows, helping AI Agents create invoices and verify payments through the rutebayar CLI, testing webhooks/forwarding/reconciliation, preparing releases, or contributing a new provider adapter such as DOKU, Flip Business, Duitku, Xendit, or Midtrans.

SKILL.md

3.1 KB, as published. Nobody here has run it

Rute Bayar AI Agent & Contributor

Use this skill for AI Agent and contributor work where correctness depends on Rute Bayar's CLI, daemon, provider model, sandbox/prod differences, and contribution conventions.

Start Here

  1. Confirm the command name is rutebayar, not rute-bayar.
  2. Read the local repo first when available: README.md, docs/provider-integration.md, docs/operations-runbook.md, and provider-specific docs under docs/providers/.
  3. Keep credentials out of commits, PR bodies, issue comments, screenshots, and logs shown to public channels.
  4. Prefer lean-ctx -c "<command>" for shell exploration when available.
  5. For current provider behavior, verify against official provider docs before changing adapter logic.

Choose The Workflow

  • Sandbox/prod operation, AI Agent billing, webhook, forwarding, health checks: read references/operator-workflows.md.
  • Adding or modifying providers: read references/contributor-workflows.md.
  • Provider capability caveats and current integration matrix: read references/provider-matrix.md.
  • CI, E2E, PR, release, and Homebrew distribution: read references/release-ci.md.

Operating Rules

  • Store raw outbound request/response JSON and raw inbound webhook body/headers for debuggability.
  • Keep webhook forwarding pass-through: preserve provider body and headers as much as possible.
  • Verify webhook authenticity when credentials support it; if verification is skipped, state why.
  • Use reconciliation as the source-of-truth fallback when webhooks are late, missing, duplicated, or non-final.
  • Treat SQLite as the current persistence target; recommend backups before production upgrades.
  • Default to small, reviewable PRs with docs and tests updated together.

Contribution Rules

  • Keep provider-specific logic in adapter packages and provider docs; do not leak provider quirks into core domain or CLI contracts unless the public interface needs it.
  • Add provider capabilities explicitly and make unsupported operations fail clearly.
  • Normalize provider statuses into internal statuses and test edge cases.
  • Add or update unit tests for adapter signing, payload mapping, webhook verification, webhook parsing, status mapping, forwarding, and service-level behavior.
  • Update docs, site changelog/data, and release notes when user-facing behavior changes.

Minimum Verification

Before saying a change is ready:

go test ./...
./scripts/smoke-local.sh

For site changes:

npm --prefix site run build

For provider sandbox validation, use scripts/e2e-sandbox.sh only when sandbox credentials are present in environment variables or GitHub Secrets.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.