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
- krishnakanthb13/antigravity_global_skillsedited, first seen Jul 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- krishnakanthb13/antigravity_global_skills★ 50100% same
Wrote their own version · 0
None found.
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 repository46 other files it gives its agents.
- agy-customizationsSkill
- antigravity-guideSkill
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code_reviewSkill
- code-simplificationSkill
- context-engineeringSkill
- create_skillSkill
- daily_logSkill
- debugging-and-error-recoverySkill
- debug_issueSkill
- deprecation-and-migrationSkill
- document_apiSkill
- documentation-and-adrsSkill
- enhance_uiSkill
- frontend_designSkill
- frontend-ui-engineeringSkill
- generate_release_imageSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- idea_to_actionSkill
- impeccableSkill
- incremental-implementationSkill
- list_featuresSkill
- open_source_prepSkill
- optimize_codebaseSkill
- performance-optimizationSkill
- permissioned-githubSkill
- planning-and-task-breakdownSkill
- release_helperSkill
- repo_infographicSkill
- scaffold_testsSkill
- security-and-hardeningSkill
- security_auditSkill
- shipping-and-launchSkill
- software_architectureSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- test_runnerSkill
- ui_ux_pro_maxSkill
- update_docsSkill
- using-agent-skillsSkill
- using-ui-stackSkill
- web_performance_optimizationSkill
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
- Distinctive: line 8
Use this skill to generate professional-grade entry point scripts for applications.
- Very specific: line 17
Use write_to_file to create the scripts.
- Very specific: line 18
Use run_command with pwsh (Windows) or bash (Unix) to verify dependency checks if needed.
- Distinctive: line 34
Check if required tools (node, python) are in PATH.
- Very specific: line 35
Check if node_modules or venv exists.
- Very specific: line 36
Check for .env file presence.
- Distinctive: line 52
Ensure that killing the launcher kills the spawned processes.
- Distinctive: line 62
When generating launchers, consider these enterprise patterns:
- Very specific: line 64
Environment Portability: Ensure the script runs correctly regardless of the current working directory by resolving paths relative to the …
- Distinctive: line 66
Health Checks: After starting the process, optionally ping an endpoint or check a port to confirm the app is actually running before …
≈ “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.
Files
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_fileto create the scripts. - Use
run_commandwithpwsh(Windows) orbash(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
.envvariables? - 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_modulesorvenvexists. - Check for
.envfile presence.
Windows (.bat / .cmd)
- Use
@echo off. - Title the window.
- Handle
Ctrl+Cgracefully if possible.
Unix (.sh for Mac/Linux)
- Shebang:
#!/bin/bash. - Permission: Remind user to
chmod +x. - Trap Signals: Implement
trap 'kill 0' SIGINTor 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.
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
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.

