Skip to content

chore: move authored skills to repository-root skills folder - #146

Open
kieronlanning wants to merge 4 commits into
mainfrom
chore/skills-root-folder
Open

kieronlanning wants to merge 4 commits into
mainfrom
chore/skills-root-folder

Conversation

@kieronlanning

Copy link
Copy Markdown
Contributor

The skills CLI only discovers skills at a root skills/ folder, and .agents/ is
gitignored here, so it is absent from a git clone. Packing is unchanged: the
IncludeRepositorySkillsInPackage shim keeps shipping them to .agents/skills/, so
consumers see no difference.

The skills CLI only discovers skills at a root skills/ folder, and .agents/ is
gitignored here, so it is absent from a git clone. Packing is unchanged: the
IncludeRepositorySkillsInPackage shim keeps shipping them to .agents/skills/, so
consumers see no difference.
Purview.BuildSdk 1.0.6 removes skill packaging and the build-time .agents/
mirror, so the skills CLI cloning the git repository is the only delivery
route. Skills are authored at skills/<name>/SKILL.md and nothing packs them.

- rename every skill to a purview-<product>-* prefix; skills install into one
  flat directory per agent, so an unprefixed name collides with somebody
  else's and the loser is whichever installed second
- validate them on every test run with Purview.Skills.Testing 1.0.6, through a
  Repository.UnitTests project whose [InheritsTests] attribute is load-bearing
- raise the TUnit floor to 1.75.0, which Purview.Skills.Testing depends on and
  central transitive pinning would otherwise pin back down
- delete the PurviewSkillsToPack shim and the .agents/**/* pack-validation entry
A tracked solution-level setting, so format-on-save matches the lint check the
pipeline runs rather than being set per developer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant