Astro - Advanced Developer

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:34 PM UTC
• Version:
  1.0.0

Overview

This is a documentation-only Astro development skill with ordinary setup, deployment, and troubleshooting guidance, though users should treat its sample secrets as placeholders and avoid overly broad activation.

Safe to install as an Astro reference skill. Review generated commands before running them, especially dependency cleanup or deployment commands, and replace all sample environment values with your own untracked or platform-managed secrets.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The activation scope is overly broad, allowing the skill to trigger on generic framework integrations and broad troubleshooting situations that may not actually require Astro expertise. In an agent system, this can cause inappropriate tool/skill selection, increasing the chance of irrelevant guidance, context hijacking, or interference with more appropriate skills.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: Allowing activation when Astro is not explicitly mentioned, based only on ambiguous concepts like frontmatter fences or island architecture, creates a high risk of false activation. In practice, those cues appear in many unrelated ecosystems, so the skill may take control in contexts where its instructions are irrelevant or conflicting.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The documentation includes realistic-looking secret values such as `SECRET_API_KEY=sk-dev-12345` and `sk-prod-67890` in a `.env` example. Even though these appear illustrative, users may copy them verbatim into repositories, normalize the practice of storing secrets in plaintext examples, or mistake them for acceptable placeholder formats, increasing the chance of credential mishandling and accidental commits.

VirusTotal

66/66 vendors flagged this skill as clean.