In Tiger, you could use Terminal.app to create .term files, which were capable of running a command in a shell when you double-clicked it in Finder. You could also put a .term file in ~/Library/Scripts and trigger it from the scripts menu in the main menu bar. I used .term files for a number of different tasks, such as running a custom ssh command to connect to a particular server, or running an svn command to update a Subersion repository. Leopard's Terminal.app has nothing comparable to .term files. Leopard does have .terminal files, which are files for exporting and importing Terminal settings, and these files do have settings for running a command in a shell on opening, but .terminal files cannot be used like .term files. Every time you double-click a .terminal file in Finder, it imports the Terminal settings and creates a new entry in the Settings view in Terminal Perferences. So you could end up with hundreds of items in the list after opening the same .terminal file hundreds of times. Also, .terminal files cannot be triggered from the system-wide scripts menu.