Skip to content

Consider using: package:extension_discovery #6

@jonasfj

Description

@jonasfj

As I understand it the idea is that packages should contain a top-level skills/ folder, in order to share skills with users who depend on the package.

As illustrate in your docs below:

my_package/
  lib/
  skills/
    my_package-code-gen/
      SKILL.md
      scripts/       # optional helper scripts
      references/    # optional reference docs
      assets/        # optional static resources
    my_package-testing/
      SKILL.md

Please consider following the conventions established in package:extension_discovery.

Basically:

my_package/
  lib/
  extension/skills/
    config.yaml
    my_package-code-gen/
      SKILL.md
      scripts/       # optional helper scripts
      references/    # optional reference docs
      assets/        # optional static resources
    my_package-testing/
      SKILL.md

Then you can also use package:extension_discovery to efficiently discover packages that have skills.

Note:

  • dart generally uses singular form

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions