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

launch-directories

Skill0 starsChanged 16 days agoMITView on GitHub

Trigger: submit to directory, AlternativeTo, MacUpdate, Indie Hackers product, AppAddict, iOS Dev Weekly. Fill app directory and newsletter forms, stopping before submit.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Eastkap/autocomp★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    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 listed in app directories or suggested to newsletters through their web forms.

    line 12
  2. Very specific:

    Before filling, check the directory's fit and gate in references/channels.md (for example MacMenuBar needs an email on the app's own domain.

    line 17
  3. Distinctive:

    Stop before the final submit button: show what was filled and ask.

    line 19
  4. Distinctive:

    Use a contact email the user has already made public, or ask for one.

    line 20
  5. Distinctive:

    Read the kit; list missing fields per directory.

    line 36
  6. Distinctive:

    Ask before submitting; after submitting, read the confirmation page.

    line 38

≈ “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 listed in app directories or suggested to newsletters through their web forms.

Hard Rules

  • Values come from docs/launch/<slug>/kit.md and its assets/. A required field that the kit lacks is a gap: ask, do not invent.
  • Before filling, check the directory's fit and gate in references/channels.md (for example MacMenuBar needs an email on the app's own domain; Applite only lists official Homebrew casks). If it does not fit, say why and skip it.
  • The user signs in; never type passwords. Fill forms with the available browser automation; if there is none, give field-by-field values.
  • Stop before the final submit button: show what was filled and ask. Never pay: paid review or promotion options are the user's decision.
  • Use a contact email the user has already made public, or ask for one.
  • Mark claims you verified in code (for example "no network requests") and do not tick feature boxes you could not verify.

Decision Gates

DirectoryNotes
AlternativeToSet icon and screenshots with the by URL fields (file uploads do not register). After submitting, confirm on My submissions and add existing apps as alternatives, or the listing stays nearly invisible. The free queue is slow; mention the paid option without choosing it
MacUpdateTransparent PNG icon, up to 5 PNG/JPG screenshots; put first-run caveats (for example not notarized) in the reviewer comments
Indie HackersProduct page first; then fill motivation, start date, founders, model, funding, commitment, platforms, tags so it appears in the directory
AppAddictReview form; for a free app answer No to the NFR license and say it is free
iOS Dev WeeklySuggest the technical post, not the app page
Indie GoodiesNow a GitHub list (onmyway133/awesome-open-source-mac-apps, one JSON per app) that needs 100+ GitHub stars; below that, mark it blocked. When the gate is met, it is a pull request (launch-lists)

Execution Steps

  1. Read the kit; list missing fields per directory.
  2. For each directory: check fit and gate, open the form, fill it, screenshot or read back the values.
  3. Ask before submitting; after submitting, read the confirmation page.
  4. Record the result with launch-tracker, including queue or review status.

Output Contract

Return per directory: submitted, skipped (reason) or blocked (gap), the confirmation text or URL, and any follow-up such as adding alternatives.

References

  • ../../references/channels.md: fields, gates and gotchas per directory.
  • ../launch-kit/SKILL.md: how the kit and assets are produced.

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.