Skill Detail

Content Strategy

This skill helps with content strategy. Driftloom found broken references and mentions of secrets in the documentation.

GitHub:sickn33/antigravity-awesome-skills content-strategy
version b3d17417ed4c
static analysis only
no human review yet
Use Caution

Current public label

Use Caution

Because the documentation has broken references and mentions secrets, it's labeled 'use_caution'. This means you should carefully review the skill's setup and usage.

This label is currently coming from the automated scorecard.

Automated result

Use Caution

The skill's documentation has broken references and mentions secrets. This suggests the skill may handle sensitive information.

4 low Final label: use caution.

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.

Driftloom currently recommends runtime testing for this version (priority 40).

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
94
Quality
82
Transparency
100
Operational
92
Maintenance
82

4 low Final label: use caution.

Severity mix: 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 and network behavior.
  • Looked for secret, token, password, and credential references.
  • Checked for broken internal references and missing files.

Findings

Broken relative reference detected
reference.missing_relative_path · quality
Low

The source references `../../../tools/integrations/sanity.md`, but that path does not exist.

File: references/headless-cms.md
Evidence: - [Sanity](../../../tools/integrations/sanity.md) — GROQ queries, mutations, CLI
Broken relative reference detected
reference.missing_relative_path · quality
Low

The source references `../../../tools/integrations/contentful.md`, but that path does not exist.

File: references/headless-cms.md
Evidence: - [Contentful](../../../tools/integrations/contentful.md) — Delivery/Management APIs, publishing
Broken relative reference detected
reference.missing_relative_path · quality
Low

The source references `../../../tools/integrations/strapi.md`, but that path does not exist.

File: references/headless-cms.md
Evidence: - [Strapi](../../../tools/integrations/strapi.md) — REST CRUD, filters, document API
Secret or credential reference detected
secret.reference · safety
Low

The docs mention credentials or secrets. That may be normal, but it still tells you the skill expects sensitive material somewhere in the workflow.

File: references/headless-cms.md
Evidence: token
Driftloom is following the boring, correct architecture: Django control plane first, isolated runner later. Miraculously, restraint survives.