domains / agent-tooling / skill-template / template

template

Skill card

combined

The copies overlap in purpose (providing a template for creating a new skill) but differ significantly in structure and content. The first, third, and fourth copies are identical minimal stubs. The second copy (anbeime/skill) is a detailed, structured template with specific sections for task goals, input/output schemas, core logic steps, and examples. Crowning the minimal stubs would hide the more comprehensive structural alternative provided by the second copy.

Repositories

Other copies

Combined skill

---
name: skill-template
description: A comprehensive template for creating new skills. Replace all placeholders with actual content.
---

# <Skill Title>

## Task Goal

- Purpose: <One-sentence description of the skill's purpose>
- Capabilities: <Capability 1>, <Capability 2>, <Capability 3>
- Trigger Conditions: <Scenarios where this skill should be used>

## Usage

### Input

<Describe what input the user needs to provide>

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| input_text | string | Yes | Input text |
| mode | string | No | Processing mode (default: auto) |

### Output

<Describe the output format of the skill>

```json
{
  "result": "Processing result",
  "metadata": {
    "processing_time": "0.5s",
    "status": "success"
  }
}
```

## Core Logic

### Step 1: <Step Name>

<Detailed explanation of this step's logic>

### Step 2: <Step Name>

<Detailed explanation of this step's logic>

### Step 3: <Step Name>

<Detailed explanation of this step's logic>

## Notes

- <Note 1>
- <Note 2>
- <Note 3>

## Examples

### Example 1: <Scenario Description>

**Input:**
```
<Example Input>
```

**Output:**
```
<Example Output>
```

### Example 2: <Scenario Description>

**Input:**
```
<Example Input>
```

**Output:**
```
<Example Output>
```