skill: package expo/skills into dockyard
Open
Nobody has claimed this yet.
skills
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Description
Package agent skills from expo/skills into the Dockyard registry.
Source
- Repo: https://github.com/expo/skills
- License: MIT
- Skill count upstream: ~12
- Trust signal: Official Expo/EAS; 1.8k stars
Candidate skills
Full curation at packaging time.
Acceptance criteria
- One
spec.yamlper selected skill underskills/<name>/ -
spec.refpinned to an audited upstream commit SHA -
task validate-skillpasses for each -
task scan-skillfindings triaged - Single PR grouping all Expo skills (branch
skills/expo)
Part of the vendor-by-vendor sweep following #466 (Trail of Bits).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the upstream expo/skills repository and the skills//spec.yaml layout first. Select and curate the skills, pin each spec.ref to an audited upstream commit SHA, then run task validate-skill and task scan-skill for every package. Done means scan findings are triaged and all Expo skills are grouped in the skills/expo branch and a single PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, yaml
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100