Repository navigation
Replies: 2 comments 2 replies
|
Hey @ryanpeach , thanks for the suggestion. It makes a ton of sense. I think it's totally possible to write a skill/skills for this. In theory, IWE can work with Logseq/Obisidian/ZK files as is if the files are in Markdown format. What do you think is needed to convert Obsidian/Logseq vault into IWE? |
|
Hey @ryanpeach, sorry for the slow reply. Your point 1, getting any set of files to match the schema, is basically what I ended up building into the Mac app. It hosts Claude Code as the agent, and its writes go through the same validator as If you are on a Mac I'd love to get your take, it's alpha: https://github.com/iwe-org/iwe-mac/releases Did you end up documenting the git-mcp gateway setup from #373? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have some experience writing tools that try to keep up with the formatting of the latest PKM tools. Some people have suggested they want an Obsidian import feature, a Logseq one, a marksman one, zk, etc. It's a lot to keep up with.
I recommend making the tool have strong linting features for the style this tool demands, and then setting up a generic import command that takes an ai key and uses the mcp to move files from a destination to a src, linting along the way. Or maybe just a skill that can be used with Claude code and the like.
That way it supports all formats without a lot of effort.
All reactions