You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When referencing, we would need the full URL for the MD files—probably via the llms.txt format. However, that still doesn’t put all the resources on the developer's PC and will increase latency. The referenced documents would need to be placed in the references/ subfolder of the skill. I am not sure if that is doable via links...
I am normally more in favor of having everything in the skill and reference folder. That allows for human review and "locking" the content, which is sadly necessary for security.
Yes relative paths are shorter and therfore preferred. But thats only workable if the skill has a working relative path to the references if they are installed locally.
Activity
bearomorphism commentedon May 2, 2026
Sounds good.
docs: add Agent Skills SKILL.md
docs: add Agent Skills SKILL.md
bearomorphism commentedon May 8, 2026
Hi @philipp-horstenkamp could you provide feedback on those 2 linked PRs when you have a moment? Thanks!
bearomorphism commentedon May 8, 2026
Closing as completed.
philipp-horstenkamp commentedon May 8, 2026
Hi,
I do not think that the skill will work like this. The resources are relative to the repository root, but when installing a skill, only the skill folder (https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen) and its contents are included. That prevents it from accessing the relative files.
When referencing, we would need the full URL for the MD files—probably via the llms.txt format. However, that still doesn’t put all the resources on the developer's PC and will increase latency. The referenced documents would need to be placed in the references/ subfolder of the skill. I am not sure if that is doable via links...
I am normally more in favor of having everything in the skill and reference folder. That allows for human review and "locking" the content, which is sadly necessary for security.
philipp-horstenkamp commentedon May 8, 2026
Also as far as i am awrare the compatibility normaly lists the agent coding systems something is compatible with. But i am less sure about that.
bearomorphism commentedon May 9, 2026
I remember full URL is less preferred because it increases token usage. Agents should be able to figure out the location of MD files by themselves.
philipp-horstenkamp commentedon May 9, 2026
Yes relative paths are shorter and therfore preferred. But thats only workable if the skill has a working relative path to the references if they are installed locally.
docs(skill): remove broken doc references and unused compatibility fi…