Terminal.skills
Terminal.skills
Browse Use Cases
Back to home

Publish a Use Case

Use cases define the real problems people face. Skills are built to serve them. Start here — share a problem worth solving.

Have a skill to publish? Go to Publish a Skill

How it works

Step 1

Fork & Clone

Fork the skills repository and create a new branch.

$
Step 2

Create Use Case

Add your use-case file using the template below.

$
Step 3

Open Pull Request

Push your branch and open a PR. Select the use-case template.

$

Use Case Template

Copy this template and fill in your use case details.

your-use-case-slug.md
---
title: "Action-Oriented Title with AI"
slug: your-use-case-slug
description: "One sentence explaining the use case."
skills: [skill-name, another-skill]  # optional — omit if no matching skills exist yet
category: documents
tags: [tag1, tag2, tag3]
---

# Action-Oriented Title with AI

## The Problem

Describe the specific pain point. Be concrete — mention file types, team sizes,
time wasted, or error rates. The reader should think "yes, that's exactly my problem."

## The Solution

Explain the approach in 2-3 sentences. Name the skills involved and include
install commands. If no matching skills exist yet, describe the workflow.

```bash
npx terminal-skills install skill-name
```

## Step-by-Step Walkthrough

### 1. Point the agent at your data

Tell the reader exactly what to say to the AI agent:

```
The exact prompt the user would type.
```

### 2. The agent processes the input

Explain what the agent does, with realistic output:

```
Expected output with real data, not placeholders.
```

### 3. You get the result

Show the concrete output the user receives.

## Real-World Example

Tell a story: a specific persona, a specific situation, and a specific outcome.

1. The persona encounters the problem
2. They use the skill with a specific prompt
3. The agent performs the steps
4. They get a concrete, measurable result

## Related Skills

- [complementary-skill](../skills/complementary-skill/) -- What it adds to this workflow
- [another-skill](../skills/another-skill/) -- Another useful combination

Frontmatter Reference

YAML fields for every use case.

FieldRules
titleAction-oriented, starts with a verb, max 100 chars
slugLowercase kebab-case, matches filename, max 64 chars
descriptionOne sentence, max 200 chars
skillsOptional — array of skill names involved; omit if none exist yet
categoryOne of the 10 categories below
tagsArray of 3-5 relevant tags

Categories

Use one of these values for category

documentsPDF, Word, document processing
developmentCode review, testing, refactoring
data-aiData analysis, ML, visualization
devopsDocker, CI/CD, infrastructure
businessSpreadsheets, reports, email
designUI/UX, design systems
automationWeb scraping, workflow automation
researchSearch, summarization, analysis
productivityGit, documentation, tooling
contentWriting, markdown, documentation

Submission Checklist

0/13

Verify your use case meets all requirements before submitting.

Ready to submit?

Push your branch and open a pull request. Select the use-case template when creating the PR.