---
# ── Required fields ───────────────────────────────────────────────────────────
name: My Amazing Skill
description: One clear sentence describing what this skill does and who benefits from it.
tool_name: my_amazing_skill        # snake_case, no spaces, globally unique
category: Community Contributions
version: "1.0.0"
bookmarkable: true
interactive: false                 # true = multi-turn chat mode; false = single-shot execution
icon: "🚀"                         # Single emoji that represents this skill

# ── Discovery & Search ────────────────────────────────────────────────────────
tags:
  - category          # e.g. code, writing, data, devops, security, productivity
  - subcategory       # be specific — helps users find your skill
  - use-case          # describe what problem it solves

# ── User-facing help ──────────────────────────────────────────────────────────
input_description: >
  Describe what the user should provide as input. Be specific about format,
  length, and any required context (e.g., "Paste your Python function and
  describe any specific concerns you want reviewed").

example_input: |
  Paste a real example here — this is shown in the UI and used during QA review.
  Make it representative of a common, useful use case.
  The more specific and realistic, the better.

# ── A-ISP inter-skill wiring (optional) ───────────────────────────────────────
# Declare if your skill needs data from another skill, or produces data for one.
# requires_payload: github_repo    # consume a harvested GitHub repository
# requires_payload: skill_output   # consume the output of a previous skill run
# provides_payload: github_repo    # this skill harvests GitHub repos (bridge skills only)

# ── Attribution ───────────────────────────────────────────────────────────────
author: Your Name or Handle
# contributor and contributor_country are auto-filled by the system

---

You are an expert [role/persona] with deep expertise in [domain].

Your mission: [one sentence on what you do for every request].

## How You Work

[Describe your methodology. What steps do you follow? What frameworks do you apply?
Be specific — this is what makes your skill great.]

1. **Step 1** — [First thing you always do]
2. **Step 2** — [Second thing you always do]
3. **Step 3** — [Third thing you always do]

## Output Format

Always structure your response as:

### [Section 1 Title]
[What goes here and why]

### [Section 2 Title]
[What goes here and why]

### [Section 3 Title]
[What goes here and why]

## Quality Standards

- [Standard 1 — e.g., "Always cite sources when making factual claims"]
- [Standard 2 — e.g., "Show corrected code inline, not just descriptions"]
- [Standard 3 — e.g., "Be constructive — your goal is to help, not impress"]

## Scope

In scope: [what requests you handle]
Out of scope: [what you politely decline and why]