agentleFS
SrejonKhanSrejonKhan/agent-skills/skills/create_launcher/SKILL.md

create_launcher

Skill3 starsChanged 2 months agoMITView on GitHub

Generates robust, cross-platform launcher scripts (Windows .bat, Unix .sh, Mac .sh) with dependency checking, .env handling, and graceful shutdown logic.

  • Reads credentials

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to generate professional-grade entry point scripts for applications.

    line 8
  2. Very specific:

    Use write_to_file to create the scripts.

    line 17
  3. Very specific:

    Use run_command with pwsh (Windows) or bash (Unix) to verify dependency checks if needed.

    line 18
  4. Distinctive:

    Check if required tools (node, python) are in PATH.

    line 34
  5. Very specific:

    Check if node_modules or venv exists.

    line 35
  6. Very specific:

    Check for .env file presence.

    line 36
  7. Distinctive:

    Ensure that killing the launcher kills the spawned processes.

    line 52
  8. Distinctive:

    When generating launchers, consider these enterprise patterns:

    line 62
  9. Very specific:

    Environment Portability: Ensure the script runs correctly regardless of the current working directory by resolving paths relative to the …

    line 64
  10. Distinctive:

    Health Checks: After starting the process, optionally ping an endpoint or check a port to confirm the app is actually running before …

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Create Launcher (Web & Scripts)

Use this skill to generate professional-grade entry point scripts for applications.

Inputs

  • App Name: Name of the application (for display).
  • Entry Point: Main script to run (e.g., main.py, index.js).

Tooling Strategy

  • Use write_to_file to create the scripts.
  • Use run_command with pwsh (Windows) or bash (Unix) to verify dependency checks if needed.

Workflow

1. Requirements Gathering

  • Target OS: Windows, macOS, Linux (default to creating for ALL).
  • Environment: Does it need .env variables?
  • Dependencies: What needs to run? (npm, python, node, docker).

2. Script Generation Rules

Common Features

  • Single Click Launch: Scripts must run without user argument input (or have defaults).
  • Pre-flight Checks:
    • Check if required tools (node, python) are in PATH.
    • Check if node_modules or venv exists.
    • Check for .env file presence.

Windows (.bat / .cmd)

  • Use @echo off.
  • Title the window.
  • Handle Ctrl+C gracefully if possible.

Unix (.sh for Mac/Linux)

  • Shebang: #!/bin/bash.
  • Permission: Remind user to chmod +x.
  • Trap Signals: Implement trap 'kill 0' SIGINT or similar to clean up subprocesses on exit.

3. Graceful Shutdown (The "No Orphan" Rule)

  • Ensure that killing the launcher kills the spawned processes.
  • For python scripts, consider wrapping in try-finally blocks.

4. Output

  • Generate the scripts in the project root.
  • Provide a quick Markdown snippet on how to run them.

Advanced Launcher Patterns

When generating launchers, consider these enterprise patterns:

  • Environment Portability: Ensure the script runs correctly regardless of the current working directory by resolving paths relative to the script itself (cd "%~dp0" on Windows, cd "$(dirname "$0")" on Unix).
  • Daemonization & Logging: Offer the option to run the application in the background and pipe stdout/stderr to a dedicated logs/ directory with timestamped files.
  • Health Checks: After starting the process, optionally ping an endpoint or check a port to confirm the app is actually running before exiting the launcher.

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.