skill: package elastic/agent-skills into dockyard
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github
- Domain
- tooling
Research direction
Start with elastic/agent-skills at upstream commit 43f4c98223 and review the candidate skills plus remaining upstream skills for packaging. Create one skills//spec.yaml per selected skill on branch skills/elastic, pin each spec.ref to the audited SHA, then run task validate-skill and task scan-skill. Done means findings are triaged and one PR groups all Elastic skills.
Written by the indexing model from the issue text.
Description
Package agent skills from elastic/agent-skills into the Dockyard registry.
Source
- Repo: https://github.com/elastic/agent-skills
- License: Apache-2.0
- Upstream HEAD (at survey time):
43f4c98(2026-04-17) - Skill count upstream: ~33
- Trust signal: Official Elastic; 364 stars
Candidate skills (examples; full curation at packaging time)
cloud/access-managementcloud/create-projectcloud/network-security- plus remaining skills in the repo
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 Elastic skills (branch
skills/elastic)
Part of the vendor-by-vendor sweep following #466 (Trail of Bits).
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 56
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from stacklok/dockyard
-
grype high security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stacklok/dockyard#950 · 3 comments ·
Maintainers usually reply within 3 days
-
grype high security
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
stacklok/dockyard#987 · 2 comments ·
Maintainers usually reply within 3 days
-
grype high security
Difficulty 3/5 1-2 days Newbie friendliness 62/100
stacklok/dockyard#986 · 2 comments ·
Maintainers usually reply within 3 days
-
grype high security
Difficulty 3/5 1-2 days Newbie friendliness 55/100
stacklok/dockyard#985 · 2 comments ·
Maintainers usually reply within 3 days
-
grype high security
Difficulty 3/5 1-2 days Newbie friendliness 50/100
stacklok/dockyard#958 · 1 comment ·
Maintainers usually reply within 3 days
All issues in stacklok/dockyard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linonetwo/cpa-session-archive#25 ·
Maintainers usually reply within 1 day
-
area/testing kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
agent-butler-finding bug
Difficulty 1/5 Under an hour Newbie friendliness 94/100
jordansmall/spindrift#4367 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day