Workflow skills
How Roark resolves bundled and repo-local skills while keeping normal workflow agents isolated from ambient Pi skill discovery.
Last updated
#create-issues publishing
The approved create-issues --yes publishing path resolves the Roark-owned github-issue-create skill and passes only that resolved skill path to the Pi runner.
Global or machine-local skills are not used as fallbacks.
#Repo-local override
Skill resolution checks the target workspace first:
.roark/skills/github-issue-create/If that override directory exists, Roark validates its SKILL.md and uses it. Missing or malformed override metadata fails clearly instead of falling back to the bundled copy.
#Bundled skill
When no repo override exists, Roark loads the bundled package skill from:
skills/github-issue-create/The path is resolved relative to the installed Roark package, not the process working directory.
The bundled package includes the skill's SKILL.md, templates/, examples/, and references/.
#Updating the bundled skill
When updating the bundled skill:
- Copy the upstream skill directory deliberately.
- Record the upstream source and commit in the update PR.
- Run skill-resolution and create-issues tests.
#Next steps
- Use Issue curation for the
curate-issuesandcreate-issuesworkflow. - Use Architecture for contributor-level integration points.
- Use CLI reference for command options.