Files
supabase-postgres-best-prac…/CONTRIBUTING.md
Pedro Rodrigues 760460c221 chore: using mise to manage node versions and tasks (#44)
* add mise for Node.js version management

Replace ad-hoc Node version pinning with mise (mise.toml + mise.lock).
This ensures all contributors and CI use the same Node LTS version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* expand mise with env loading, PATH management, and task runner

- [env] _.file loads .env files for local API keys (replaces dotenv)
- [env] _.path adds node_modules/.bin to PATH for direct tool access
- [tasks] mirrors npm scripts with sources/outputs for file-based caching
- eval tasks for running LLM evaluations via mise run
- update AGENTS.md and CONTRIBUTING.md to use mise run commands

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-17 12:44:44 +00:00

4.3 KiB

CONTRIBUTING.md

Thank you for contributing to Supabase Agent Skills! Here's how to get started:

1. Getting Started | 2. Issues | 3. Pull Requests | 4. Contributing New References | 5. Creating a New Skill

Getting Started

To ensure a positive and inclusive environment, please read our code of conduct before contributing.

Setup

This project uses mise to manage tool versions, environment variables, and project tasks. Install mise, then run from the repository root:

mise install        # Install Node.js (version defined in mise.toml)
mise run install    # Install all npm dependencies

For LLM evals, copy the env example and add your API keys:

cp packages/evals/.env.example packages/evals/.env
# Edit packages/evals/.env with your ANTHROPIC_API_KEY and OPENAI_API_KEY

mise automatically loads .env files defined in mise.toml.

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 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.
  • If you're proposing a significant new skill or major changes, please open a Discussion first to gather feedback before investing time in implementation.

Pre-Flight Checks

Before submitting your PR, make sure you have the right tooling and run these checks:

mise install       # Ensure correct Node.js version
mise run check     # Format and lint (auto-fix)
mise run validate  # Check reference format and structure
mise run build     # Generate AGENTS.md from references

All 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:
mise run validate
mise run build

Creating a New Skill

Skills follow the Agent Skills Open Standard.

1. Create the directory structure

mkdir -p skills/my-skill/references

2. Create SKILL.md

---
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

## 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

mise 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.