Google Reader has a nifty “Send To…” feature that lets you push reader items to other services — such as social networks, Instapaper, and so forth.

I have recently set up a Send To service that will send your Google Reader articles to OmniFocus, provided you’re using version 1.8 or later. (Currently in beta, download it here) (Props and full credit goes to Gokubi for setting this up for version 1.7 — I just polished it up a bit and used the native URI handler in OF 1.8)

Setup is pretty simple. In Google Reader, go to your Reader Settings (upper right corner), and click on the “Send To” tab. Then you just have to add a new service, and use the following settings:

Name: OmniFocus

Send to URL: http://omnifocus.nik.me?name=${title}&note=From+${source}%3A+${short-url}

Icon URL: http://omnifocus.nik.me/OmniFocus-16.png

Then just go back to Google Reader, and choose Send To on an article (or type Shift + T), and select OmniFocus.

Again, this only works with OmniFocus 1.8, which is in beta right now. If you want the same functionality without having to switch to a potentially untrustworthy version of OF, you can use Gokubi’s original setup, which leverages my URI handler for OF 1.7 and earlier.

OMNIFOCUS URI HANDLER

This applet enables you to create new tasks using an “x-omnifocus” URL. This is particularly designed to make it easy to add tasks from a web browser via a bookmarklet, without having to code a separate script for each browser. This also works in browsers that don’t support AppleScript. (I’m looking at you, Firefox!!!)

It also supports more advanced URLs containing context and project assignments that you’re likely to create from web page bookmarklets. This functionality can be utilized to make it easier to add OmniFocus tasks from other applications, shell scripts, etc., without having to hook into complicated AppleScript.

It’s taken me a few days to consider what, if any, reaction was warranted by the recent announcement of OmniFocus. Given that I am hopelessly addicted to all the software Omni makes (although I don’t own all of it, I would buy it if I didn’t have a family to feed), I assume I will be migrating to OmniFocus when it ships or enters public beta.

However, I am currently stuck wholly in Kinkless GTD, and I expect to keep working there as well.

So the question comes down to whether I intend to continue to improve/support the many scripts I’ve built to enhance Kinkless GTD.