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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dbos-golang/SKILL.md

Quality

Content

61%Scale 1-5

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

The skill provides a solid overview of DBOS Go application structure with executable code examples and clear constraints. Its main weaknesses are the absence of referenced bundle files (making progressive disclosure hollow) and the lack of validation/verification steps in the workflow, which is notable for a skill focused on fault-tolerant applications. The priority table adds organizational value but consumes tokens without directly aiding execution.

Suggestions

Provide the referenced rule files (references/lifecycle-config.md, references/workflow-determinism.md, references/queue-concurrency.md) or remove the references to avoid dead-end navigation.

Add explicit validation/verification steps to the workflow, such as how to verify DBOS launched successfully, how to confirm workflow registration, or how to handle and recover from workflow failures.

Consider trimming the 'When to Use' bullet list and the priority table, which add bulk without actionable value — the rule prefixes aren't used elsewhere in the skill body.

Dimension	Reasoning	Score
Conciseness	Generally efficient with minimal unnecessary explanation. The priority table and 'When to Use' section add some bulk that could be trimmed, but the core content respects Claude's intelligence and avoids over-explaining concepts.	4 / 5
Actionability	Provides concrete, executable code examples for configuration, launch, workflow/step structure, and installation. The key constraints are specific and actionable. Minor gap: the referenced rule files (e.g., lifecycle-config.md, workflow-determinism.md) are not provided, so deeper guidance is missing.	4 / 5
Workflow Clarity	The setup sequence (create context → register → launch) is clear, and the workflow/step relationship is demonstrated. However, there are no explicit validation checkpoints, error recovery loops, or verification steps for the workflow lifecycle, which is important for a 'fault-tolerant' system.	3 / 5
Progressive Disclosure	The skill references rule files like 'references/lifecycle-config.md' and 'references/workflow-determinism.md', but no bundle files are provided, meaning these references lead nowhere. The content that is present is reasonably structured, but the promise of deeper content without delivery is a significant gap.	2 / 5
	Total	13 / 20 Passed

Description

82%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.

This is a solid skill description that clearly identifies its niche (DBOS durable workflows in Go) and provides explicit 'Use when' guidance with concrete trigger scenarios. The main weakness is that the capability listing could be more detailed with additional specific actions beyond workflows, steps, and queues.

Suggestions

Expand the capability list with more specific actions, e.g., 'configuring retries, handling errors, setting up durable execution, managing transactional steps' to improve specificity.

Add synonym trigger terms like 'durable execution', 'reliable task processing', or 'DBOS SDK' to capture more user query variations.

Dimension	Reasoning	Score
Specificity	Names the domain (Go applications with DBOS durable workflows) and mentions a few concrete concepts (workflows, steps, queues, concurrency control), but doesn't list specific actions comprehensively — e.g., it doesn't mention error handling, retries, transaction management, or other concrete capabilities.	3 / 5
Completeness	Clearly answers both 'what' (building reliable, fault-tolerant Go applications with DBOS durable workflows) and 'when' (adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control) with explicit trigger phrases.	5 / 5
Trigger Term Quality	Includes good natural keywords like 'DBOS', 'Go', 'durable workflows', 'queues', 'concurrency control', 'steps', and 'fault-tolerant'. Missing some variations users might say like 'durable execution', 'reliable workflows', 'task queues', or 'Go DBOS SDK'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive — the combination of 'DBOS' and 'Go' creates a very specific niche that is unlikely to conflict with other skills. The mention of durable workflows, steps, and queues further narrows the scope.	5 / 5
	Total	17 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/dbos-golang/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.