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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/dbos-golang/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 solid, mostly actionable overview with good code examples and appropriate offloading of detail to reference files, weakened by weak bundle navigation (3 of 28 files listed as bare names) and implicit rather than explicit workflow checkpoints.

Suggestions

Replace the bare-filename list in 'How to Use' with a categorized, linked index of all 28 reference files (e.g., map the priority table categories to their reference files) so each file's purpose is discoverable.

Remove the duplicated opening sentence and trim the 'When to Use' list to avoid repeating the frontmatter description verbatim.

Add explicit validation checkpoints to the launch/setup workflow (e.g., 'Verify workflows are registered before Launch()') rather than relying only on inline error checks.

DimensionReasoningScore

Conciseness

Mostly lean with concrete code and a useful priority table, but the opening line and 'When to Use' list largely duplicate the frontmatter description, creating minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready Go code for installation, context/launch, and step usage plus concrete constraints, but snippets omit full import lists and the 'How to Use' section only names files without describing their contents.

4 / 5

Workflow Clarity

The launch example has an implicit sequence with error-handling checks, but validation checkpoints are not framed explicitly and the end-to-end workflow-building process is not clearly sequenced.

3 / 5

Progressive Disclosure

Overview structure and category table are good and details are correctly split into 28 reference files, but only 3 of those files are surfaced as bare filenames with no descriptions or category mapping, so references are not clearly signaled.

3 / 5

Total

14

/

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 well-crafted third-person description that explicitly states both what the skill does and when to use it, with concrete domain-specific trigger phrases. Minor keyword/coverage gaps prevent a perfect specificity and trigger-term score.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control' — but omits several covered domains (events, messages, testing, client), leaving minor coverage gaps.

4 / 5

Completeness

Clearly answers 'what' ('building reliable, fault-tolerant Go applications with DBOS durable workflows') and 'when' with an explicit 'Use when...' clause enumerating concrete triggers, matching the anchor better than the level-4 example.

5 / 5

Trigger Term Quality

Strong natural keywords ('DBOS', 'Go', 'workflows', 'steps', 'queues', 'concurrency control') a user would say, but misses common variations like 'events', 'messages', 'streams', and file/extension synonyms.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (DBOS durable workflows in Go) with distinct triggers; minimal overlap risk with 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.