Skill Detail

DBOS TypeScript Best Practices

This skill provides a guide for building TypeScript applications with DBOS durable workflows. It appears to make outbound HTTP calls.

GitHub:sickn33/antigravity-awesome-skills dbos-typescript
version 81ace2a0ba19
static analysis only
no human review yet
Needs Review

Current public label

Needs Review

The skill's use of network calls and documentation-heavy structure warrant a review.

This label is currently coming from the automated scorecard.

Automated result

Needs Review

The skill's documentation references external endpoints and makes outbound HTTP calls. The skill is mostly documentation.

5 medium, 4 low Final label: needs review.

Human review

No human review has been recorded yet.

The current public label is still relying on automation. A human has not weighed in yet.

What happened

Driftloom completed a static scan. It inspected the skill files, recorded findings, and generated a scorecard.

Runtime evidence

No sandbox runtime result has been recorded yet.

What did not happen

  • Driftloom did not run this skill in an isolated sandbox yet.
  • This label is not a guarantee that the skill is safe, bug-free, or appropriate for every environment.
  • A good score does not replace human judgment when a skill touches secrets, shell access, or external systems.

Source provenance

Source: Workspace import

Originally ingested from a local workspace copy.

Scorecard

Safety
100
Quality
94
Transparency
7
Operational
92
Maintenance
52

5 medium, 4 low Final label: needs review.

Severity mix: 5 medium, 4 low

What Driftloom checked

  • Read the skill files and metadata to understand what the skill claims to do.
  • Looked for shell commands and risky command patterns, even if none stood out strongly.
  • Looked for external URLs, network calls, and signs the skill reaches outside the machine.
  • Looked for secrets and credential handling clues.
  • Checked whether the skill structure and references looked internally consistent.

Findings

Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: SKILL.md
Evidence: fetch(
Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: references/step-basics.md
Evidence: fetch(
Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: references/step-retries.md
Evidence: fetch(
Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: references/workflow-constraints.md
Evidence: fetch(
Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: references/pattern-classes.md
Evidence: fetch(
Documentation-only skill structure
structure.docs_only · quality
Low

The source looks almost entirely documentation-based, with no obvious code or config files to inspect. That does not make it bad, but it limits how much automation can meaningfully verify.

File: SKILL.md
Explicit external endpoint reference detected
network.url_reference · transparency
Low

The docs reference an external endpoint or network flow in a context that likely matters to how the skill operates.

File: references/client-enqueue.md
Evidence: https://docs.dbos.dev/typescript/reference/client#enqueue
Explicit external endpoint reference detected
network.url_reference · transparency
Low

The docs reference an external endpoint or network flow in a context that likely matters to how the skill operates.

File: references/client-setup.md
Evidence: https://docs.dbos.dev/typescript/reference/client
Explicit external endpoint reference detected
network.url_reference · transparency
Low

The docs reference an external endpoint or network flow in a context that likely matters to how the skill operates.

File: references/pattern-classes.md
Evidence: https://us.api.com
Driftloom is following the boring, correct architecture: Django control plane first, isolated runner later. Miraculously, restraint survives.