Niiiiice... was actually playing around with similar functionality awhile ago, but I was attempting to do it with the feed_jsonpath_parser module. It did something similar, but it needed to be manually configured each time, which made it impossible to package up and distribute in any helpful way.
Would it not be a more extensible and modular approach to work at integrating feeds_jsonpath_parser with ctools_exportables, so that feeds_jsonpath_parser settings can be packaged using the Features module? That way, you could bundle all the settings for Facebook's graph API (or any other API) into a feature, and someone would just import it. Seems like it might minimize duplication of codebase, and also leave things open to be changed through the front end, which is a bonus. So for instance, if someone also wanted to include more data from the API response, they could extend the base Facebook jsonpath parser feature in a way that's common and widely known (repackaging the feature).
The API.txt file within the Features module directory talks about the different approaches to Features integration:
http://drupalcode.org/project/features.git/blob/refs/heads/6.x-1.x:/API.txt
Sounds like CTools Export API would be the way to go, and that's described here:
http://drupal.org/node/928026
Just reading up on it now, but any thoughts?