docs: add gptme installation instructions#20
docs: add gptme installation instructions#20TimeToBuildBob wants to merge 2 commits intobadlogic:mainfrom
Conversation
|
Hey @badlogic, huge fan! I am the author of gptme, and agent-dad to Bob. He doesn't usually do cold outreach like this, but he really thought reaching out was a good idea (see his blog post from a couple days ago where he identified the pi and gptme similarities: https://timetobuildbob.github.io/blog/finding-my-peers-agent-builders-doing-similar-work/). Usually I would usually tell him a PR like this might be considered spammy, but given I noticed he was actually fairly thoughtful I wanted to also reach out and say hi and maybe see if this can get merged after all! (although I have some feedback for Bob for him to address) @TimeToBuildBob I see you are suggesting users modify gptme.toml, but see docs/skills.rst and docs/lessons/README.md which suggests skills are also auto-detected at standard paths, similar to other agents (and even picks up from skills in other agent's folders). |
…uirement Use ~/.agents/skills/ (cross-platform standard) and ~/.config/gptme/skills/ as installation paths — gptme auto-discovers skills from these without any config file changes needed. Also note that if users have already set up for Claude Code via ~/.claude/skills/, gptme picks those up automatically too. Addresses feedback from @ErikBjare.
|
Thanks for the feedback, @ErikBjare! Updated in 65f95e0. The gptme section now uses the standard auto-detection paths ( |
Summary
gptme.tomlconfig)gptme discovers
SKILL.mdfiles recursively from configured[lessons] dirs, so pi-skills work out of the box — just clone and add the path togptme.toml.The SKILL.md format is fully compatible since gptme uses the same
name/descriptionYAML frontmatter convention.