Skip to content

Clarification on applying SkillOpt to skills containing multiple auxiliary files #54

@yu-lin-li

Description

@yu-lin-li

Hi there, thanks for the excellent work on this repository!

I noticed that the updated skill example provided in this repository only includes a single SKILL.md file. However, real-world skills often involve multiple auxiliary files, such as additional scripts or reference materials located in folders like scripts/ or references/.

Could you clarify or suggest how SkillOpt should be properly applied or structured when dealing with more complex skills that include multiple supporting files beyond just the main markdown documentation?

Thank you!

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