Hook files are plain text files with the “.hook” suffix. They can contain any valid address (“URI”), whether or not the address is a hook://. For instance, you can insert a link to a website (such as https://apple.com), an OmniFocus task (such as:
omnifocus:///task/nGSe83xr2tE), or any other link.
When you double-click/tap on a Hook file in the Finder, Hook parses the address, and makes a system call to open the linked item.
Hook files are like aliases and web location (.webloc) files. Like Finder aliases they can link to other files. Like Finder “.webloc” files, they can link to web pages.
But they are better than aliases and web locations in many respects:
- they can refer to anything that your macOS instance can normally resolve;
- they can refer to hook:// items (and so link to email, files, Spotlight searches and so on); and
- in the spirit of Markdown and openness, Hook files are plain text. So you can include any address (URI) or even a Markdown link in a Hook file!
The “Make Hook File” command is a Pro feature. However, you can also construct Hook files manually by creating a plain text file that has a “.hook” filename extension. Just include whatever address (URI) or Markdown link you’d like Hook to execute.
When you use the “Make Hook File” command from the Desktop, Hook will try to put a Hook file in the same folder as a current selection, which must be a single file or resource. You can also create a Hook file using the Hook window in the context of other apps than Finder. In that case, Hook will create a Hook file from the current resource and put in the “Hook Files” folder of your Hook folder.