My New Skill

My New Skill provides a customizable framework for specific tasks, enabling streamlined workflows or tool operations in defined scenarios.

Security Scan

This skill is an inert template (placeholder SKILL.md) that requests no binaries, env vars, installs, or code — it does nothing and does not ask for privileges, though it is incomplete and non-functional as-is.

Purpose & Capability

The skill has no meaningful name/description or declared purpose — SKILL.md is a generic TODO/template. That lack of purpose is a usability/quality issue but not a permissions mismatch: the skill does not request any capabilities, credentials, or tools that would be incoherent with a stated purpose.

Instruction Scope

The runtime instructions are purely template guidance and do not direct the agent to run commands, read files, access environment variables, or send data externally. There is no scope creep in the provided instructions because there are no operational instructions.

Install Mechanism

No install specification is present (instruction-only skill), so nothing is downloaded or written to disk. This is the lowest-risk install posture.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is no disproportionate secret or system access requested.

Persistence & Privilege

Flags are default (always: false, user-invocable: true, model invocation allowed). The skill does not request elevated persistence or modify other skill/system configs.

Assessment

This package is a blank skill template and is safe but non-functional. If you plan to use it, edit SKILL.md to provide a clear description of purpose and concrete runtime instructions, and before enabling or sharing a completed version, verify that any added install steps, required environment variables, or external network calls are necessary and appropriate. If you don’t intend to develop it, you can ignore or remove it. If you do install a future version, re-check the manifest for added install specs, env vars, or downloads before enabling the skill.

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.