\r \r

Jupiter Quote\r

\r

Overview\r

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

Structuring This Skill\r

\r [TODO: Choose the structure that best fits this skill's purpose. Common patterns:\r \r 1. Workflow-Based (best for sequential processes)\r

• Works well when there are clear step-by-step procedures\r
• Example: DOCX skill with "Workflow Decision Tree" -> "Reading" -> "Creating" -> "Editing"\r
• Structure: ## Overview -> ## Workflow Decision Tree -> ## Step 1 -> ## Step 2...\r \r 2. Task-Based (best for tool collections)\r
• Works well when the skill offers different operations/capabilities\r
• Example: PDF skill with "Quick Start" -> "Merge PDFs" -> "Split PDFs" -> "Extract Text"\r
• Structure: ## Overview -> ## Quick Start -> ## Task Category 1 -> ## Task Category 2...\r \r 3. Reference/Guidelines (best for standards or specifications)\r
• Works well for brand guidelines, coding standards, or requirements\r
• Example: Brand styling with "Brand Guidelines" -> "Colors" -> "Typography" -> "Features"\r
• Structure: ## Overview -> ## Guidelines -> ## Specifications -> ## Usage...\r \r 4. Capabilities-Based (best for integrated systems)\r
• Works well when the skill provides multiple interrelated features\r
• Example: Product Management with "Core Capabilities" -> numbered capability list\r
• Structure: ## Overview -> ## Core Capabilities -> ### 1. Feature -> ### 2. Feature...\r \r Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).\r \r Delete this entire "Structuring This Skill" section when done - it's just guidance.]\r \r

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

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

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

Resources (optional)\r

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

scripts/\r

Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.\r \r Examples from other skills:\r

• PDF skill: fill_fillable_fields.py, extract_form_field_info.py - utilities for PDF manipulation\r
• DOCX skill: document.py, utilities.py - Python modules for document processing\r \r Appropriate for: Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.\r \r Note: Scripts may be executed without loading into context, but can still be read by Codex for patching or environment adjustments.\r \r

references/\r

Documentation and reference material intended to be loaded into context to inform Codex's process and thinking.\r \r Examples from other skills:\r

• Product management: communication.md, context_building.md - detailed workflow guides\r
• BigQuery: API reference documentation and query examples\r
• Finance: Schema documentation, company policies\r \r Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.\r \r

assets/\r

Files not intended to be loaded into context, but rather used within the output Codex produces.\r \r Examples from other skills:\r

• Brand styling: PowerPoint template files (.pptx), logo files\r
• Frontend builder: HTML/React boilerplate project directories\r
• Typography: Font files (.ttf, .woff2)\r \r Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.\r \r ---\r \r Not every skill requires all three types of resources.\r