---
name: submit-a-skill
description: >-
  Fills the Skylark skill submission form from a SKILL.md the user already has,
  and stops before submitting so they can check it. Use it when the user wants
  to contribute a skill they have written.
runtime: browser
permissions:
  - page:read
  - page:act
  - navigate
scope:
  - https://skills.skylarkbrowser.com/submit
triggers:
  - kind: url_pattern
    pattern: https://skills.skylarkbrowser.com/submit
  - kind: intent
    description: submit a skill to the directory
  - kind: intent
    description: contribute a web skill
version: 1.0.0
---

# Submit a skill

Submitting is public and creates work for a curator, so the last click belongs
to the user. Fill the form in, then hand it back.

## Before you start

1. Call `read_page` and confirm you are on
   `https://skills.skylarkbrowser.com/submit`.

2. If the page asks you to sign in, stop. Tell the user they need to sign in
   with GitHub first, and do not attempt it yourself. Authentication is theirs.

3. Get two things from the user, and do not guess at either of them:

   - the hostname the skill acts on,
   - whether they have a URL to a `SKILL.md` or the file contents.

   If they have neither, say so and stop, because there is nothing to submit.

## Filling the form

4. Fill the site field with the hostname on its own, leaving out the scheme and
   the path. Use `billing.acme.example` rather than
   `https://billing.acme.example/account`.

5. Choose the matching source tab, then fill it:

   - **Link to a file** for a URL. It must be `https`.
   - **Paste the contents** for the file itself, frontmatter and all.

6. Set a category if one obviously fits. Leave it blank rather than guessing,
   because a wrong category is worse than none for someone browsing.

7. Leave the reviewer notes field to the user unless they dictated something.
   That field is a message from a person to a person.

## Stop before submitting

8. Summarise what is in the form and ask the user to confirm. Do not click
   **Submit for review**.

   This is deliberate. Submitting publishes their name against a proposal and
   puts work in front of a curator, and there is no way to unsubmit it.

9. Once the user has confirmed in their own words, they can submit it
   themselves, or ask you to. Only click it if they explicitly ask.

## Afterwards

10. If a submission was made, read the page again. Automated checks run
    immediately and any findings appear under "Your submissions". Quote them
    back verbatim rather than paraphrasing, because a blocking finding is the
    difference between waiting for review and needing changes.