Files
supabase-postgres-best-prac…/CONTRIBUTING.md
2026-01-26 15:22:35 +00:00

136 lines
3.6 KiB
Markdown

# CONTRIBUTING.md
Thank you for contributing to Supabase Agent Skills! Here's how to get started:
[1. Getting Started](#getting-started) | [2. Issues](#issues) |
[3. Pull Requests](#pull-requests) | [4. Contributing New References](#contributing-new-references) |
[5. Creating a New Skill](#creating-a-new-skill)
## Getting Started
To ensure a positive and inclusive environment, please read our
[code of conduct](https://github.com/supabase/.github/blob/main/CODE_OF_CONDUCT.md)
before contributing.
## Issues
If you find a typo, have a suggestion for a new skill/reference, or want to improve
existing skills/references, please create an Issue.
- Please search
[existing Issues](https://github.com/supabase/agent-skills/issues) before
creating a new one.
- Please include a clear description of the problem or suggestion.
- Tag your issue appropriately (e.g., `bug`, `question`, `enhancement`,
`new-reference`, `new-skill`, `documentation`).
## Pull Requests
We actively welcome your Pull Requests! Here's what to keep in mind:
- If you're fixing an Issue, make sure someone else hasn't already created a PR
for it. Link your PR to the related Issue(s).
- We will always try to accept the first viable PR that resolves the Issue.
- If you're new, we encourage you to take a look at issues tagged with
[good first issue](https://github.com/supabase/agent-skills/labels/good%20first%20issue).
- If you're proposing a significant new skill or major changes, please open a
[Discussion](https://github.com/orgs/supabase/discussions/new/choose) first to
gather feedback before investing time in implementation.
### Pre-Flight Checks
Before submitting your PR, please run these checks:
```bash
npm run validate # Check reference format and structure
npm run build # Generate AGENTS.md from references
```
Both commands must complete successfully.
## Contributing New References
To add a reference to an existing skill:
1. Navigate to `skills/{skill-name}/references/`
2. Copy `_template.md` to `{prefix}-{your-reference-name}.md`
3. Fill in the frontmatter (title, impact, tags)
4. Write explanation and examples (Incorrect/Correct)
5. Run validation and build:
```bash
npm run validate
npm run build
```
## Creating a New Skill
Skills follow the [Agent Skills Open Standard](https://agentskills.io/).
### 1. Create the directory structure
```bash
mkdir -p skills/my-skill/references
```
### 2. Create SKILL.md
```yaml
---
name: my-skill
description: Brief description of what this skill does and when to use it.
license: MIT
metadata:
author: your-org
version: "1.0.0"
organization: Your Org
date: January 2026
abstract: Detailed description of this skill for the compiled AGENTS.md.
---
# My Skill
Instructions for agents using this skill.
## References
- https://example.com/docs
```
### 3. Create references/_sections.md
```markdown
## 1. First Category (first)
**Impact:** HIGH
**Description:** What this category covers.
## 2. Second Category (second)
**Impact:** MEDIUM
**Description:** What this category covers.
```
### 4. Create reference files
Name files as `{prefix}-{reference-name}.md` where prefix matches a section.
Example: `first-example-reference.md` for section "First Category"
### 5. Build
```bash
npm run build
```
The build system auto-discovers skills by looking for `SKILL.md` files.
## Questions or Feedback?
- Open an Issue for bugs or suggestions
- Start a Discussion for broader topics or proposals
- Check existing Issues and Discussions before creating new ones
## License
By contributing to this repository, you agree that your contributions will be
licensed under the MIT License.