Skip to content

Add possibility to define locations where skills should work #567

@zdohnal

Description

@zdohnal

Description

Hi all,

I was using Ymir skills for backport and rebuild, but since I have already prepared environment - dist-git repo prepared with remote url to my fork - I would like to declare for the skill that it can skip cloning and forking of repos, because it sometimes can take longer time because of spamming protections like Anubis.

Unfortunately lately if I call the skill in model Opus 4.6 and tell it the location, the model forgets it should work with the skill and some hiccups known for models which are covered by Ymir tools reappear (like incorrect date in changelog).

Would it be possible to support path(s) arguments for the skills, so it will be more difficult for LLM to forget?

Thank you in advance!

Zdenek

Benefit

Users which have already downloaded and prepared repos and are willing to allow LLM to access those dirs will the process be faster.

Importance

low importance

Workaround

  • There is an existing workaround that can be used until this feature is implemented.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions