ISSUE TEMPLATE

---
name: Propose a skill (community tier)
about: Suggest a community-contributed skill for an ASB-Skill collection. Keep it short — a maintainer (or the propose-skill command) fills in the rest.
title: "Propose skill: <name>"
labels: ["propose", "community-skill", "needs-triage"]
---

<!--
Keep this short. Tell us WHAT the skill does, WHY it's worth adding, and give a
LINK to the skill (or paste its SKILL.md). The `propose-skill` command does the
matching, grounding, and normalization, and stages a reviewable PR. A maintainer
makes the final merge decision — you cannot self-merge.
See governance/COMMUNITY_SKILLS.md for how community skills are curated.
-->

**What does the skill do?** <!-- one line, e.g. "Use when aligning RT across batches with method X" -->

**Why it matters (one or two sentences):**
<!-- What procedure does it capture, and why is it worth grounding agent retrieval on? -->

**Link to the skill:** <!-- a gist, repo path, or the SKILL.md pasted below — whatever you have -->

**Tool(s) it grounds on:** <!-- the software/tool the skill drives, if any -->

**Target collection:** <!-- the domain repository's collection slug, or a slug registered in collections.yaml -->

---
<!-- Optional, all skippable — a maintainer/the command resolves these: -->
- **Related existing skills?** <!-- slugs it overlaps or composes, if you know them -->
- **You:** <!-- @handle, ORCID -->
- **Conflict of interest?** <!-- disclosure only, never disqualifying -->

## Licensing

- [ ] I license my contributed skill prose (description + body) under **CC-BY-4.0**.

<!--
This CC-BY-4.0 grant covers the text you wrote. It is separate from the skill's
`license_tier`, which describes the tool the skill grounds on (open / noncommercial
/ restricted) — see governance/LICENSE_TIERS.md.
-->