CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is dbos-golang in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, mostly lean guide with executable code for the critical DBOS lifecycle and workflow/step path, supported by a clear category table and a rich reference bundle. Main gaps are limited inline coverage of non-critical categories and reliance on naming convention rather than explicit per-file links.

Suggestions

Add a short inline code snippet for the most common queue usage so the four highest-priority categories (lifecycle, workflow, step, queue) all have executable examples.

Replace the prefix-convention reliance with an explicit enumerated list (or table) of the reference files per category so all 29 are directly navigable.

Trim the duplicated opening line and 'When to Use' list since they restate the frontmatter description.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable code and tight constraint lists, but the opening line and 'When to Use' list repeat content already in the description, and the full main() program is somewhat long for an overview.

4 / 5

Actionability

Copy-paste-ready executable code is given for the critical path (install, context/registration/launch, RunAsStep) and concrete DO/DON'T constraints, but queues, communication, patterns, testing, and client categories have no inline code — only reference pointers.

4 / 5

Workflow Clarity

The launch lifecycle is shown as a clear ordered sequence (create context → register workflows → launch) with error checks, though there are no explicit validation checkpoints for the broader multi-category workflow.

4 / 5

Progressive Disclosure

Good structure with an overview body, a priority/prefix category table that maps to the 29 reference files, and one-level-deep references; minor gap is that only 3 of 29 reference files are explicitly linked, relying on the prefix convention for the rest.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause and concrete domain-specific triggers that clearly answer both what and when. Minor weakness is the slightly abstract 'reliable, fault-tolerant' framing and the absence of synonyms like 'durable execution'.

DimensionReasoningScore

Specificity

The 'Use when' clause lists several concrete actions — 'adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control' — but the opening 'building reliable, fault-tolerant Go applications' framing is somewhat abstract and coverage stops short of comprehensiveness (events/messages, testing, client).

4 / 5

Completeness

It explicitly answers both what ('Guide for building reliable, fault-tolerant Go applications with DBOS durable workflows') and when ('Use when adding DBOS..., creating workflows and steps, or using queues...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural domain terms a user would say are present ('DBOS', 'Go', 'workflows', 'steps', 'queues', 'concurrency control'), but it misses common synonyms such as 'durable execution' or 'sagas'.

4 / 5

Distinctiveness Conflict Risk

'DBOS durable workflows' in Go is a clear, narrow niche with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.