Skillsby SefarAI

Submissions

Bring the source. We will help make the case.

Automated submissions are not open in this release. You can still propose an individual skill or a complete outcome-led stack.

What to prepare

A clean submission makes every public claim traceable to the repository.

  1. 01Public repository URL and exact SKILL.md path
  2. 02Skill name, publisher, and one-sentence job
  3. 03Verified install command
  4. 04License name or a clear note that it is unspecified
  5. 05Three practical use cases and expected outcomes
  6. 06Runtime, tools, or file requirements

Proposing a stack?

Include the intended outcome, target agent and toolchain, ordered phases, role of every skill, prerequisites, expected evidence, and known limits.

Ready to introduce it?

Use the main SefarAI contact route and include “Skills submission” with the repository link. A dedicated workflow will replace this in a later release.

Visit SefarAI

Before submitting, read the listing methodology.