agentleFS
alvaldesalvaldes/launch-skills/skills/launch-lists/SKILL.md

launch-lists

Skill0 starsChanged 16 days agoMITView on GitHub

Trigger: awesome list, add to awesome-mac, open-source-mac-os-apps, list PR. Add a tool to curated GitHub lists with one PR per list.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user wants a tool added to a curated GitHub list (awesome-mac, open-source-mac-os-apps or a similar awesome list).

    line 12
  2. Very specific:

    Read the list's CONTRIBUTING and PR template first.

    line 16
  3. Very specific:

    Search open and closed PRs and the list itself for the tool before editing: gh pr list -R <repo> --state all --search "<name> in:title".

    line 17
  4. Distinctive:

    Check the gates above and the duplicates search.

    line 35
  5. Distinctive:

    Commit with a Conventional Commit message.

    line 39
  6. Very specific:

    Ask, then push and run gh pr create -R <repo> --head <user>:add-<slug> --title "Add <Name>" --body-file <body>.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Activation Contract

Use when the user wants a tool added to a curated GitHub list (awesome-mac, open-source-mac-os-apps or a similar awesome list).

Hard Rules

  • Read the list's CONTRIBUTING and PR template first; they override this skill. Check the list still accepts public PRs: gh api repos/<owner>/<repo> -q .pull_request_creation_policy must not be collaborators_only, and recent issues must not announce a closure.
  • Search open and closed PRs and the list itself for the tool before editing: gh pr list -R <repo> --state all --search "<name> in:title".
  • One PR per list per tool. Change only the lines for this tool.
  • Pick the category by the closest comparable apps already in the list, not by keyword alone. Follow each file's own structure, even when translations differ.
  • Copy comes from docs/launch/<slug>/kit.md; descriptions are one sentence ending with a period.
  • Forking, pushing and opening the PR are public actions: show the diff and the PR body, then ask before each.
  • Work in a clone outside temp folders; never in /tmp.

Decision Gates

ListHow
jaywcjlove/awesome-macOne line in README.md, README-zh.md, README-ja.md, README-ko.md; insert with scripts/insert-list-line.py per file and section; icons as the section uses them
serhii-londar/open-source-mac-os-appsWrite entry.json, append with scripts/add-json-entry.py applications.json entry.json; categories from categories.json
iCHAIT/awesome-macOSClosed to public submissions (2026-10-27); stop and tell the user
Another awesome listRead its rules; use insert-list-line.py for Markdown lists

Execution Steps

  1. Check the gates above and the duplicates search.
  2. gh repo fork <repo> --clone=false, then git clone --depth 1 the fork and git switch -c add-<slug>.
  3. Edit with the scripts; confirm git diff --stat touches only the intended files and lines.
  4. Validate: JSON parses; Markdown lines sit inside the right section, alphabetical.
  5. Commit with a Conventional Commit message; write the PR body from the repo's template.
  6. Ask, then push and run gh pr create -R <repo> --head <user>:add-<slug> --title "Add <Name>" --body-file <body>.
  7. Record the PR in the tracker (launch-tracker).

Output Contract

Return, per list: category chosen and why, the diff, the PR URL or the reason it was skipped.

References

  • ../../references/channels.md: list formats and closures.
  • scripts/insert-list-line.py: exit 1 on duplicates, 2 on bad input.
  • scripts/add-json-entry.py: keeps the file's formatting; exit 1 on duplicates.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.