ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Jupiter Quote

v1.0.0

Provides curated quotes about the planet Jupiter for educational or reference purposes upon request.

⭐ 0· 200·0 current·0 all-time
byAndrew Boehner@boehner

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for boehner/jupiter-quote.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Jupiter Quote" (boehner/jupiter-quote) from ClawHub.
Skill page: https://clawhub.ai/boehner/jupiter-quote
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install jupiter-quote

ClawHub CLI

Package manager switcher

npx clawhub@latest install jupiter-quote
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
The name and description (providing curated quotes about Jupiter) imply a simple, read-only capability that would not need credentials or installs. However the shipped SKILL.md is a generic authoring template with TODOs and contains no content or runtime instructions implementing that purpose, so the advertised capability is not actually present.
!
Instruction Scope
SKILL.md contains only template/authoring guidance and no concrete runtime directives (no commands, no data sources, no allowed endpoints, no sample requests/responses). Because it gives no explicit scope, an implementing agent or future edit could add broad network access or file reads; the current file does not constrain or describe what the skill will do at runtime.
✓
Install Mechanism
There is no install spec and no code files. That minimizes risk from downloads or installs but also means the skill currently does nothing.
✓
Credentials
The skill requests no environment variables, credentials, or config paths — consistent with a read-only quote provider. There is no disproportionate credential request in the metadata.
✓
Persistence & Privilege
always is false and the skill is user-invocable; model invocation is allowed (default) which is normal. The skill does not request persistent presence or system modifications in its metadata.
What to consider before installing
This package is a placeholder/template rather than a working skill. Do not install it as-is if you expect a functioning 'Jupiter Quote' provider. Before installing, ask the publisher to provide a completed SKILL.md that clearly states: 1) where quotes come from (embedded/local file, included assets, or a named external API), 2) exact runtime steps the skill will perform, 3) any network endpoints it will call and any credentials it will require, and 4) sample inputs and outputs and licensing/attribution for quotes. If the skill will call external services, insist those endpoints and required environment variables be declared in the metadata. If you must use it now, only do so after confirming it does not fetch arbitrary web content or access sensitive files/credentials. Because the current file is empty, the main risk is uncertainty about future behavior — treat it as untrusted until clarified.

Like a lobster shell, security has layers — review code before you run it.

latestvk975j0g4penq6v7pjbhz4kccqx837z04
200downloads
0stars
1versions
Updated 20h ago
v1.0.0
MIT-0
Andrew Boehner@boehner
latest
Download

Jupiter Quote

Overview

[TODO: 1-2 sentences explaining what this skill enables]

Structuring This Skill

[TODO: Choose the structure that best fits this skill's purpose. Common patterns:

1. Workflow-Based (best for sequential processes)

  • Works well when there are clear step-by-step procedures
  • Example: DOCX skill with "Workflow Decision Tree" -> "Reading" -> "Creating" -> "Editing"
  • Structure: ## Overview -> ## Workflow Decision Tree -> ## Step 1 -> ## Step 2...

2. Task-Based (best for tool collections)

  • Works well when the skill offers different operations/capabilities
  • Example: PDF skill with "Quick Start" -> "Merge PDFs" -> "Split PDFs" -> "Extract Text"
  • Structure: ## Overview -> ## Quick Start -> ## Task Category 1 -> ## Task Category 2...

3. Reference/Guidelines (best for standards or specifications)

  • Works well for brand guidelines, coding standards, or requirements
  • Example: Brand styling with "Brand Guidelines" -> "Colors" -> "Typography" -> "Features"
  • Structure: ## Overview -> ## Guidelines -> ## Specifications -> ## Usage...

4. Capabilities-Based (best for integrated systems)

  • Works well when the skill provides multiple interrelated features
  • Example: Product Management with "Core Capabilities" -> numbered capability list
  • Structure: ## Overview -> ## Core Capabilities -> ### 1. Feature -> ### 2. Feature...

Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).

Delete this entire "Structuring This Skill" section when done - it's just guidance.]

[TODO: Replace with the first main section based on chosen structure]

[TODO: Add content here. See examples in existing skills:

  • Code samples for technical skills
  • Decision trees for complex workflows
  • Concrete examples with realistic user requests
  • References to scripts/templates/references as needed]

Resources (optional)

Create only the resource directories this skill actually needs. Delete this section if no resources are required.

scripts/

Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.

Examples from other skills:

  • PDF skill: fill_fillable_fields.py, extract_form_field_info.py - utilities for PDF manipulation
  • DOCX skill: document.py, utilities.py - Python modules for document processing

Appropriate for: Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.

Note: Scripts may be executed without loading into context, but can still be read by Codex for patching or environment adjustments.

references/

Documentation and reference material intended to be loaded into context to inform Codex's process and thinking.

Examples from other skills:

  • Product management: communication.md, context_building.md - detailed workflow guides
  • BigQuery: API reference documentation and query examples
  • Finance: Schema documentation, company policies

Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.

assets/

Files not intended to be loaded into context, but rather used within the output Codex produces.

Examples from other skills:

  • Brand styling: PowerPoint template files (.pptx), logo files
  • Frontend builder: HTML/React boilerplate project directories
  • Typography: Font files (.ttf, .woff2)

Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.

Not every skill requires all three types of resources.

Comments

Loading comments...