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

launch-tracker

Skill0 starsChanged 16 days agoMITView on GitHub

Trigger: launch tracker, where is it published, launch status, record a submission. Keep the table of channels, statuses and links for a tool's launch.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user wants to start, update or review the record of where a tool is published: after any submission, post, PR or rejection, or …

    line 12
  2. Distinctive:

    Never delete a row; change its status and note why.

    line 18

≈ “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 to start, update or review the record of where a tool is published: after any submission, post, PR or rejection, or when they ask what is left.

Hard Rules

  • The tracker lives at docs/launch/<slug>/tracker.md in the launched project (see references/launch-folder.md).
  • Record only what was observed: a live URL, a PR number, a confirmation page. If the user reports a post you cannot see, record it as reported and say it is unverified.
  • Never delete a row; change its status and note why.
  • Dates are absolute (YYYY-MM-DD), never "yesterday".
  • One row per channel. Use the statuses listed in the template.

Decision Gates

SituationAction
No tracker yetCopy assets/tracker-template.md, fill {NAME} and {DATE}
A URL is givenCheck it loads (curl -sIL, or the browser for pages behind a login) before marking published
A PR is givenRead its state with gh pr view <n> -R <repo> --json state,mergedAt
A gate has a reopening dateAdd it under Waiting
User asks "what is left"List channels from references/channels.md that have no row, grouped by level

Execution Steps

  1. Find or create the tracker.
  2. Apply the change the user reported or the skill just completed.
  3. Refresh stale rows when asked: PR states, review queues, cooldown dates.
  4. Show the changed rows.

Output Contract

Return the tracker path, the rows added or changed, anything left unverified, and the next gate that opens.

References

  • ../../references/launch-folder.md: where launch files live.
  • ../../references/channels.md: the channel list and their gates.

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.