Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Hookaido Operator
Create, review, and operate Hookaido webhook queue setups, including Hookaidofile management, CLI commands, pull-mode consumption, Admin API triage, and prod...
skill openclawclawhub Free
Create, review, and operate Hookaido webhook queue setups, including Hookaidofile management, CLI commands, pull-mode consumption, Admin API triage, and prod...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- agents/openai.yaml, references/operations.md, scripts/install_hookaido.sh, README.md, RELEASE_NOTES.md, SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.0.1
Provenance
- Publisher
- 7schmiede
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Overview
Implement and troubleshoot Hookaido with a config-first workflow: edit Hookaidofile, validate, run, exercise ingress/pull flows, then diagnose queue health and DLQ behavior. Treat Hookaido v2.0.0's modular architecture as additive in this skill: keep the existing workflow intact by default, and opt into modules such as postgres, gRPC workers, or release verification only when they materially help the task. Use conservative, reversible changes and validate before runtime operations.
Workflow
Confirm target topology: inbound+pull (HTTP or gRPC), push outbound, or internal queue, plus the queue backend (sqlite, memory, or postgres). Choose runtime mode and ensure hookaido exists where tools execute. Host-binary mode: use the install action from metadata.openclaw.install. Host fallback: run bash {baseDir}/scripts/install_hookaido.sh (pinned v2.0.0, SHA256-verified). Public repo/source mode: use the public upstream repo github.com/nuetzliches/hookaido via go install github.com/nuetzliches/hookaido/cmd/hookaido@v2.0.0 when a source-based install is preferred. Docker-sandbox mode: use a sandbox image that already includes hookaido (preferred), or install inside sandbox via agents.defaults.sandbox.docker.setupCommand. Keep host install actions available as fallback and to satisfy metadata.openclaw.requires.bins. Inspect and update Hookaidofile minimally. Run format and validation before starting or reloading: hookaido config fmt --config ./Hookaidofile hookaido config validate --config ./Hookaidofile hookaido config validate --config ./Hookaidofile --strict-secrets when secret refs or Vault-backed config are involved. Start runtime and verify health: hookaido run --config ./Hookaidofile --db ./.data/hookaido.db hookaido run --config ./Hookaidofile --postgres-dsn "$HOOKAIDO_POSTGRES_DSN" when queue postgres is selected. curl http://127.0.0.1:2019/healthz?details=1 Validate end-to-end behavior: ingress request accepted and queued consumer dequeue/ack/nack/extend path works (HTTP pull, batch ack/nack, plus gRPC pull when enabled) For incidents, inspect backlog and DLQ first, then mutate.
Configure Ingress and Pull Consumption
Define a route with explicit auth and pull path (HTTP pull, optional gRPC pull worker listener). Keep secrets in env/file refs, never inline. Verify route and global pull auth are consistent. Test with a real webhook payload and a dequeue/ack cycle, using batch ack/nack when worker throughput matters. Prefer this baseline: ingress { listen :8080 } pull_api { listen :9443 grpc_listen :9943 # optional gRPC pull-worker listener auth token env:HOOKAIDO_PULL_TOKEN } /webhooks/github { auth hmac env:HOOKAIDO_INGRESS_SECRET pull { path /pull/github } }
Configure Push Delivery
Use push delivery only when inbound connectivity to the service is acceptable. Set timeout and retry policy explicitly. Validate downstream idempotency since delivery is at-least-once. /webhooks/stripe { auth hmac env:STRIPE_SIGNING_SECRET deliver "https://billing.internal/stripe" { retry exponential max 8 base 2s cap 2m jitter 0.2 timeout 10s } }
Configure Queue Backends
Default to sqlite unless the task explicitly needs ephemeral dev mode or shared Postgres storage. Treat memory and postgres as additive v2 modules, not replacements for existing sqlite workflows. When using postgres, document the DSN source and validate health plus backlog endpoints after startup. Prefer these patterns: queue sqlite queue memory queue postgres
Operate Queue and DLQ
Start with health details and backlog endpoints. Inspect DLQ before requeue or delete. If requeueing many items, explain expected impact and rollback path. Require clear operator reason strings for mutating admin calls. Use: GET /healthz?details=1 GET /backlog/trends GET /dlq POST /dlq/requeue POST /dlq/delete
Use MCP Mode for AI Operations
Default to --role read for diagnostics. Enable mutations only with explicit operator intent: --enable-mutations --role operate --principal <identity> Enable runtime control only for admin workflows: --enable-runtime-control --role admin --pid-file <path> Include reason for mutation calls and keep it specific.
Verify Public Releases
Prefer official release assets from the public Hookaido repo. When supply-chain assurance matters, validate checksums, signature material, and provenance before rollout. Keep verification optional by default so existing skill flows do not become heavier unless the task requires it. Use: hookaido verify-release --checksums ./hookaido_v2.0.0_checksums.txt --require-provenance
Validation Checklist
hookaido config validate returns success before runtime start/reload. hookaido config validate --strict-secrets is used when secret refs, Vault, or public-release rollout validation matters. Health endpoint is reachable and reports expected queue/backend state. Pull consumer can dequeue, ack, nack, and extend with valid token (HTTP and optional gRPC transport), including batch ack/nack when enabled. For push mode, retry/timeout behavior is explicitly configured. For queue postgres, runtime is started with --postgres-dsn or HOOKAIDO_POSTGRES_DSN. Any DLQ mutation is scoped, justified, and logged.
Safety Rules
Do not disable auth to "make tests pass." Do not suggest direct mutations before read-only diagnostics. Treat queue operations as at-least-once; require idempotent handlers. Keep secrets in env: or file: refs.
References
Read references/operations.md for command snippets and API payload templates.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Docs1 Scripts1 Config
- SKILL.md
- README.md
- references/operations.md
- RELEASE_NOTES.md
- scripts/install_hookaido.sh
- agents/openai.yaml