As OO and Scrivener both consume OPML, that is one route although OPML format limits the amount of data (attributes) pre item that can be interchanged**. See my aTbRef article on OPML export (and links from it). The built-in OPML
It sounds as though you want to:
- Use File -> Built-in Templates -> OPML to add the OPML template.
- Set your agent to use the OPML template.
- With the agent selected, use File -> Export selected note to export an OPML.
- Use the target apps’ OPML import instructions to ingest the the file.
** Note: OPML was never designed for interchange of lots of custom data, but rather for simple outlines. Of the two other apps in the frame here, OO and Scrivener, the latter is most limited. Scrivener is essentially an upstream app. Whilst you can add (links to) reference data, by design it doesn’t seem to see itself as an app into which you import existing writing. May a more seasoned Scrivener user please correct me (I’m certainly not doing down the app, just reflecting limitations for data interchange). By comparison, OmniOutliner might accept a custom CSV or tab-delimited format. You might need to start by seeing what OO will export and seeing if you can recreate that format from Tinderbox export. One thing I do know TB can’t export is outline expand/collapse state, which some other outliner can handle.