Agent skill

dbos-golang

Guide for building reliable, fault-tolerant Go applications with DBOS durable workflows. Use when adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill dbos-golang --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 33
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/dbos-golang/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# DBOS Go Best Practices Guide for building reliable, fault-tolerant Go applications with DBOS durable workflows. ## When to Use Reference these guidelines when: - Adding DBOS to existing Go code - Creating workflows and steps - Using queues for concurrency control - Implementing workflow communication (events, messages, streams) - Configuring and launching DBOS applications - Using the DBOS Client from external applications - Testing DBOS applications ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Lifecycle | CRITICAL | `lifecycle-` | | 2 | Workflow | CRITICAL | `workflow-` | | 3 | Step | HIGH | `step-` | | 4 | Queue | HIGH | `queue-` | | 5 | Communication | MEDIUM | `comm-` | | 6 | Pattern | MEDIUM | `pattern-` | | 7 | Testing | LOW-MEDIUM | `test-` | | 8 | Client | MEDIUM | `client-` | | 9 | Advanced | LOW | `advanced-` | ## Critical Rules ### Installation Install the DBOS Go module: ```bash go get github.com/dbos-inc/dbos-transact-golang/dbos@latest ``` ### DBOS Configuration and Launch A DBOS application MUST create a context, register workflows, and launch before running any workflows: ```go package mai

What's inside
Steps it walks through
  1. When to Use
  2. Rule Categories by Priority
  3. Critical Rules
  4. Installation
  5. DBOS Configuration and Launch
  6. Workflow and Step Structure
  7. Key Constraints
  8. How to Use
  9. References
  10. Limitations
Ships with 24 files
  • AGENTS.md
  • CLAUDE.md
  • references/_sections.md
  • references/advanced-patching.md
  • references/advanced-versioning.md
  • references/client-enqueue.md
  • references/client-setup.md
  • references/comm-events.md
  • references/comm-messages.md
  • references/comm-streaming.md
  • references/lifecycle-config.md
  • references/pattern-debouncing.md
  • references/pattern-idempotency.md
  • references/pattern-scheduled.md
  • references/pattern-sleep.md
  • references/queue-basics.md
  • references/queue-concurrency.md
  • references/queue-deduplication.md
  • references/queue-listening.md
  • references/queue-partitioning.md
  • references/queue-priority.md
  • references/queue-rate-limiting.md
  • references/step-basics.md
  • references/step-concurrency.md
first 24 of 33
Commands it runs
go get github.com/dbos-inc/dbos-transact-golang/dbos@latest
More from agentic-awesome-skills
All skills →
About this skill
What does the dbos-golang skill do?

Guide for building reliable, fault-tolerant Go applications with DBOS durable workflows. Use when adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill dbos-golang --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going