Replies: 2 comments 1 reply
-
|
Having filemaker documentation available to the agent is great, but I think it is better to have documentation available through an MCP server so the agent can be more effective looking for information. We have created the documentation in docsets for FileMaker Pro, FileMaker Server, FileMaker Odata and FileMaker Data API and we haven indexed that documentation with databases so it can be most effective. We are still testing, but I can send you the docsets if you want to try it. We don't have instructions in the docs folder yet to teach the agent how to use dash yet |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good. I've not updated my personal copy of Dash and since Claris has historically had non existent support for Dash it's probably a good candidate for an include via the CLAUDE/AGENTS.md file. Either that - or - it would best be implemented as a skill that can be optionally included for those developers who do use Dash. Since using Dash is more specific to the developers who chose to use it, my first thought is to implement a skill lookup. My suggestion would be to create your own repository. Maybe something like 'filemaker-dash-skill'. I can then have agentic-fm use it's own skill-lookup feature (not created yet) and it can reference a file of repositories I've included into the project. There's already a skill for migrating out of FileMaker here. I was going to do my own, but he's done a really comprehensive job so it makes more sense to just support having an agent pull it into the local project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@marcoaperez proposed this within the comments of #10 This is where the discussion will be facilitated.
Beta Was this translation helpful? Give feedback.
All reactions