Suggest a resource, Custom GPT based on Ethereum Builder Docs

[jtd2]

Name

Eth_AI

Resource URL

t.me/Eth_GPT_AI_BOT

Description

The resource provided is a simple Custom GPT based on the Ethereum Builder Docs. The main goal is to make the Ethereum Ecosystem more accessible to future developers.

Training Document regarding the file:
eth_llms.txt

Logo

No response

Category

Artificial Intelligence

Would you like to work on this issue?

• Yes
• No

[konopkja]

ok so it coincidentally happened @pettinarip that we have another llm text file here, duplication with #15654

[jtd2]

ok so it coincidentally happened @pettinarip that we have another llm text file here, duplication with #15654

@konopkja Do you want me to contribute to #15654 or do you want me to keep this current ticket opened?

[konopkja]

I think we need just one llm file so i will let decide @pettinarip which one is more suitable or the next steps

[pettinarip]

Hey @jtd2 I've created a general llms.txt file for the site, which will live at the root level: https://ethereum.org/llms.txt.
Since you've been focused on the documentation, I have a few questions about how this should work:

• Should this file be placed at the docs level instead, for example, https://ethereum.org/developers/docs/llms.txt?
• If so, how would it differ from the root-level file?

I'm also unsure about the efficiency of having nested llms.txt files, to be honest.

[jtd2]

Hey @jtd2 I've created a general llms.txt file for the site, which will live at the root level: https://ethereum.org/llms.txt. Since you've been focused on the documentation, I have a few questions about how this should work:

• Should this file be placed at the docs level instead, for example, https://ethereum.org/developers/docs/llms.txt?
• If so, how would it differ from the root-level file?

I'm also unsure about the efficiency of having nested llms.txt files, to be honest.

Hello @pettinarip, I think this file should be placed on the root level instead of the docs level. The reason why I would say that is because I already looked at the file and the llms.txt file that you have already provided is a basic, surface level document requiring what documents to scrape. My llms.txt file is completely different because it focuses on the builder docs extensively where the links have been expanded out to include the context that each of those specific links provides.

When you mean by nested llms.txt files, are you referring to the document that I have posted on my ticket where it shows the builder docs files in detail with their links?

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[konopkja]

closing this for now as not doing