← all publishers

ddnetters

@ddnetters source repo

Report this profile Claim this profile

• 8 skills
• 0 followers
• 1 week ago last updated

1. ▌
   Langfuse Observability · ddnetters

   LLM observability with Langfuse — query traces, generations, costs, metrics, and debug LLM pipelines via the REST API
   1 install
2. ▌
   Caddy Reverse Proxy · ddnetters

   Caddy reverse proxy configuration, Caddyfile syntax, automatic HTTPS, Docker integration, and common patterns
   1 install
3. ▌
   Invoking Codex Exec · ddnetters bundle

   Use when delegating a single coding task to `codex exec` ("hand off to codex", "run codex on this", "dispatch codex on this ticket", any one-shot invocation). Covers flags, sandbox traps, monitoring, and recovery. Not for multi-issue parallel batches — use codex-issue-waves for those.
   1 install
4. ▌
   Slite Knowledge Base · ddnetters

   Slite knowledge base API — ask questions, search notes, retrieve content, manage users and groups, and audit knowledge health via the REST API
   1 install
5. ▌
   Gogcli · ddnetters bundle

   Use `gog` CLI for Gmail and Google Calendar operations. Trigger when user asks to send/search/read email, manage Gmail labels/drafts/filters, create/update/list calendar events, check availability, or interact with Google Workspace email and scheduling. Also covers auth setup, account management, and output formatting.
   1 install
6. ▌
   Codex Task Waves · ddnetters

   Use when the user says "have codex fix this" / "have codex implement this" / "let codex handle this" / "give this to codex" / "delegate this to codex" for a single task with context already in scope (a Jira ticket, GitHub issue, file diff, bug, or described change). Plans the work, splits it into reviewable waves, dispatches codex per wave with review and correction between waves before opening a PR. Not for multi-issue parallel batches (use codex-issue-waves) or one-shot codex runs without planning (use invoking-codex-exec).
   0 installs
7. ▌
   Codex Issue Waves · ddnetters bundle

   Run a batch of GitHub issues through codex exec in isolated git worktrees as parallel autonomous PRs, then manage the review and correction waves until merge. Use when the user gives a list of issue numbers (≥ 2) and asks to "spawn codex" / "dispatch codex" / "have codex work on" / "manage the PRs" / "process feedback" / "get them merged" for those issues, or when the user asks for multi-issue parallel delegation to codex. Not for single-issue wave-driven delegation (use codex-task-waves), single-issue one-shot dispatch (use invoking-codex-exec), or implementation without delegation (use /pr or direct implementation).
   1 install
8. ▌
   Ntfy Notifications · ddnetters

   Self-hosted push notifications with ntfy — publishing, authentication, priorities, and integration patterns for scripts and monitoring
   1 install