feat(skills): Add aggregated instrument-* skills with example_paths and metadata support#87
feat(skills): Add aggregated instrument-* skills with example_paths and metadata support#87
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
|
Nest your skill directories under |
| const baseDescription = group.description || null; | ||
| const baseSharedDocs = group.shared_docs || []; | ||
| const baseMetadata = group.metadata || {}; | ||
| const baseExamplePaths = group.example_paths || []; |
There was a problem hiding this comment.
@skoob13 we have an existing example_path field at the skill variant level. I think including multiple examples makes total sense! but now we have multiple code paths for resolving example_path and example_paths in the spec
would you mind updating the repo to standardize on a single example_paths field that accepts either a string or an array at both the skills group level and individual variant level? We can then normalize everything to an internal _examplePaths array with a single function
2 participants
Problem
Agent consumers (like Twig) need bundled skills that contain all platform variants in a single package, rather than picking one per-platform skill. We also need these aggregated skills to include example project code as references, and to carry metadata (like
consumer: agent) through to the manifest.Changes
instrument-*skills: Added four new skill groups (instrument-integration,instrument-feature-flags,instrument-llm-analytics,instrument-logs) withtype: docs-onlyconfigs and dedicated description templates. Each bundles all platform docs into a single skill.example_pathssupport: New config field that lists multiple example projects. Group-level and variant-level paths are merged. Each example is processed into anEXAMPLE-{dirName}.mdreference file, listed after docs in the skill body.metadatapassthrough: Group and variant-levelmetadatafields are merged and flow through to SKILL.md frontmatter and the manifest. Used to tagconsumer: agenton aggregated skills.build.jsnow includes skill metadata in the generated manifest when present._examplePaths(group passthrough, variant merge, empty default) and_metadata(group passthrough, variant override, empty default).How did you test this code?
npx vitest run scripts/lib/tests/skill-group-expander.test.js— all 10 tests passpnpm build— builds all 59 skills successfullyinstrument-integration-all.zipcontains 30EXAMPLE-*.mdfiles listed after docs in SKILL.md