dbos-typescript

DBOS TypeScript SDK guidance plus MoltNet-specific authoring, lifecycle, transaction, recovery, bundling, testing, and versioning rules.

Quality

72%

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 ./.agents/skills/dbos-typescript/SKILL.md

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.

The content is concise, actionable, and well-structured for progressive disclosure, with executable code and a clear navigation overlay backed by a substantial, verified reference bundle. Its main weaknesses are mild redundancy across the 'When to Apply', priority, and 'How to Use' sections and validation guidance living in references rather than inlined for destructive/database operations.

Suggestions

Consolidate the 'When to Apply', 'Rule Categories by Priority', and 'How to Use' sections to remove overlapping file listings and intent restatements.

Inline a brief validate→fix→retry checkpoint for durable transaction/recovery changes (or explicitly point to the testing.md crash-gap/process-recovery loop from the overlay) so verification is visible in the overview.

Replace the 'How to Use' filename-only listing with a one-line command or a pointer that mirrors the overlay's six-file read order to keep navigation consistent.

Dimension	Reasoning	Score
Conciseness	The body is lean — imperative rules, executable code, and a compact priority table — with no preamble explaining concepts Claude already knows; only minor redundancy between the 'When to Apply' list, the priority table, and the 'How to Use' file listing keeps it just below the score-5 anchor.	4 / 5
Actionability	Provides concrete executable guidance (npm install pin, DBOS.setConfig/launch, DBOS.runStep with registerWorkflow) plus explicit hard constraints, with bulk detail correctly delegated to reference files; minor gaps such as the 'How to Use' block listing filenames rather than commands keep it at 4.	4 / 5
Workflow Clarity	The numbered MoltNet overlay (read file X before changing Y) gives a clear sequenced navigation workflow backed by a priority table, and verification is delegated to references such as testing.md; validation checkpoints are not inlined in SKILL.md itself, which keeps it just below 5.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview pointing to 41 real, substantive one-level-deep reference files with well-signaled links tied to specific change types; minor organization redundancy (the 'How to Use' file subset overlaps the overlay's six links) prevents a 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is specific, domain-distinct, and clearly scoped to DBOS TypeScript with a MoltNet overlay, but it omits an explicit 'Use when' trigger clause, which caps its completeness. Adding concrete trigger phrasing would raise the completeness and trigger_term_quality dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding DBOS to TypeScript code, authoring workflows/steps/queues, or modifying MoltNet durable-execution behavior.'

Add a couple of natural user-facing synonyms or phrasings (e.g. 'durable workflows', 'durable execution', 'Postgres-backed workflows') to broaden trigger coverage.

Lead with the core action (e.g. 'Build and modify fault-tolerant DBOS TypeScript workflows') so the 'what' reads as an action before listing rule domains.

Dimension	Reasoning	Score
Specificity	Names the DBOS TypeScript SDK domain and enumerates seven concrete rule areas (authoring, lifecycle, transaction, recovery, bundling, testing, versioning), giving several specific actions with only minor coverage gaps relative to the score-5 anchor.	4 / 5
Completeness	Provides a clear 'what' but no explicit 'Use when...' trigger guidance, so per the missing-trigger clause completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes domain-accurate natural terms a contributor would say (lifecycle, transaction, recovery, bundling, testing, versioning) plus the DBOS/MoltNet identifiers, with only a few common variations or synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The DBOS TypeScript SDK scope combined with the MoltNet-specific overlay carves a clear, narrow niche with minimal risk of triggering for an unrelated skill.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getlarge/themoltnet
Path: .agents/skills/dbos-typescript/SKILL.md
Commit: 5daa9ca

Reviewed: ~14 hours 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.