Open contribution guide

Add a skill people can trust.

FroggyBot skills are short, readable instructions—not executable plugins. A contributor describes a useful way of working, chooses only the reviewed tools it needs, and opens a pull request.

Before you start

• Search the library and existing pull requests so you do not duplicate a skill.
• Choose one clear user outcome. “Plan a group trip” is stronger than “be helpful.”
• Never include scripts, binaries, secrets, tokens, or instructions fetched from an unreviewed URL.

Submit a skill

1. Fork FroggyBot Skills on GitHub.
2. Copy the closest example in skills/ into a new lowercase, hyphenated folder.
3. Edit its SKILL.md. Include a short name and description, when to use it, a compact process, and its important limits.
4. Add one entry to catalog.json. Use no more than six useful tags and list only reviewed tool IDs the skill truly requires.
5. Run python3 scripts/validate_catalog.py.
6. Open a pull request. The checklist will guide the usefulness, clarity, safety, and least-privilege review.

Request a skill instead

Propose a tool

Tools can access services or take actions, so they require server-side implementation and a stricter review. Start with a tool request that states:

• the user outcome and exact actions;
• what information the tool reads, stores, or changes;
• how authentication works and where credentials live;
• whether each action is read-only, sandboxed, or interactive; and
• the smallest permissions that can support the use case.

Propose a tool

What happens after review

Accepted skills are versioned and published from this repository. FroggyBot refreshes the catalog without an app release, while bots already using a skill remain pinned to the version they selected. Users can make a private editable copy without changing the public original.