skill: package awslabs/agent-plugins 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 awslabs/agent-plugins into the Dockyard registry.
Source
- Repo: https://github.com/awslabs/agent-plugins
- License: Apache-2.0
- Upstream HEAD (at survey time):
d8952ba(2026-04-16) - Trust signal: Official AWS Labs; 597 stars
Candidate plugins / skills
Plugins (each bundles a skills/ subfolder):
aws-serverless—aws-lambda,api-gateway,aws-serverless-deployment, etc.aws-amplifydatabases-on-awsdeploy-on-awsmigration-to-awssagemaker-aiamazon-location-service
Exact paths to confirm at packaging time — likely curate a subset given the size.
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 AWS Labs skills (branch
skills/awslabs)
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
Start by confirming the exact skill paths in awslabs/agent-plugins and selecting the subset to package. Create one skills//spec.yaml per selected skill with spec.ref pinned to an audited upstream commit SHA. Run task validate-skill and task scan-skill for each, triage findings, and group the work in a single skills/awslabs branch PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100