Skill Name

Brief one-paragraph summary of what this skill accomplishes. Use plain English and short sentences.

1. Purpose

State the exact goal of the skill. Define any unfamiliar terms immediately.

2. When to Use

List clear triggers and situations where this skill should be selected:

• Trigger condition 1
• Trigger condition 2

3. When Not to Use

List boundaries and alternative skills to avoid misrouting:

• If the task is X, use alternative-skill-1 instead.
• If the task is Y, use alternative-skill-2 instead.

4. Required Inputs

List every input required for execution:

• input_one: Description of what it is and acceptable format.
• input_two: Description of what it is and acceptable format.

5. Missing-Input Behavior

State exact rules when inputs are missing:

1. If input_one is missing, stop immediately and ask: "Please provide input_one."
2. Do not invent missing data.
3. Do not assume default values unless explicitly listed here.

6. Procedure

Follow these numbered, ordered steps:

1. Step 1: Inspect and Prepare
   • Read the provided input.
   • Confirm required fields exist.
2. Step 2: Execute Core Operation
   • Follow specific instructions without skipping steps.
3. Step 3: Self-Check Output
   • Review against the verification checklist before returning.

7. Decision Rules

Use explicit "if X, do Y" branches:

• If condition A is met, execute branch A.
• If condition B is met, execute branch B.
• If an unexpected error occurs, follow Section 10 (Common Failures and Recovery).

8. Output Format

Specify the exact schema or template of the expected output:

### Title / Summary
- Status: [SUCCESS | BLOCKED | FAILED]
- Result: [Concise description]
- Evidence: [Factual data points]

9. Verification Checklist

Before returning your answer, verify every item:

• Required input was validated.
• No facts or data were invented.
• Output conforms to the required format.
• All step actions were executed in sequence.

10. Common Failures and Recovery

11. Stop or Escalation Conditions

Stop work and escalate to the user when:

• Required input cannot be determined from context.
• Retry limit is reached (maximum 2 attempts).
• An operation requires destructive filesystem or network changes without approval.

12. Examples

Example 1: Successful Execution

Input:

[Input payload here]

Expected Observable Actions:

1. Action 1 taken.
2. Action 2 taken.

Output:

[Concrete output conforming to Output Format]

Example 2: Missing Input or Failure Case

Input:

[Incomplete or ambiguous input payload here]

Output:

[Exact question or escalation message returned]

Example 3: Expected Final Output

Output:

[Sample canonical completed response]