Skill Detail

DBOS Python Best Practices

This skill provides guidance for building Python applications with DBOS durable workflows. It appears to be mostly documentation.

GitHub:sickn33/antigravity-awesome-skills dbos-python
version 3c1d6c1c3bb1
static analysis only
no human review yet
Needs Review

Current public label

Needs Review

The skill's use of external network resources and its documentation-heavy structure warrant a review to ensure proper operation and security.

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 source code is mostly documentation.

4 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
22
Operational
92
Maintenance
58

4 medium, 4 low Final label: needs review.

Severity mix: 4 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: references/pattern-classes.md
Evidence: fetch(
Programmatic network client usage detected
network.client_code · transparency
Medium

The source appears to make outbound HTTP calls in code.

File: SKILL.md
Evidence: requests.
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: requests.
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: requests.
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/python/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/python/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/lifecycle-fastapi.md
Evidence: https://docs.dbos.dev/python/tutorials/workflow-tutorial
Driftloom is following the boring, correct architecture: Django control plane first, isolated runner later. Miraculously, restraint survives.